| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
Co-authored-by: github-actions <github-actions@users.noreply.github.com>
|
|
* zfp: updates and many fixes for version 1.0.0
Co-authored-by: Bernhard Kaindl <43588962+bernhardkaindl@users.noreply.github.com>
|
|
- enable sundials+magma+ginkgo
- enable dealii+sundials
- disable dealii~cgal due to build errors
- enable petsc+rocm
- enable slepc+cuda+rocm
- enable strumpack+cuda+slate
- enable slate build with non-gcc compilers
- enable pumi+shared
- enable mfem+shared
- enable ginkgo+mpi
- add hiop
- and exago
- use exago~ipopt due to mumps~mpi conflict with mpi.h)
- add raja variant [used by exago/hiop]
~raja builds exago in pflow-only mode - i.e exago~hiop~ipopt~python~cuda ^hiop~cuda [Default on MacOS]
Co-authored-by: Cody Balos <balos1@llnl.gov>
|
|
* Update BML versions list in package.py
* Update package.py
|
|
Co-authored-by: sxs-bot <sxs-bot@users.noreply.github.com>
|
|
|
|
* New Package: Prime95/Mprime
* Fix trailing whitespaces in prime95
* Fix checksum for prime95
Signed-off-by: saqibkh <saqibkhan@utexas.edu>
|
|
|
|
We need Python 3.0:3.9
|
|
* thepeg: make rivet dependency optional...
* add "libs" variant, move compiler flags to flag_handler
Co-authored-by: iarspider <iarspider@users.noreply.github.com>
|
|
Revamp the timer so we always have a designated begin and end.
Fix a bug where the phase timer was stopped before the phase started,
resulting in incorrect timing reports in timers.json.
|
|
|
|
|
|
Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com>
|
|
This reverts commit bf1b2a828c61fb465f7641b6230fef4f17867162, as libxcrypt's configure script requires Perl, leading to a circular dependency.
|
|
|
|
Error message:
```
ModuleNotFoundError: No module named 'setuptools'
```
Co-authored-by: Stephen Sachs <stesachs@amazon.com>
|
|
|
|
* Ginkgo 1.5.0 release, new MPI variant
* Fix ROCTHRUST/ROCPRIM issues
* Fix deal.II issue with Ginkgo 1.5.0
* Also fix hipRAND+rocRAND RPATH settings
* Turn off CCACHE for spack builds.
Co-authored-by: Veselin Dobrev <dobrev@llnl.gov>
Co-authored-by: Veselin Dobrev <dobrev@llnl.gov>
|
|
|
|
|
|
Detected using https://github.com/spack/spack/pull/28109
|
|
|
|
|
|
* Remove CI jobs related to Python 2.7
* Remove Python 2.7 specific code from Spack core
* Remove externals for Python 2 only
* Remove llnl.util.compat
|
|
|
|
|
|
|
|
|
|
* GDAL: add v3.6.0
* Explicitly control BASISU
* More reasonable variant defaults
|
|
|
|
[dealii] force cmake to accept Scalapack settings from Spack
|
|
|
|
* Update ExaGO for 1.5.0 release
|
|
* magma: add version 2.7.0
Co-authored-by: Stan Tomov <tomov@icl.utk.edu>
|
|
|
|
* libxcrypt: 4.4.30
* libxcrypt.so.2 by default
* add libs prop, since libxcrypt provides libcrypt
|
|
* ParaView: Add variant for VisItBridge
* ParaView: Add kwryankrattiger has package maintainer
|
|
|
|
And update dependency on superlu-dist (now works with @8)
|
|
Environments and environment views have taken over the role of `spack activate/deactivate`, and we should deprecate these commands for several reasons:
- Global activation is a really poor idea:
- Install prefixes should be immutable; since they can have multiple, unrelated dependents; see below
- Added complexity elsewhere: verification of installations, tarballs for build caches, creation of environment views of packages with unrelated extensions "globally activated"... by removing the feature, it gets easier for people to contribute, and we'd end up with fewer bugs due to edge cases.
- Environment accomplish the same thing for non-global "activation" i.e. `spack view`, but better.
Also we write in the docs:
```
However, Spack global activations have two potential drawbacks:
#. Activated packages that involve compiled C extensions may still
need their dependencies to be loaded manually. For example,
``spack load openblas`` might be required to make ``py-numpy``
work.
#. Global activations "break" a core feature of Spack, which is that
multiple versions of a package can co-exist side-by-side. For example,
suppose you wish to run a Python package in two different
environments but the same basic Python --- one with
``py-numpy@1.7`` and one with ``py-numpy@1.8``. Spack extensions
will not support this potential debugging use case.
```
Now that environments are established and views can take over the role of activation
non-destructively, we can remove global activation/deactivation.
|
|
even on newer releases of ROCm. (#33772)
|
|
|
|
|
|
Co-authored-by: Seth R. Johnson <johnsonsr@ornl.gov>
|
|
* redis-plus-plus: added initial support
* redis-plus-plus: use cmake arg provided by Spack
* redis-plus-plus: oups tiny typo
Signed-off-by: Loïc Pottier <pottier1@llnl.gov>
Signed-off-by: Loïc Pottier <lpottier@arnor>
Co-authored-by: Loïc Pottier <lpottier@arnor>
|
|
|
|
Co-authored-by: Matthew Lieber <lieber.31@osu.edu>
|
|
xsdk-examples: deprecate @0.2.0, remove @0.1.0 in sync with older xsdk releases
|
