Telcon: 2017 01 26 - spack/spack GitHub Wiki
Participants
Todd Gamblin (LLNL)
others TBD
News
NASA had a Spack tutorial yesterday (thanks Elizabeth!)
Spack v0.10 was released on the 17th.
Lots of bugfixes
New platform/os/target architecture support (has been in develop
for a while, but was not in 0.9.1
)
Spack is now on twitter @spackpm
Spack environments working group met yesterday, with some participants from the lsat telcon
Focuses on how to make the environment support in spack consistent (modules and otherwise)
How can we make it easier to deploy a development environment with Spack?
Build a large code, work on 4 packages, build again, etc.
Others welcome to add to the feedback there
Seems to be some consensus on what is needed to overhaul spack view
, spack setup
, and other commands.
We'll have another meeting and try to come up with potential interfaces.
Plan for v1.0
continues to focus on:
Testing!
Better concretization algorithm
Kiel Friedt has made a prototype spack test-suite
command for running combinatorial tests
Takes a YAML file as input describing tests to run (sort of like Travis CI build matrix)
Posts results to spack.io/cdash
Hoping to polish this for general use soon.
Let us know if you'd like to run a dashboard where you can post your test results.
Switched from coveralls to codecov for coverage
Has a nice Chrome plugin so you can see test coverage inline on GitHub
Feature highlights
As usual, check the pulse page to see what's going on
More detailed docs on using MPI in the packaging guide #2838
Updated packaging docs cover AutotoolsPackage
, CMakePackage
, MakefilePackage
classes #2780
Note that these new packages let you run build phases separately for packages that support it:
spack configure
spack build
spack install
etc.
Fixes to the spec
parser . You can now refer to specs by hash properly, e.g. python/1c3fba
Better support for xl_r compilers from IBM
xl_r is a separate compiler because it's more than just XL with different flags
Runtime libs are different for xl_r
than xl
, particularly for Fortran
Thanks to Adam Stewart and Elizabeth for many OCD fixes that help Spack be more consistent
Discussion
Tom Merrick: How do I pass flags to MPI compilers?
using cflags='-O3 -etc' in packages.yaml
, but not seeing the flags in the build log
Todd: compiler flags passed that way are injected within Spack's compiler wrappers, so you wouldn't see them in the build log.
You CAN see them by running spack -d install <package
. This will give you two log files in the current working directory, one with the input arguments to the compiler wrapper and one with the output arguments passed to the actual compiler. Diffing these files with some diff program that can do sub-line diffs will show you exactly what got added by Spack.
Todd uses opendiff
on his mac to do this.
🗂️ Page Index for this GitHub Wiki