Telcon: 2016 06 02
- Todd Gamblin (LLNL)
- Benedikt Hegner (CERN)
- Ben Boeckel (Kitware)
- Dan Udwary (NERSC)
- Jim Galarowicz (Krell)
- Joseph Ciurej (LLNL)
- Mario Melara (NERSC)
- Matt Legendre (LLNL)
- Mike Collette (LLNL)
- Patrick Gartung (Fermi)
- Steve Leak (NERSC)
- Veronica Vergara (ORNL)
- Yang (??)
- BT (??)
- Todd back from travel this week
- Catching up with PRs
- Cray support nearly done github/NERSC/features/newarch
- Things remaining to do:
- A few remaining tweaks to the
spec.yaml
formatting. This changes hashes but ensures maintainability.
- more lazy binding on platform/os/etc. (too much currently being encoded in spec)
-
New
compilers.yaml
format:compilers: - compiler: spec: gcc@4.2.1 alias: 'gcc421' operating_system: elcappitan paths: cc: /usr/bin/gcc cxx: /usr/bin/g++ f77: null fc: null modules: []
-
Allows compiler descriptor to be self-contained, easily copied/reused.
-
A few small design tweaks
- A few remaining tweaks to the
- Build dependencies (#378) next large PR on the list after new architecture support.
- Sorry for delay on this one -- we needed to get Cray support out the door for NERSC and ORNL
- NERSC Spackathon!
- Todd Visited NERSC Tuesday, spent 2 hrs giving an overview of spack to consultant team.
- Nice to meet the NERSC consultants (10+ people)
- very envious of the view from Bldg 59.
- Mario Melara and others at NERSC helping to bootstrap the Cori phase II packaging effort
- NERSC has lots of good suggestions, setting up channels for support.
- Maybe get some ORNL folks involved?
- Eliminated a lot of importing and O(num package.py files) from Spack.
- See the PR description for details; still needs testing.
- On my mac, this brings concretization time for
dealii
down to ~5-6 sec, 3 sec withoutopenssl
(see next bullet)
- Current OpenSSL version check pings the OpenSSL site; this is problematic for a few reasons.
- Change
openssl
'surl_for_version
->_url_for_version
for a quick fix. - Slows down any concretization that has openssl (even things like
spack spec
that do not install) - Makes for kludgy code in
url_for_version
- See discussion here for proposed solutions.
- Compiler
LD_LIBRARY_PATH
issues
- Partially addressed by new compilers.yaml format in Cray support branch
- Allows modules
- Will add env options for custom
LD_LIBRARY_PATH
too (Per @hegner's #943)
- NERSC wants #908 too (customize install location)
- also wants to customize install tree layout
- views would be better
- Intel compiler installation (Greg Lee)
- RPM building (Matt, Peter)
- Archive caching (Peter)
- Kitware update (Ben, DJ)
- build deps rebased and squashed for develop
- DJ still working on Qt and UVCDAT
- Update from HEP team
- binary packaging (Gartung, Hegner)
- views (Viren)
- Sorry for delays on PRs -- hope to get them in faster.
- Others?
- @citibeth?
-
Mario Melara: update on NERSC's Spack workflow
-
NERSC consultants divvying up packages to maintain (10-ish people) 1. Work on packages in home directory 1. Install in
/usr/common
once working for a consultant. 1. First installing things with gcc & intel on haswell and KNL -
Potential issues/questions from consultants: 1. static vs dynamic linking on Cray
- Todd suggests handling this with
shared
variant 1. auto-generation of module files - every variant currently produces a module file
- LLNL in a similar situation with RPM-based system
- spack can build more than we want to "publish" to users
- took steps to decide whether a package is actually seen by users or "just installed"
- "published" packages have module files, others are just installed but no module generated.
1. changing the install prefix from
$spack/opt/spack
to something else
- In Benedikt's PR -- to be merged real soon.
1. consultant's spack build environment is breaking due to modules in
.bashrc
- Cray doesn't have a good way to get a vanilla environment
- Need a better way to get a basic environment without using
module purge
.- or tell users to unload all modules that depend on the PrgEnv
- Look into also omitting the user's
.bashrc
- could we just source the site-specific .bashrc
- Todd suggests handling this with
-
veronica trying to use Spack to build on a Power machine * Sqlite and can't understand that the machine is POWER * look in package.py files and grep for filter_file for examples of how to customize build files.
-
Joe Ciurej (LLNL): PR update 1. Better support for setup.py (ignoring user configuration) is ready to merge (PR #950) 1. Fetcher configuration
-
curl
on LC systems sometimes fail because curl does not support the progress bar - probably need a notion of fetch dependencies in Spack
-