-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Telcon: 2020 07 16
Dr. Christian Tacke edited this page Jul 16, 2020
·
10 revisions
- Peter Scheibel (host)
- Vivek Kale (BNL)
- Christian Tacke
-
Can Spack customize runtime libraries?
- Not right now: these are defined by the compiler you choose (and no further customization is possible).
-
SOLLVE is identified as a Clang compiler now, does it need to be updated WRT https://github.com/spack/spack/pull/17525?
- No: if it was identified and usable as a Clang compiler before, that will still be true after 17525
-
On Cray, do I have to module load a compiler for Spack to find it with
spack compiler find?- No: Spack will look through all available modules (regardless of whether they are loaded) to find compilers.
-
How to test compilers?
- In general, any package can implement a
testfunction; packages have arun_testsattribute which isTruewhen the user installs withspack install test=...where you can selecttest=rootortest=all - Also one can have dedicated test packages: Like
fabtests. It is doing infiniband tests. They're run for after install iftest=root/allis select. In addition all the tests are install intobin/so that they can be run at any later time.
- In general, any package can implement a
-
If you override a config section in an environment, you should not see it anywhere
- Christian: provides an environment with packages and no compilers defined
- Christian: you currently cannot specify a config directory with
-Cand use an environment at the same time- There is a PR for that: https://github.com/spack/spack/pull/14608
- Right now, we can test specific Spack commands, but not global
spackcommand options (like-C)