Telcon: 2020 07 16

Attendees

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 test function; packages have a run_tests attribute which is True when the user installs with spack install test=... where you can select test=root or test=all
- Also one can have dedicated test packages: Like fabtests. It is doing infiniband tests. They're run for after install if test=root/all is select. In addition all the tests are install into bin/ so that they can be run at any later time.
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 -C and 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 spack command options (like -C)