54018b488a
``` 5 errors found in build log: 609 CXX mbpart.o 610 CXX quality.o 611 CXX umr.o 612 CXX merge.o 613 CXX parread.o 614 mbpart.cpp: In function 'int main(int, char**)': >> 615 mbpart.cpp:494:19: error: no match for 'operator<<' (operand types are 'std::ostream' {aka 'std::basic_ostream<char>'} and 'std::ostri ngstream' {aka 'std::__cxx11::basic_ostringstream<char>'}) 616 std::cerr << tmp_output_file << " : failed to write file." << std::endl; 617 ~~~~~~~~~~^~~~~~~~~~~~~~~~~~ 618 mbpart.cpp:494:19: note: candidate: 'operator<<(int, int)' <built-i n> 619 mbpart.cpp:494:19: note: no known conversion for argument 2 from 'std::ostringstream' {aka 'std::__cxx11::basic_ostringstream<char>' } to 'int' 620 In file included from /software/user_tools/centos-7.2.1511/cades-ns ed-spack/opt/spack/linux-centos7-x86_64/gcc-4.8.5/gcc-8.2.0-uc6sbum ioobdbkw4rwfyn2givi4nyvwq/include/c++/8.2.0/iterator:64, 621 from /software/user_tools/centos-7.2.1511/cades-ns ed-spack/var/spack/stage/moab-4.9.2-77uuzmj4ofb7z7vz6m25sftyks7p5do 7/spack-src/src/moab/Range.hpp:167, ... 886 /software/user_tools/centos-7.2.1511/cades-nsed-spack/opt/spack/lin ux-centos7-x86_64/gcc-4.8.5/gcc-8.2.0-uc6sbumioobdbkw4rwfyn2givi4ny vwq/include/c++/8.2.0/ostream:682:5: note: candidate: 'template<cla ss _Ostream, class _Tp> typename std::enable_if<std::__and_<std::__ not_<std::is_lvalue_reference<_Tp> >, std::__is_convertible_to_basi c_ostream<_Ostream>, std::__is_insertable<typename std::__is_conver tible_to_basic_ostream<_Tp>::__ostream_type, const _Tp&, void> >::v alue, typename std::__is_convertible_to_basic_ostream<_Tp>::__ostre am_type>::type std::operator<<(_Ostream&&, const _Tp&)' 887 operator<<(_Ostream&& __os, const _Tp& __x) 888 ^~~~~~~~ 889 /software/user_tools/centos-7.2.1511/cades-nsed-spack/opt/spack/lin ux-centos7-x86_64/gcc-4.8.5/gcc-8.2.0-uc6sbumioobdbkw4rwfyn2givi4ny vwq/include/c++/8.2.0/ostream:682:5: note: template argument dedu ction/substitution failed: 890 /software/user_tools/centos-7.2.1511/cades-nsed-spack/opt/spack/lin ux-centos7-x86_64/gcc-4.8.5/gcc-8.2.0-uc6sbumioobdbkw4rwfyn2givi4ny vwq/include/c++/8.2.0/ostream: In substitution of 'template<class _ Ostream, class _Tp> typename std::enable_if<std::__and_<std::__not_ <std::is_lvalue_reference<_Tp> >, std::__is_convertible_to_basic_os tream<_Ostream>, std::__is_insertable<typename std::__is_convertibl e_to_basic_ostream<_Tp>::__ostream_type, const _Tp&, void> >::value , typename std::__is_convertible_to_basic_ostream<_Tp>::__ostream_t ype>::type std::operator<<(_Ostream&&, const _Tp&) [with _Ostream = std::basic_ostream<char>&; _Tp = std::__cxx11::basic_ostringstream <char>]': 891 mbpart.cpp:494:22: required from here >> 892 /software/user_tools/centos-7.2.1511/cades-nsed-spack/opt/spack/lin ux-centos7-x86_64/gcc-4.8.5/gcc-8.2.0-uc6sbumioobdbkw4rwfyn2givi4ny vwq/include/c++/8.2.0/ostream:682:5: error: no type named 'type' in 'struct std::enable_if<false, std::basic_ostream<char>&>' 893 CXXLD mbdepth 894 CXXLD hexmodops >> 895 make[2]: *** [mbpart.o] Error 1 896 make[2]: *** Waiting for unfinished jobs.... 897 make[2]: Leaving directory `/localscratch/tmp/s3j-spack/spack-stage /spack-stage-NT13kT/spack-src/tools' >> 898 make[1]: *** [all-recursive] Error 1 899 make[1]: Leaving directory `/localscratch/tmp/s3j-spack/spack-stage /spack-stage-NT13kT/spack-src/tools' >> 900 make: *** [all-recursive] Error 1 ``` |
||
---|---|---|
.github | ||
bin | ||
etc/spack/defaults | ||
lib/spack | ||
share/spack | ||
var/spack | ||
.codecov.yml | ||
.coveragerc | ||
.dockerignore | ||
.flake8 | ||
.flake8_packages | ||
.gitignore | ||
.mailmap | ||
.readthedocs.yml | ||
.travis.yml | ||
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
@mention
us!
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