93e87474fb
Verification builds on LANL Darwin x86_64, ARM, and, Power9: x86_64: OPTANE dantopa@cn733:pr-openmpi-4.0.2.spack $ spack arch linux-centos7-skylake_avx512 $ spack install openmpi @ 4.0.2 % gcc @ 4.8.5 ... ==> Installing openmpi ... ==> Successfully installed openmpi Fetch: 2m 15.65s. Build: 6m 13.17s. Total: 8m 28.82s. [+] /scratch/users/dantopa/new-spack/pr-openmpi-4.0.2.spack/opt/spack/linux-centos7-haswell/gcc-4.8.5/openmpi-4.0.2-jrypg7vfnk6nl5if2rnzt65wdrjelxsq NEHALEM $ spack arch linux-centos7-nehalem $ spack install openmpi @ 4.0.2 % gcc @ 4.8.5 ... ==> Installing openmpi ... ==> Successfully installed openmpi Fetch: 50.48s. Build: 9m 11.45s. Total: 10m 1.93s. [+] /scratch/users/dantopa/new-spack/pr-openmpi-4.0.2.spack/opt/spack/linux-centos7-nehalem/gcc-4.8.5/openmpi-4.0.2-4jz3bcwjci44taizt4jqzxqh4y75uswc ARM $ spack arch linux-rhel7-aarch64 $ spack install openmpi @ 4.0.2 % gcc @ 4.8.5 ... ==> Installing openmpi ... ==> Successfully installed openmpi Fetch: 1m 10.47s. Build: 11m 41.45s. Total: 12m 51.92s. [+] /scratch/users/dantopa/new-spack/pr-openmpi-4.0.2.spack/opt/spack/linux-rhel7-aarch64/gcc-4.8.5/openmpi-4.0.2-ygr77roadqzdnsdgqz3uactjqnb5nayn POWER9 $ spack arch linux-rhel7-power9le $ spack install openmpi @ 4.0.2 % gcc @ 4.8.5 ==> Warning: Using GCC 4.8 to optimize for Power 8 might not work if you are not on Red Hat Enterprise Linux 7, where a custom backport of the feature has been done. Upstream support from GCC starts in version 4.9 ... ==> Installing openmpi ... ==> Successfully installed openmpi Fetch: 23.95s. Build: 9m 7.67s. Total: 9m 31.62s. [+] /scratch/users/dantopa/new-spack/pr-openmpi-4.0.2.spack/opt/spack/linux-rhel7-power8le/gcc-4.8.5/openmpi-4.0.2-cid4wfzr2iwgz6ybhkexludwu7koi266 $ spack find -ldf openmpi ==> 4 installed packages -- linux-centos7-haswell / gcc@4.8.5 ---------------------------- jrypg7v openmpi@4.0.2%gcc lliismp hwloc@1.11.11%gcc 7dqpxas libpciaccess@0.13.5%gcc viidrh5 libxml2@2.9.9%gcc yhvj3br numactl@2.0.12%gcc pkmj6e7 zlib@1.2.11%gcc -- linux-centos7-nehalem / gcc@4.8.5 ---------------------------- 4jz3bcw openmpi@4.0.2%gcc pcauu6w hwloc@1.11.11%gcc yiqf6bj libpciaccess@0.13.5%gcc wpfgqf2 libxml2@2.9.9%gcc fd2xpnm numactl@2.0.12%gcc xguzaxf zlib@1.2.11%gcc -- linux-rhel7-aarch64 / gcc@4.8.5 ------------------------------ ygr77ro openmpi@4.0.2%gcc omy3xi2 hwloc@1.11.11%gcc 6a4he35 libpciaccess@0.13.5%gcc txqo4cc libxml2@2.9.9%gcc m5neuus numactl@2.0.12%gcc 67s2oqn zlib@1.2.11%gcc -- linux-rhel7-power8le / gcc@4.8.5 ----------------------------- cid4wfz openmpi@4.0.2%gcc zcdnwb3 hwloc@1.11.11%gcc lencfon libpciaccess@0.13.5%gcc bve4jop libxml2@2.9.9%gcc kajzqwg numactl@2.0.12%gcc tjbynt2 zlib@1.2.11%gcc Thu Oct 17 19:02:50 MDT 2019 Signed-off-by: Daniel Topa <dantopa@lanl.gov> |
||
|---|---|---|
| .github | ||
| bin | ||
| etc/spack/defaults | ||
| lib/spack | ||
| share/spack | ||
| var/spack | ||
| .codecov.yml | ||
| .coveragerc | ||
| .dockerignore | ||
| .flake8 | ||
| .flake8_packages | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .mailmap | ||
| .readthedocs.yml | ||
| .travis.yml | ||
| CHANGELOG.md | ||
| COPYRIGHT | ||
| LICENSE-APACHE | ||
| LICENSE-MIT | ||
| NOTICE | ||
| README.md | ||
Spack
Spack is a multi-platform package manager that builds and installs multiple versions and configurations of software. It works on Linux, macOS, and many supercomputers. Spack is non-destructive: installing a new version of a package does not break existing installations, so many configurations of the same package can coexist.
Spack offers a simple "spec" syntax that allows users to specify versions and configuration options. Package files are written in pure Python, and specs allow package authors to write a single script for many different builds of the same package. With Spack, you can build your software all the ways you want to.
See the Feature Overview for examples and highlights.
To install spack and your first package, make sure you have Python. Then:
$ git clone https://github.com/spack/spack.git
$ cd spack/bin
$ ./spack install zlib
Documentation
Full documentation is available, or
run spack help or spack help --all.
Tutorial
We maintain a hands-on tutorial. It covers basic to advanced usage, packaging, developer features, and large HPC deployments. You can do all of the exercises on your own laptop using a Docker container.
Feel free to use these materials to teach users at your organization about Spack.
Community
Spack is an open source project. Questions, discussion, and contributions are welcome. Contributions can be anything from new packages to bugfixes, documentation, or even new core features.
Resources:
- Slack workspace: spackpm.slack.com. To get an invitation, click here.
- Mailing list: groups.google.com/d/forum/spack
- Twitter: @spackpm. Be sure to
@mentionus!
Contributing
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.
Code of Conduct
Please note that Spack has a Code of Conduct. By participating in the Spack community, you agree to abide by its rules.
Authors
Many thanks go to Spack's contributors.
Spack was created 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.
License
Spack is distributed under the terms of both the MIT license and the Apache License (Version 2.0). Users may choose either license, at their option.
All new contributions must be made under both the MIT and Apache-2.0 licenses.
See LICENSE-MIT, LICENSE-APACHE, COPYRIGHT, and NOTICE for details.
SPDX-License-Identifier: (Apache-2.0 OR MIT)
LLNL-CODE-647188