Skip to content
Todd Gamblin edited this page Sep 10, 2015 · 7 revisions

Participants

  • Todd Gamblin (LLNL)
  • Mike Collette (LLNL)
  • Gregory Becker (LLNL)

News

New contributions & suggestions

  • From Justin Too (ROSE compiler team):
  • From Rasmus Wriedt Larsen:
  • Multiple requests lately for Lmod support and module hierarchies (from CINECA and U. Pitt.)
    • Timo Bremer at LLNL has started getting Lmod packaged, maybe others.
    • If others want to work on this I'm happy to help answer questions.
    • Would be very useful in general; need something like it for Cray machines too.

Bugs

  • LLNL NextGen code team was able to resolve environment issues on Rhea at ORNL
    • Issues with LD_LIBRARY_PATH
    • Issues with ccache getting included in the environment turned out to be user's environment
      • Might need a command-line switch to enable/disable user environment inclusion in the build.
      • Let people get things built, then focus on how to make it reproducible.
  • Another long path issue for installed Python scripts
    • Greg Lee reported similar issue previously
    • What are some good ways to deal with this? Can't really do much about a long spack prefix.
      • could consider reducing opt/spack part of prefix in Spack.
      • Could shorten human-readable compiler and arch prefix, but it is useful for understanding install layout
      • Need to move more variants into hash.
    • System installs should probably be someplace short!
      • /spack?
      • /usr/tce (for TOSS3)?

Open Discussion

  • The Spack telcon is open; all are welcome to ask questions!

  • Mike had a rough week with Spack

    • Getting flags synched among packages is still difficult and needs to be changed in too many places.
    • Need C99 flags and consolidated flags for compilers
  • Mike still needs better boost package testing

    • Boost package needs to pass proper toolkit to non-GNU compilers
    • Wants to be able to build consistently (currently depends_on('boost%gcc'))
  • Jim still waiting on PR integration for O|SS

    • Not sure that the next release of O|SS can use Spack as installer w/o:
      • external packages
      • module prereqs
    • One after that maybe.
    • Spack support can proceed separately from O|SS release and replace existing installer when it's ready.
Clone this wiki locally