Telcon: 2022 06 29

Attendees

• Peter Scheibel (host)
• Massimiliano Culpo
• Richarda Butler
• Matt Belhorn (OLCF)
• Greg Becker
• Brian Van Essen
• Todd Gamblin
• Phil Sakievich

Agenda items

• Brian: unify: false - why is that the default?
  • All created environments have unify: false explicitly added (with spack create)
  • As a side effect, if you
  • true would make more sense
  • Next Spack release will change away from unify: false
    • Unify-when-possible might be the safest default in the sense that it avoids concretization errors
    • But... it doesn't necessarily produce what users might expect (i.e. if they aren't aware, then they might get different installs of things)
• The annoyances of ~ configuration came up

Possible Agenda items

• (Massimiliano) Continue from https://github.com/spack/spack/wiki/Telcon%3A-2022-06-08: multiple build systems used by one package
• (Matt) if we build an environment, and one package fails, then module files are not generated
  • Want spack module refresh but only to generate module files that haven't been generated yet
• Updating compiler wrapper to strip -Werror (optionally): https://github.com/spack/spack/pull/30284
• (Wileam) Adding fpm as a build system
  • Issue on fpm repo: https://github.com/fortran-lang/fpm/issues/79
• Default action for concretization in environments: https://github.com/spack/spack/pull/29942#issuecomment-1097287194
• Continue from https://github.com/spack/spack/wiki/Telcon%3A-2022-04-06: warning() directive
• (Wileam) Can't bootstrap llvm@13 and @14 if gold is enabled (which is the default behavior) https://github.com/spack/spack/issues/29350
  • Pinpointed issue to external package (binutils carried by OS) based on comment
  • PR drafted: https://github.com/spack/spack/pull/30954
  • Can externals detection be expanded from executables only to arbitrary files (e.g. header or .a/.so library files)?
• How to reorganize the docs?
• Continue from https://github.com/spack/spack/wiki/Telcon%3A-2022-04-13: not in spec syntax