![]() * add tensorflow Change-Id: Id778c68d148cc42f0b478a9d10a8f937cb54cdc6 * make bazel and tensorflow build Change-Id: Iae9005e8f4dcc8f1ed36ea9337d2430aeebb291f * fix flake8 Change-Id: Ib05529dd796eab4a8855a5d7775cc4efea8e479d * 2nd flake8 attempt Change-Id: I46224be3a374b2a65793048b0c5178ea64adbd78 * replace md5 sums with sha256 * add version 1.13.2 * bazel() -> bazel('build',... * specify versions of bazel dependency * build with CUDA * add TODOs * add more todo"s * improve enum34 dependency * py-future is a dependency as of v1.14 * Update var/spack/repos/builtin/packages/tensorflow/package.py Co-Authored-By: Adam J. Stewart <ajstewart426@gmail.com> * Update var/spack/repos/builtin/packages/tensorflow/package.py Co-Authored-By: Adam J. Stewart <ajstewart426@gmail.com> * Update var/spack/repos/builtin/packages/tensorflow/package.py Co-Authored-By: Adam J. Stewart <ajstewart426@gmail.com> * Update var/spack/repos/builtin/packages/tensorflow/package.py Co-Authored-By: Adam J. Stewart <ajstewart426@gmail.com> * enable nccl, cuda by default * explain patches * add todo * remove unnecessary copt_flag * use join * join argument must be an iterable * split long line; use same opts for non-cuda build * without opt flags, configure hangs * introduce build phases; re-arrange * undo mistake * restore unset tmp_path * as of v1.14, nccl_install_path is parsed correctly, hence change ...prefix.lib to ...prefix * now, version 1.14 compiles successfully with cuda * add version 2.1.0 * specify bazel dependency for version 2.1.0-rc0 * account for deprecated bazel opts for v2.1.0-rc0 * disable mkldnn contraction kernel * Flake8 fixes * md5 -> sha256 * Fix TF and TF-estimator version deps * Don't just comment out patch * Add myself as a maintainer * Patch py-astor to support newer py-setuptools * Add more versions and bazel version constraints * Add a build phase * Add note about configure interactivity * dev-build -> build-env * Disable iOS build * Use correct optimization flags * Add variants for all possible features * nccl isn't always a dependency * Specify correct dependency versions for each release * Libs may not be in lib or lib64 * Add py-opt-einsum package * Add newer version of py-protobuf * Add newer version of py-wrapt * Fix Python 2.6 syntax error * Code review * Set more env vars for older versions * Add more env vars, fix bazel versions, add conflicts * Fix config options * Specify version that support --config args * Add py-future dependency for Python 2 * Fix cuda config flag and compute capabilities * Fix installation on macOS, add unit tests * Override cuda variant default to True on non-macOS * Rename tensorflow to py-tensorflow * Has to extend something * Fix os.symlink call * convert cuda_arc values to capabilities * restore nccl prefix path for v1.13.1 * Revert to v2 * Remove extraneous period * Add new version of jdk/openjdk * More stable cuda_arch formatting * Fix bazel unit tests * Fix symlinking * Fix unit tests * +gcp by default until build error figured out |
||
---|---|---|
.github | ||
bin | ||
etc/spack/defaults | ||
lib/spack | ||
share/spack | ||
var/spack | ||
.codecov.yml | ||
.coveragerc | ||
.dockerignore | ||
.flake8 | ||
.flake8_packages | ||
.gitattributes | ||
.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
@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