Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
* Fix mercurial print_str failure.
* Perform same fix on py-pybind11 for print_string missing method.
Co-authored-by: Nicholas Cameron Sly <sly1@llnl.gov>
|
|
|
|
|
|
* Add new root versions and associated dependency constraints
* Please style guide
* Avoid conflicts where possible
* Untested prototype of macOS version detection
* Fixes for macOS version prototype
* More logical ordering
* More correctness and style fixes
* Try to use spack's macos_version
* Add some forgotten @s
* Actually, Spack can't build Python 3.6 anymore, and thus no older PyROOT
Co-authored-by: Seth R. Johnson <johnsonsr@ornl.gov>
|
|
* pip/wheel/setuptools: extend PythonExtension
* Base class still required
|
|
* Fix compile errors with latest HDF5 1.13.3
* format
* Update var/spack/repos/builtin/packages/hdf5-vol-async/package.py
Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com>
Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com>
|
|
This commit reworks the bootstrapping procedure to use Spack environments
as much as possible.
The `spack.bootstrap` module has also been reorganized into a Python package.
A distinction is made among "core" Spack dependencies (clingo, GnuPG, patchelf)
and other dependencies. For a number of reasons, explained in the `spack.bootstrap.core`
module docstring, "core" dependencies are bootstrapped with the current ad-hoc
method.
All the other dependencies are instead bootstrapped using a Spack environment
that lives in a directory specific to the interpreter and the architecture being used.
|
|
|
|
|
|
* slightly raise tolerance of some tests
|
|
|
|
replaced the reference to the undefined "bindir" variable with prefix.bin
|
|
* pharokka and py-phanotate: new packages
* move libxcrypt edit
I don't need libxcrypt when not building dev infernal. Moving to a different PR
|
|
Co-authored-by: teachers-uk-net <stuart.morrison@kcl.ac.uk>
|
|
The cray manifest shows dependency information for cray-mpich, which we never previously cared about
because it can only be used as an external. This updates Spack's dependency information to make cray-mpich
specs read in from the cray external manifest usable.
|
|
Signed-off-by: Loïc Pottier <pottier1@llnl.gov>
Co-authored-by: Massimiliano Culpo <massimiliano.culpo@gmail.com>
|
|
|
|
|
|
* initial changes for rocm recipes
* drop support for older releases
* drop support for older rocm releases - add more recipes
* drop support for older releases
* address style issues
* address style error
* fix errors
* address review comments
|
|
* Added plumed version 2.8.1 including gromacs compatibility
* Corrected ~mpi and +mpi variants in new depends
* Fixed regression logic plumed+gromacs@2020.6 support
|
|
* LAMMPS: Add version 20220803 and 20220623.1
* LAMMPS: Add 20220915, 20221103, and 20220623.2
|
|
The 0.9.0-beta requires yaml-cpp for parsing the configuration file format in YAML.
P.S. I'm using https://www.conventionalcommits.org/en/v1.0.0/#specification for this commit message.
|
|
* epsic: add epsic package to spack
* psrcat: add psrcat to spack
* psrchive: add psarchive to spack
* tempo: add tempo package to spack
|
|
See release notes at https://github.com/potassco/clingo/releases/tag/v5.6.2
|
|
* Add the very first version of cernlib
* Update package.py
* Update package.py
Co-authored-by: Andrii Verbytskyi <andriish@pcatlas18.mpp.mpg.de>
|
|
* py-nbclassic: add 0.4.8 and new package py-notebook-shim
* Add missing dependencies
|
|
|
|
Co-authored-by: sxs-bot <sxs-bot@users.noreply.github.com>
|
|
|
|
|
|
|
|
|
|
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
|
|
|
|
|
|
* Add conflicts with gcc@12.2.0
* Add more links for reference
|
|
* py-mne: add 1.2.2 and depencendy packages
* py-mne: add 1.2.3
* Remove unnecessary when statement
|
|
|
|
|
|
|
|
|
|
* doxygen: add build-tool tag
This allows it to be included automatically as an external. No one links against doxygen so this should be ok.
* doxygen: add self as maintainer
|
|
* vecgeom: add new 1.2.1 version
* vecgeom: introduce conflict between gcc/cuda
Recent tests of vecgeom in Spack environments have shown that the build
with +cuda fails with GCC >= 11.3 and CUDA < 11.7 with error
...lib/gcc/x86_64-pc-linux-gnu/11.3.0/include/serializeintrin.h(41):
error: identifier "__builtin_ia32_serialize" is undefined
1 error detected in the compilation of
".../VecGeom/source/BVHManager.cu".
Other GCC/CUDA combinations appear o.k.
Avoid this error in spack, and document it for users, with a conflict
directive to express the restriction.
|
|
|
|
|
|
* py-alphafold: update to 2.2.4, update dependencies
* style
|
|
|
|
conditional variants (#34244)
* ROOT: add GSL/math dependency
* ROOT: use conditional variants instead of conflicts
|
|
|