| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
* methylcode: added package
* pyfasta: added package
* py-bsddb3: added package
* py-bsddb3: added package
* Update package.py
* Update package.py
* Update package.py
* removed fixme comments
* Update package.py
* Update package.py
* Update package.py
* Update package.py
* Update package.py
* Update package.py
* Update package.py
* Update package.py
|
|
As protobuf has been converted to CMakePackage, it doesn't have a 'shared' variant anymore.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Fixes a problem in ymake-filter: The line buffer is currently hardcoded to be
2048 bytes large but some Makefiles contain lines longer than that. This
caused the Makefiles to sometimes not be generated, consequently failing parts
of the build.
|
|
|
|
setup-env.sh adds the 'module' command to the user's environment
if it is not defined and if there is a Spack installation of
environment-modules available. This commit updates that logic to
perform these checks and updates quietly.
|
|
Added support for building NOX package to Trilinis Spackage
|
|
This fixes the build of the ADIOS package.
The `with_or_without` interface of the Autotools builds
seems to have changed, this fixes it.
|
|
* libsodium: update URLs
updates the URLs for libsodium releases.
Fixes broken builds (404).
* libsodium: add new version
|
|
* Added missing help2man dependency to nauty
* Add type=build
* Added gmp dependency to nauty package
|
|
Add sha of the latest boost bugfix release.
http://www.boost.org/users/history/version_1_65_1.html
Besides other fixed issues, it adds compatebility for the upcoming
CUDA 9 release.
|
|
On OSX, the shell detection code may get a preceding dash, like
"-bash". This adds a filter to remove it.
|
|
The correct place to set the mutual references between spec and
package objects is at the end of concretization. After a call to
concretize we should now be ensured that spec is the same object
as spec.package.spec.
Code in `build_environment.py` that was performing the same
operation has been turned into an assertion to be defensive on
the new behavior.
|
|
|
|
This also introduces the ssl, snappy and zlib variants for libmongoc.
|
|
|
|
* dealii: explicitly specify bzip2 libs
* bzip2: add libs() property
|
|
- Fixes bugs where concretization would fail due to an erroneously cached
_concrete attribute.
- Ripped out a bunch of code in spec.py that isn't needed/valid anymore:
- The various concrete() methods on different types of Specs would
attempt to statically compute whether the Spec was concrete.
- This dates back to when DAGs were simpler and there were no optional
dependencies. It's actually NOT possible to compute statically
whether a Spec is concrete now. The ONLY way you know is if it goes
through concretization and is marked concrete once that completes.
- This commit removes all simple concreteness checks and relies only on
the _concrete attribute. This should make thinking about
concreteness simpler.
- Fixed a couple places where Specs need to be marked concrete explicitly.
- Specs read from files and Specs that are destructively copied from
concrete Specs now need to be marked concrete explicitly.
- These spots may previously have "worked", but they were brittle and
should be explcitly marked anyway.
|
|
- Dependencies in concrete specs did not previously have their cache
fields (_concrete, _normal, etc.) preserved.
- _dup and _dup_deps weren't passing each other enough information to
preserve concreteness properly, so only the root was properly
preserved.
- cached concreteness is now preserved properly for the entire DAG, not
just the root.
- added method docs.
|
|
|
|
|
|
Fixes #4112
This commit extends the support of the AutotoolsPackage methods
`with_or_without` and `enable_or_disable` to bool-valued variants. It
also defines for those functions a convenience short-cut if the
activation parameter is the prefix of a spec (like in
`--with-{pkg}={prefix}`).
This commit also includes:
* Updates to viennarna and adios accordingly: they have been modified to
use `enable_or_disable` and `with_or_without`
* Improved docstrings in `autotools.py`. Raise `KeyError` if name is
not a variant.
|
|
|
|
|
|
* berkeley-db: initial commit
* berkeley-db: added more versions
|
|
|
|
These were discovered with bash 4.1.2.
Add quotations around a variable to prevent the destruction of a
newline. Without this fix a conditional doesn't work properly.
Remove square brackets around a conditional meant to be evaluated based
on the return code of a command. This wasn't working properly with an
old bash.
Fix a typo.
|
|
* fix armadillo macro expansions
- most compilers `#define linux 1`
- armadillo does raw pasting of include directories in code
- this means macro expansion of `linux-x86_64` -> `1-x86_64`
- new version, previous download url seems broken
- lib64 instead of lib?
- needs verification, was required for intel, works for others
* flake8: two spaces is modules, one for classes
* add some explanation of how the patch works
* use p1 patch file with -U0 to prepend undef linux
* armadillo v8.100.1
|
|
There are some opencv dependencies missing such as "core" that are mandatory in order to complete the caffe build.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Improve PDToolkit support for different compilers
PDT dependency of TAU profiler doesn't use CC, CXX eb variables and needs command line arguments for compiler identification. If we don't pass compiler id then it uses gcc and result in link time errors while building TAU. This patch fixes it; tested with PGI and Intel compilers.
|
|
|
|
* Improve caffe dependency detection with extra CMake flags
* lmdb and leveldb fix
|
|
|
|
|
|
|
|
* Fix name detection in HeaderList and LibraryList
* Add support for CUDA header files
|
|
Renames the existing bootstrap command to 'clone'. Repurposes
'spack bootstrap' to install packages that are useful to the
operation of Spack (for now this is just environment-modules).
For bash and ksh users running setup-env.sh, if a Spack-installed
instance of environment-modules is detected and environment modules
and dotkit are not externally available, Spack will define the
'module' command in the user's shell to use the environment-modules
built by Spack.
|
|
First, quote the environment variable values. Second, export the
variables. sorry, this is bourn-shell syntax. Happy to consider a
shell-independent way to do this, but spack is already using sh-like
"env=value"
|
|
* mlhka: new package
|
