d04ae9a2b4
* xSDK: a bundle/meta package that simple installs a series of packages with suitable specs This is based on struggles with previous attempts at such a bundler Funded-by: IDEAS Project: IDEAS/xSDK Time: 12 hours * PETSc needs c++11 when built with Trilinos * Added alquimia package * remove direct setting of cpp in petsc/package.py since it doesn't work on some systems. Funded-by: IDEAS Project: IDEAS/xSDK Time: .3 hours Reported-by: Mark A. Berrill <berrillma@ornl.gov> * provide the MPI compilers to PETSc configure with --with-cc etc instead of --with-mpi-dir Funded-by: IDEAS Project: IDEAS/xSDK * Spack bug fix issue #3144 String could contain /n which resulting in spack generating warning message to stderr on each use of compiler which configure interpreted as failing compiler Thanks-to: Mark A. Berrill <berrillma@ornl.gov> * Fixed alquimia package Alquimia expects PETSC_DIR and PETSC_ARCH to be defined, and refuses to install if they are not. Spack does not define PETSC_ ARCH, so Alquimia will not install. This patch does two things to fix the alquimia build: 1. A patch has been added to remove the dependency on PETSC_ARCH. 2. Alquimia currently depends on old versions of PETSc and pflotran. @ghammond86 updated the alquimia interfaces to use more recent versions, but his patch is still sitting in an alquimia pull request. As a result, the spack installer now uses his fork of alquimia. This is a temporary fix until his pull request is accepted. * Need to pass to Alquimia the MPI compilers, not the raw compilers Otherwise the PETSc tests do not produce executables that can run because they are not linked against MPI libraries Funded-by: IDEAS Project: IDEAS/xSDK Time: .5 hours * Add alquimia to xSDK build Funded-by: IDEAS Project: IDEAS/xSDK * Fix flake8 errors for xsdk packages * Add xsdk support for xsdk version xsdk-0.2.0 Note that currently it is just dummy code, but will eventually use a xsdk-0.2.0 tag for each package it installs. Funded-by: IDEAS Project: IDEAS/xSDK Time: .7 hours * Do not build Mumps by default for PETSc since it is not portable, for example to Cray Allow alquimia to accept PETSc even if the PETSc test executable cannot run since this is a problem on Cray. Reported-by: Alicia Marie Klinvex <amklinv@sandia.gov> * Add xsdk-0.2.0-rc1 tag for xsdk-0.2.0 installs * Switch alquimia download site back to standard location since they have incorporated Glenn Hammond's fixes Also it no longer needs the patch to the Alquimia cmake Funded-by: IDEAS Project: IDEAS/xSDK Reported-by: Sergi Molins Rafa <smolins@lbl.gov> * update hypre to use the latest release candidate for xsdk 0.2.0 Funded-by: IDEAS Project: IDEAS/xSDK Reported-by: Ulrike Meier Yang <yang11@llnl.gov> * Re-added patch to alquimia The patch was out of date and has been updated accordingly. * Added Tpetra-free option to Trilinos The Tpetra stack takes forever to build and is not used by any of the IDEAS teams, so there should be an option to disable it. I have added this option and updated the xSDK accordingly. I also disabled xSDKTrilinos in the xSDK, since none of the apps teams currently use it, and it's largely Tpetra-based. * Removed alquimia patch from develop version The patch has been incorporated into alquimia and is no longer necessary for the develop version. The tagged version has not been updated accordingly and still needs the patch for now. (When the tagged version gets updated, the patch does need to be removed from spack altogether, or it will break the build.) * Removed patch from alquimia It has been incorporated into alquimia, both the develop and rc2 tagged versions. The 0.2.0 version of alquimia has been updated to tag rc2 rather than rc1. * update xsdk-0.2.0 to depend on PETSc xsdk-0.2.0-rc2 which fixes for Apple xcode 8.3 Commit-type: bug-fix Funded-by: IDEAS Project: IDEAS/xSDK * import sys got lost in merge with develop * Update xsdk packages to use xsdk-0.2.0 tag Commit-type: feature Funded-by: IDEAS Project: ECP * Fixes for Flake8 note, had to ignore some long lines due to a single string * simple improvements to XDK packages as suggested by Spack pull request reviewers Commit-type: style-fix Funded-by: IDEAS Project: xSDK * Removed unneeded : after develop as requested by Denis Davydov in pull request review Commit-type: style-fix Funded-by: IDEAS Project: xSDK Thanks-to: Denis Davydov * Removed change that may not be needed due to updates in PETSc spack file such as using mpicc etc directly Commit-type: bug-fix Funded-by: IDEAS Project: xSDK Thanks-to: Adam J. Stewart * Do not turn on xSDKTrilinos for xSDK builds since it requires tpetra Commit-type: bug-fix Funded-by: IDEAS Project: xSDK * comment why MUMPS is disabled by default for PETSc so that others won't try to enable it when modifying petsc package next time Commit-type: documentation Funded-by: IDEAS Project: xSDK Thanks-to: Denis Davydov |
||
|---|---|---|
| bin | ||
| etc/spack/defaults | ||
| lib/spack | ||
| share/spack | ||
| var/spack | ||
| .codecov.yml | ||
| .coveragerc | ||
| .flake8 | ||
| .gitignore | ||
| .mailmap | ||
| .travis.yml | ||
| LICENSE | ||
| pytest.ini | ||
| README.md | ||
Spack is a package management tool designed to support multiple versions and configurations of software on a wide variety of platforms and environments. It was designed for large supercomputing centers, where many users and application teams share common installations of software on clusters with exotic architectures, using libraries that do not have a standard ABI. Spack is non-destructive: installing a new version does not break existing installations, so many configurations can coexist on the same system.
Most importantly, Spack is simple. It offers a simple spec syntax so that users can specify versions and configuration options concisely. Spack is also simple for package authors: package files are written in pure Python, and specs allow package authors to write a single build script for many different builds of the same package.
See the Feature Overview for examples and highlights.
To install spack and install your first package, make sure you have Python (2 or 3). Then:
$ git clone https://github.com/llnl/spack.git
$ cd spack/bin
$ ./spack install libelf
Documentation
Full documentation for Spack is the first place to look.
We've also got a Spack 101 Tutorial, so you can learn Spack yourself, or teach users at your own site.
See also:
- Technical paper and slides on Spack's design and implementation.
- Short presentation from the Getting Scientific Software Installed BOF session at Supercomputing 2015.
Get Involved!
Spack is an open source project. Questions, discussion, and contributions are welcome. Contributions can be anything from new packages to bugfixes, or even new core features.
Mailing list
If you are interested in contributing to spack, the first step is to join the mailing list. We're using a Google Group for this, and you can join it here:
Contributions
Contributing to Spack is relatively easy. Just send us a
pull request.
When you send your request, make develop the destination branch on the
Spack repository.
Your PR must pass Spack's unit tests and documentation tests, and must be PEP 8 compliant. We enforce these guidelines with Travis CI. To run these tests locally, and for helpful tips on git, see our Contribution Guide.
Spack uses a rough approximation of the Git
Flow
branching model. The develop branch contains the latest
contributions, and master is always tagged and points to the
latest stable release.
Authors
Many thanks go to Spack's contributors.
Spack was originally written by Todd Gamblin, tgamblin@llnl.gov.
Citing Spack
If you are referencing Spack in a publication, please cite the following paper:
- Todd Gamblin, Matthew P. LeGendre, Michael R. Collette, Gregory L. Lee, Adam Moody, Bronis R. de Supinski, and W. Scott Futral. The Spack Package Manager: Bringing Order to HPC Software Chaos. In Supercomputing 2015 (SC’15), Austin, Texas, November 15-20 2015. LLNL-CONF-669890.
Release
Spack is released under an LGPL license. For more details see the LICENSE file.
LLNL-CODE-647188