Telcon: 2022 05 04

Attendees

• Peter Scheibel (host)
• Mark Krentel
• Phil Regier
• Massimiliano Culpo
• Greg Becker
• Tammy Dahlgren
• Wileam Phan
• Brian Van Essen

Agenda items

• (Mark) How do you tell Spack where opt/rocm is?
  • (Mark) you can install rocm through spack, but most people apparently download it and register it as an external
    • Proposal: Create an all-in-one AMD-rocm install of Spack
    • Right now hpctoolkit knows either to look in one joined space, or in several component spaces
    • (Greg) this requires turning each component into a virtual
    • (Greg) this could also be achieved by implementing external find for the components
      • Detecting externals by library is now possible
      • Also: each of the ROCm components could get a "rocm" tag, such that you can say spack external find --tags=rocm
        • (Once all the component packages have been updated to be "find-able"
  • (Peter) Do users expect to interface with a single ROCm prefix in their build systems?
    • (Mark) hpctoolkit understands the ROCm components individually
• (Phil) https://github.com/spack/spack/pull/30385: customizing OS for containers
  • Assigned reviewer
• (Brian)
  • Is there a way to encode a compiler used to build an external?
  • On a Cray machine, several instances of a package are installed with different compilers
  • (Greg) determine_spec_details
    • The default implementation calls determine_version and determine_variants, but nothing for compiler
    • We could update the default implementation to allow packages to implement determine_compiler
  • (Massimiliano) do these libraries live in the same directory?
    • Yes
    • In that case - problem: the base logic expects that you might have multiple instances with different versions in one dir, but that otherwise they will be split
  • (Peter) Cray manifest parsing should handle this automatically (since this is on a Cray)
    • (Greg) this month, the release should create Manifest files on most Cray systems

Possible Agenda items

• Continue from https://github.com/spack/spack/wiki/Telcon%3A-2022-03-09: Packages with multiple build systems
  • https://github.com/spack/spack/pull/29530
  • (Peter) What about external package repositories?
• Upcoming Cray support changes:
  • For 0.18
  • manifest (https://github.com/spack/spack/pull/29652)
  • (Greg) module list cray environments
• (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
• 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
• How to reorganize the docs?
• Continue from https://github.com/spack/spack/wiki/Telcon%3A-2022-04-13: not in spec syntax