diff options
| author | Todd Gamblin <tgamblin@llnl.gov> | 2020-07-05 22:35:01 -0700 |
|---|---|---|
| committer | Todd Gamblin <tgamblin@llnl.gov> | 2020-07-06 13:55:14 -0700 |
| commit | c00a05bfba50b79ce865ce32385d782667abea3d (patch) | |
| tree | 4e541bed7b895c796c3e197ba1619b0e164b07c1 /.coveragerc | |
| parent | 9ec9327f5aacc7b62a1469771c8917547393676d (diff) | |
| download | spack-c00a05bfba50b79ce865ce32385d782667abea3d.tar.gz spack-c00a05bfba50b79ce865ce32385d782667abea3d.tar.bz2 spack-c00a05bfba50b79ce865ce32385d782667abea3d.tar.xz spack-c00a05bfba50b79ce865ce32385d782667abea3d.zip | |
bugfix: no infinite recursion in setup-env.sh on Cray
On Cray platforms, we rely heavily on the module system to figure out
what targets, compilers, etc. are available. This unfortunately means
that we shell out to the `module` command as part of platform
initialization.
Because we run subcommands in a shell, we can get infinite recursion if
`setup-env.sh` and friends are in some init script like `.bashrc`.
This fixes the infinite loop by adding guards around `setup-env.sh`,
`setup-env.csh`, and `setup-env.fish`, to prevent recursive
initializations of Spack. This is safe because Spack never shells out to
itself, so we do not need it to be initialized in subshells.
- [x] add recursion guard around `setup-env.sh`
- [x] add recursion guard around `setup-env.csh`
- [x] add recursion guard around `setup-env.fish`
Diffstat (limited to '.coveragerc')
0 files changed, 0 insertions, 0 deletions