Skip to content
Peter Scheibel edited this page Aug 28, 2023 · 12 revisions

Wednesday August 23rd, 9am PT (UTC -7:00)

Attendees

  • Peter Scheibel (host)
  • Mark Krentel
  • Massimiliano Culpo
  • Tammy Dahlgren
  • Srinath Vadlamani
  • Patrick Broderick
  • Richarda Butler
  • Davide DelVento
  • Dom Heinzeller
  • Yang Liu
  • Todd Gamblin
  • Chris Green

Agenda

(This meeting is just Q&A, there are no pre-planned general Spack topics)

  • Mark: Question about porting environments between machines
    • src and target
    • Create a spack.yaml on src and concretize it
    • Copied the spack.lock
    • Is this the best way to proceed?
      • If the machines are the same, then yes
      • Mark: What does "same" mean?
        • The same compiler (or using one Spack can build)
        • Same OS
          • Mark: in this case they were both RHEL 8
        • Same externals
        • Same arch and target
          • Mark: In this case the src is intel and the target is amd
          • This is the mismatch: because of this, spack.yaml should be copied and not spack.lock
          • Why didn't spack complain?
            • The lock is pre-concretized
        • Massimiliano: the common denominator is x86_64v3 so if you select this target on the src machine
  • Patrick:
    • Built some packages ~1 year ago
    • Package called spiral and some other spiral-* packages
    • spiral expects to find packages under a home directory
      • Was using spack activate
    • An env was creating a view
      • was encountering an issue when installing a new package
      • Peter: this should work, so I want to check what went wrong here
      • It turns out that the "root" spiral package needs these to be in it's prefix at build time (i.e. at the time you build spiral-sub
    • Todd: suggestion to create variants in spiral-software, which depends on the spiral-* components, after installing those components, the spiral-software install will copy the dependency code into its prefix
    • Another question about fftx package, specifically building with +rocm
    • Looking for the rocm packages with spack external find
    • Peter: create a how-to section on setting up external rocm packages
  • Yang: building openmpi with slurm
    • srun works, mpirun doesn't
    • Also running into a problem specifying an external slurm WRT pmix
      • Peter: either remove external slurm or add external pmix, if that doesn't work ping me
Clone this wiki locally