| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
* Fix python in views when python prefix is under a symlink
* Add todo for future generalization
|
|
|
|
* Add master branch as version to HPX package
* Remove C++98 option from HPX package
* Add option to turn off examples in HPX package
* Add MPI variant to HPX package
|
|
* New package py-cdsapi to access Climate Data Store for downloading climate and weather reanalysis data
* Improvements
|
|
* mfem: add version 4.0.0 (without cuda, raja, etc)
* mfem@4.0.0: add occa variant
* mfem@4.0.0: add raja variant
* Update package.py
* Update package.py
* Update package.py
* Update package.py
* Update package.py
|
|
|
|
|
|
* sundials: add version 5.0.0 and new variant
plus some cleanup
* sundiaks: fix formatting
* sundials: fix dependencies
|
|
|
|
Rename the `spack diy` command to `spack dev-build` to make the use case clearer.
The `spack diy` command has some useful functionality for developers using Spack to build their dependencies and configure/build/install the code they are developing. Developers do not notice it, partly because of the obscure name.
The `spack dev-build` command has a `-u/--until PHASE` option to stop after a given phase of the build. This can be used to configure your project, run cmake on your project, or similarly stop after any stage of the build the user wants. These options are analogous to the existing `spack configure` and `spack build` commands, but for developer builds.
To unify the syntax, we have deprecated the `spack configure` and `spack build` commands, and added a `-u/--until PHASE` option to the `spack install` command as well.
The functionality in `spack dev-build` (specifically `spack dev-build -u cmake`) may be able to supersede the `spack setup` command, but this PR does not deprecate that command as that will require slightly more thought.
|
|
|
|
* mysql: Use correct python command
python~pythoncmd does not provide a python symlink for python3, so make
sure we pick the right command.
* mysql: Adapt to build env changes
|
|
* hypre: Add new variants to expost existing features.
* hypre: Add new variants to expose existing features.
* hypre: Shorten description line.
* hypre: Add an explicit else clause to disable some features.
|
|
|
|
|
|
|
|
It seems that 3.4.2 includes a change that is supposed to fix parallel
builds (https://lists.gnu.org/archive/html/bug-bison/2019-08/msg00000.html).
Instead, it actually breaks it for me (with -j48) with errors such as:
```
mv: cannot stat 'examples/c/reccalc/scan.stamp.tmp': No such file or directory
Makefile:9323: recipe for target 'examples/c/reccalc/scan.stamp' failed
```
|
|
|
|
|
|
|
|
|
|
python~pythoncmd does not provide a python symlink for python3, so make
sure we pick the right command.
|
|
python~pythoncmd does not provide a python symlink for python3, so make
sure we pick the right command.
|
|
* Ace package. Initial commit
* Correcting header now with licence.
* Using sha256
* Making requested changes:removing import line, urls and checksums in one line, and making it an MakefilePackage.
* Removing extra line
|
|
python~pythoncmd does not provide a python symlink for python3, so make
sure we pick the right command.
|
|
* petsc: add version 3.12.1 [and variant: batch]
* fix test_prs_update_old_api errors
|
|
This PR ensures that environment activation sets all environment variables set by the equivalent `module load` operations, except that the spec prefixes are "rebased" to the view associated with the environment.
Currently, Spack blindly adds paths relative to the environment view root to the user environment on activation. Issue #12731 points out ways in which this behavior is insufficient.
This PR changes that behavior to use the `setup_run_environment` logic for each package to augment the prefix inspections (as in Spack's modulefile generation logic) to ensure that all necessary variables are set to make use of the packages in the environment.
See #12731 for details on the previous problems in behavior.
This PR also updates the `ViewDescriptor` object in `spack.environment` to have a `__contains__` method. This allows for checks like `if spec in self.default_view`. The `__contains__` operator for `ViewDescriptor` objects checks whether the spec satisfies the filters of the View descriptor, not whether the spec is already linked into the underlying `FilesystemView` object.
|
|
|
|
Boost iostream autodetects the compression libraries libzstd and
liblzma outside of the Spack environment.
This commit disables mentioned libraries. In the future if the
Spack zstd/lzma packages were added as dependencies of the Spack
Boost package, additional work could be done to build Boost with
the Spack-built versions of these libraries.
|
|
Update the documentation of the `endian_reverse` variant in ADIOS2.
The short description caused some confusion (for me) :-)
|
|
PS: The old versions do not work: it's likely that they changed git
history on submodules
|
|
* Default to Python 3
* Fix build with Intel compilers
|
|
* Add latest version of py-scikit-learn
* setup_environment -> setup_build_environment
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Add latest version of zstd
* setup_environment -> setup_build_environment
|
|
* sniffles: fix zlib header lookup directory.
* use bamtools and zlib to spack installed package.
* remove unneeded patch.
|
|
* add CMAKE Fortran MODDIR FLAG for Fujitsu compiler
* elsi:remove extra fix
|
|
|
|
|
|
For some reason, newer versions of qt fail to build because they cannot
find certain system libraries such as libatomic and libdl.
Leaving the qmake compiler set to gcc seems to fix the problem.
Fixes #13221
|
|
|
|
|
