Telcon: 2024 05 15

Wednesday May 15th, 9am PT (UTC -7:00)

(This week the meeting is for Q&A, there are no pre-planned topics)

Sean: building software stack with a Spack environment
- Multiple compilers
- Multiple MPI instances
- Want to build every combination of compiler+mpi
- Split the compilers into separate environments
  - Each of these environments has 1 or 2 MPI implementations
- Merging them all into 1 environment, was having an issue with matrix specifications
  - when you combine [^mpi] with [sapy], it didn't build sapy at all
    - when you explicitly say sapy ^mpi, it would generate an error message
    - also note: sapy came from an external package repo
- This was using 0.21.2
  - https://github.com/spack/spack/pull/43202 was merged March 31st, and may help (it is part of 0.22)
- Also was having an issue where the environment would mix compilers for DAGs that were expanded
  - See: https://github.com/spack/spack/issues/43475
Sean: external dependencies
- A package references a dependency, e.g. setup_dependent_build environment
- Or cases where packages ask about dependencies of dependencies
- oneapi-mkl has an example of this
- In general, what to do about dereference errors for externals
  - You can add a direct dep
Wyatt: new release features?
- https://github.com/spack/spack/discussions/44141
Wyatt: smoke tests use .spack
- These are not relocated
- See: https://github.com/spack/spack/issues/29186

Provide feedback