28e7248b06
* Add Tophat v2.1.2, fixes automake issues The Tophat team merged the patch from https://github.com/spack/spack/pull/8244 and release v2.1.2 This change requires the old automake if you're building the older release and is relaxed about the automake it requires if you're building the v2.1.2 release. Building v2.1.1 and v2.1.2 works on a CentOS 7 system, I don't have the necessary bit to actually test the resulting binaries. Here's the commit note from the change that was ultimately merged upstream. Fixes #8025 > Tophat was failing to build with automake@1.16.1, it worked with the > older automake@1.15.1. This commit adds a patch to Tophat's > src/Makefile.am which cleans up a few things. The result builds > successfully with both automake@1.15.1 and automake@1.16.1. I have no > way to check that the resulting builds Do The Right Thing. > > It changes two things: > > the original Makefile.am had a rule for $(SAMPROG) with no > actions, and since there was a directory there with a tempting name > the newer automake was trying to do something with it, but lacked > the appropriate clues. Since that target is actually made as a side > effect of making the library (sigh...), it seems to work to just > give that rule something harmless to do (the Peter Principle > triumphs again...). > > a bunch of the targets need a libtophat.a and libgc.a; the older > automake was probably able to guess what to do given the list of > sources but the newer automake apparently won't make the necessary > assumptions. This patch wires up a simple rule and cleans up the > appropriate dependencies so that things work. > > While it may appear that I'm someone who understands automake, keep in > mind that I only play such a person on a TV reality show. YMMV. * Remove extraneous when constraint |
||
|---|---|---|
| bin | ||
| etc/spack/defaults | ||
| lib/spack | ||
| share/spack | ||
| templates | ||
| var/spack | ||
| .codecov.yml | ||
| .coveragerc | ||
| .flake8 | ||
| .flake8_packages | ||
| .gitignore | ||
| .mailmap | ||
| .travis.yml | ||
| CODE_OF_CONDUCT.md | ||
| conftest.py | ||
| CONTRIBUTING.md | ||
| issue_template.md | ||
| LICENSE | ||
| NOTICE | ||
| pytest.ini | ||
| 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 libelf
Documentation
Full documentation for Spack is the first place to look.
Try the Spack Tutorial, to learn how to use spack, write packages, or deploy packages for users at your 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, join the mailing list. We're using Google Groups for this:
Slack channel
Spack has a Slack channel where you can chat about all things Spack:
Sign up here to get an invitation mailed to you.
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 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.
Release
Spack is released under an LGPL license. For more details see the NOTICE and LICENSE files.
LLNL-CODE-647188