Skip to content

add subsection "Installing for a different StdEnv" #38

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Sep 1, 2020
Merged

add subsection "Installing for a different StdEnv" #38

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d92bbc2
add subsection "Installing for a different StdEnv"
ostueker Sep 1, 2020
ed592c4
fix typo
ostueker Sep 1, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions doc/easybuild.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -298,6 +298,21 @@ sudo -i -u ebuser RSNT_ARCH=sse3 eb <name of easyconfig file>
**Note:** The actual generated easyconfig will be saved into
`/cvmfs/soft.computecanada.ca/easybuild/ebfiles_repo*`.

### Installing for a different StdEnv

The `StdEnv/2016.4` and `StdEnv/2018.3` are built on top of Nix while the `StdEnv/2020` is built on top of Gentoo.
In order for EasyBuild to choose the correct toolchains and underlying Nix or Gentoo, a suitable StdEnv needs
to be loaded before invoking `eb`.
As of September 2020, on build-node the `StdEnv/2016.4` is still the default and good to compile software for
both `StdEnv/2016.4` and `StdEnv/2018.3`.

So for building software for `StdEnv/2020`, the new StdEnv needs to be loaded first:

```
module load StdEnv/2020
sudo -i -u ebuser eb <name of easyconfig file>
```

### Creating or changing a recipe

Because often a few things need changing in the easyconfig file we are going to
Expand Down