Spack packaging for inclusion E4S

Issue #218 resolved
Paul Hargrove created an issue

ECP is using "The Extreme-scale Scientific Software Stack" (http://e4s.io)as its vehicle for distributing ECP software to participants and to external parties. It includes a Spack package repository containing configuration to build/install the software, plus container-based distributions of the installed software.

A short article is here.

We have been absent from the first two public releases of E4S and are not even on the "Future" list in the current release notes. This should be resolved as soon as practical.

The plan is to use the "offline" tarball which packages UPC++ and GASNet-EX. GASNet-EX will not have a separate package at this stage (use by Legion creates complications).

Initially it seems sufficient to build only for the default compiler (clang on macOS, gcc on Linux, and on Cray systems cross-compile with the wrapper compilers and the then-current PrgEnv). However, going forward we could pursue supporting multiple compilers/PrgEnv's installed on the same host (this is one of Spack's distinguishing features when compared to something like Homebrew).

Comments (4)

  1. Dan Bonachea

    The Spack pull-request into the upstream repo is here.

    We expect this to be merged into the main Spack repo today.

    The next step is for Paul to contact Sameer Shende and get it added to the E4S package list. This should happen ASAP to ensure we are included in the E4S release 0.3, which is expected to be finalized in November.

  2. Dan Bonachea

    The Spack PR has been merged and email communication from the E4S guys seems to indicate UPC++ should be included in the next E4S release.

    UPC++/GASNet-EX are now listed on the E4S package page

  3. Log in to comment