Telcon: 2024 02 21

Wednesday February 21st, 9am PT (UTC -8:00)

Attendees

• Peter Scheibel (host)
• Aditya Kavalur
• Prentice Bisbal (PPPL)
• Dom Heinzeller
• Massimiliano Culpo

Possible issues for next week:

• https://github.com/spack/spack/issues/42535
  • Module autoloading: spack loads too many modules for some users (more than necessary)

Agenda

There are no pre-planned agenda items: this meeting is just for Q&A

• Aditya: https://github.com/spack/spack/issues/42695
  • Issue building Paraview
  • Issue finding libstdc++
  • Is paraview a script?
    • If so, we might want to check if the underlying executable has the same issue (i.e. if the script interferes with the env in some way)
  • Is paraview built as part of our pipelines?
    • https://cache.spack.io/
    • Yes: https://cache.spack.io/package/v0.21.1/paraview/specs/
  • You can see that with spack build-env paraview bash
  • Try readelf -d on paraview
  • You can look at the compiler entries with spack config blame compilers
• Prentice:
  • "spack edit "
  • Each new version includes a dozen or so tarballs
  • Also this is commercial software that has to be downloaded separately
  • Can I checksum them all with Spack?
    • spack checksum --add-to-package
      • This might not add resources
      • and it might not work for file URLs