summaryrefslogtreecommitdiff
path: root/CITATION.cff
diff options
context:
space:
mode:
authorHarmen Stoppels <harmenstoppels@gmail.com>2022-10-12 01:45:51 +0200
committerGitHub <noreply@github.com>2022-10-11 17:45:51 -0600
commit926dca9e5fa159201989ebef464984aab92716d2 (patch)
tree778431d8db8b633740e85222fff435feb27ae7f3 /CITATION.cff
parent4b866e8ffc69d89064cf011675f63de12684ef76 (diff)
downloadspack-926dca9e5fa159201989ebef464984aab92716d2.tar.gz
spack-926dca9e5fa159201989ebef464984aab92716d2.tar.bz2
spack-926dca9e5fa159201989ebef464984aab92716d2.tar.xz
spack-926dca9e5fa159201989ebef464984aab92716d2.zip
Specify GCC prefix in LLVM-based compilers (#33146)
* spack.compiler.Compiler: introduce prefix property We currently don't really have something that gives the GCC install path, which is used by many LLVM-based compilers (llvm, llvm-amdgpu, nvhpc, ...) to fix the GCC toolchain once and for all. This `prefix` property is dynamic in the sense that it queries the compiler itself. This is necessary because it's not easy to deduce the install path from the `cc` property (might be a symlink, might be a filename like `gcc` which works by having the compiler load a module that sets the PATH variable, might be a generic compiler wrapper based on environment variables like on cray...). With this property introduced, we can clean up some recipes that have the logic repeated for GCC. * intel-oneapi-compilers: set --gcc-sysroot to %gcc prefix
Diffstat (limited to 'CITATION.cff')
0 files changed, 0 insertions, 0 deletions