diff options
| author | Todd Gamblin <tgamblin@llnl.gov> | 2020-07-21 18:48:37 -0700 |
|---|---|---|
| committer | Gregory Becker <becker33@llnl.gov> | 2020-07-23 13:56:18 -0700 |
| commit | f528022a7d4a3671deed9b031e878cf7a0ba950f (patch) | |
| tree | 33bb31c80ac3c78fc22608ae4e3e2ed6288452bd /.coveragerc | |
| parent | 665a47607ea579f0773b4b1ca3315b8759bd9cb0 (diff) | |
| download | spack-f528022a7d4a3671deed9b031e878cf7a0ba950f.tar.gz spack-f528022a7d4a3671deed9b031e878cf7a0ba950f.tar.bz2 spack-f528022a7d4a3671deed9b031e878cf7a0ba950f.tar.xz spack-f528022a7d4a3671deed9b031e878cf7a0ba950f.zip | |
bugfix: make compiler preferences slightly saner (#17590)
* bugfix: make compiler preferences slightly saner
This fixes two issues with the way we currently select compilers.
If multiple compilers have the same "id" (os/arch/compiler/version), we
currently prefer them by picking this one with the most supported
languages. This can have some surprising effects:
* If you have no `gfortran` but you have `gfortran-8`, you can detect
`clang` that has no configured C compiler -- just `f77` and `f90`. This
happens frequently on macOS with homebrew. The bug is due to some
kludginess about the way we detect mixed `clang`/`gfortran`.
* We can prefer suffixed versions of compilers to non-suffixed versions,
which means we may select `clang-gpu` over `clang` at LLNL. But,
`clang-gpu` is not actually clang, and it can break builds. We should
prefer `clang` if it's available.
- [x] prefer compilers that have C compilers and prefer no name variation
to variation.
* tests: add test for which()
Diffstat (limited to '.coveragerc')
0 files changed, 0 insertions, 0 deletions