| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
* Add flag to enable WRF-Chem module
* Update var/spack/repos/builtin/packages/wrf/package.py
Co-authored-by: Tamara Dahlgren <35777542+tldahlgren@users.noreply.github.com>
* Set chem variant only for v4+
Co-authored-by: Tamara Dahlgren <35777542+tldahlgren@users.noreply.github.com>
|
|
|
|
pmix@:2 uses hwloc if it's available (e.g. in homebrew) which can break
the installation.
|
|
|
|
Anticipate openPMD-api changes in the next major release that are
already in `dev` (aka Spack `develop`):
- C++17 requirement
- drop: `mpark-variant` public dependency
- add: `toml11` private dependency
Also add @franzpoeschel as co-maintainer for the Spack package.
|
|
Fixes WarpX issues:
- https://github.com/ECP-WarpX/WarpX/pull/3134
- https://github.com/ECP-WarpX/WarpX/pull/3141
and uses GitHub patch URLs directly instead of storing
patch copies.
|
|
|
|
|
|
|
|
|
|
* Bump up the version for ROCm-5.1.3 release
* remove extra comma from hashes for device-libs of rocm-openmp-extras
|
|
Some systems have trouble when using the python on the login node so
this should provide an option to build that doesn't require running
python.
|
|
|
|
|
|
* Updated intel-gtpin package.py for most recent version, GTPin 3.0.
* Fixed style issues in package.py -- removed trailing whitespace on two
lines.
|
|
|
|
|
|
|
|
* nag: add new version
* nag: update maintainers
|
|
|
|
* Adding a libunwind variant to libzmq
* Remove whitespace line 46
|
|
* tmux: support building from master and utf8 opts
* Fix style errors
|
|
* Add rclone 1.58
* Update rclone git repo path
|
|
* gromacs: Add recent releases
* gromacs: Update branch name
* gromacs: Update links
|
|
|
|
* Add pugixml dependency
* Dependency updates
* Fix Spack Numpy verion
* Test more generous NumPy constraint
* Fix NumPy requirment
|
|
|
|
Co-authored-by: openCARP consortium <info@opencarp.org>
|
|
|
|
(#29945)
|
|
Updates to improve Spack-generated modules for Intel oneAPI compilers:
* intel-oneapi-compilers set CC etc.
* Add a new package intel-oneapi-compilers-classic which can be used to
generate a module which sets CC etc. to older compilers (e.g. icc)
* lmod module logic now updated to treat the intel-oneapi-compilers*
packages as compilers
|
|
* acts-dd4hep: new package, separated from new acts@19.1.0
* acts-dd4hep: improved versioning
* acts-dd4hep: don't use curl | sha256sum
* acts: new variant `odd` for Open Data Detector
* acts-dd4hep: style changes
|
|
|
|
dependency (#30938)
|
|
|
|
Set CC to cc
|
|
* Add new versions
* Updated the hashes to match the published pypi.org hashes. Added version constraints for Python.
|
|
|
|
|
|
Add two new stacks targeted at x86_64 and arm, representing an initial list of packages
used by current and planned AWS Workshops, and built in conjunction with the ISC22
announcement of the spack public binary cache.
Co-authored-by: Scott Wittenburg <scott.wittenburg@kitware.com>
|
|
Explicitly import package utilities in all packages, and corresponding fallout.
This includes:
* rename `spack.package` to `spack.package_base`
* rename `spack.pkgkit` to `spack.package`
* update all packages in builtin, builtin_mock and tutorials to include `from spack.package import *`
* update spack style
* ensure packages include the import
* automatically add the new import and remove any/all imports of `spack` and `spack.pkgkit`
from packages when using `--fix`
* add support for type-checking packages with mypy when SPACK_MYPY_CHECK_PACKAGES
is set in the environment
* fix all type checking errors in packages in spack upstream
* update spack create to include the new imports
* update spack repo to inject the new import, injection persists to allow for a deprecation period
Original message below:
As requested @adamjstewart, update all packages to use pkgkit. I ended up using isort to do this,
so repro is easy:
```console
$ isort -a 'from spack.pkgkit import *' --rm 'spack' ./var/spack/repos/builtin/packages/*/package.py
$ spack style --fix
```
There were several line spacing fixups caused either by space manipulation in isort or by packages
that haven't been touched since we added requirements, but there are no functional changes in here.
* [x] add config to isort to make sure this is maintained going forward
|
|
* Add amdblis and amdlibflame as BLAS/LAPACK options
* Add Cray-libsci as BLAS/LAPACK option
* Use Netlib config for Cray-libsci
|
|
|
|
* Call Numpy package's set_blas_lapack() and setup_build_environment() in Scipy package
* Remove broken link from comment
* Use .package attribute of spec to avoid import
|
|
|
|
|
|
This PR fixes several issues I noticed while trying to get Spack working on Apple M1.
- [x] `build_environment.py` attempts to add `spec['foo'].libs` and `spec['foo'].headers` to our compiler wrappers for all dependencies using a try-except that ignores `NoLibrariesError` and `NoHeadersError` respectively. However, The `libs` and `headers` attributes of the Python package were erroneously using `RuntimeError` instead.
- [x] `spack external find python` (used during bootstrapping) currently has no way to determine whether or not an installation is `+shared`, so previously we would only search for static Python libs. However, most distributions including XCode/Conda/Intel ship shared Python libs. I updated `libs` to search for both shared and static (order based on variant) as a fallback.
- [x] The `headers` attribute was recursively searching in `prefix.include` for `pyconfig.h`, but this could lead to non-deterministic behavior if multiple versions of Python are installed and `pyconfig.h` files exist in multiple `<prefix>/include/pythonX.Y` locations. It's safer to search in `sysconfig.get_path('include')` instead.
- [x] The Python installation that comes with XCode is broken, and `sysconfig.get_paths` is hard-coded to return specific directories. This meant that our logic for `platlib`/`purelib`/`include` where we replace `platbase`/`base`/`installed_base` with `prefix` wasn't working and the `mkdirp` in `setup_dependent_package` was trying to create a directory in root, giving permissions issues. Even if you commented out those `mkdirp` calls, Spack would add the wrong directories to `PYTHONPATH`. Added a fallback hard-coded to `lib/pythonX.Y/site-packages` if sysconfig is broken (this is what distutils always did).
|
|
|
|
|
|
Updated mfme constraints in laghos spackage to better match comments and
support legacy builds of `laghos@1.0:2.0`
|
