summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2023-08-30llvm: fix for Flang variant due to exception handling (#36171)Pat McCormick1-1/+10
* The flang project does not support exceptions enabled in the core llvm library (and developer guidelines explicitly state they should not be used). For this reason, when the flang variant is selected, LLVM_ENABLE_EH needs to be disabled. In the current main branch of llvm (and thus future releases), enabling flang and setting LLVM_ENABLE_EH will cause the overall build to fail. * Update var/spack/repos/builtin/packages/llvm/package.py Co-authored-by: Harmen Stoppels <harmenstoppels@gmail.com> * fix syntax --------- Co-authored-by: Harmen Stoppels <harmenstoppels@gmail.com> Co-authored-by: Satish Balay <balay@mcs.anl.gov>
2023-08-30Windows: oneapi/msvc consistency (#39180)John W. Parent1-36/+145
Currently, OneAPI's setvars scripts effectively disregard any arguments we're passing to the MSVC vcvars env setup script, and additionally, completely ignore the requested version of OneAPI, defaulting to whatever the latest installed on the system is. This leads to a scenario where we have improperly constructed Windows native development environments, with potentially multiple versions of MSVC and OneAPI being loaded or called in the same env. Obviously this is far from ideal and leads to some fairly inscrutable errors such as overlapping header files between MSVC and OneAPI and a different version of OneAPI being called than the env was setup for. This PR solves this issue by creating a structured invocation of each relevant script in an order that ensures the correct values are set in the resultant build env. The order needs to be: 1. MSVC vcvarsall 2. The compiler specific env.bat script for the relevant version of the oneapi compiler we're looking for. The root setvars scripts seems to respect this as well, although it is less explicit 3. The root oneapi setvars script, which sets up everything else the oneapi env needs and seems to respect previous env invocations.
2023-08-30py-llvmlite: add Python version requirements (#39711)Adam J. Stewart1-16/+15
2023-08-30completion: make bash completion work in zshTodd Gamblin2-4/+32
`compgen -W` does not behave the same way in zsh as it does in bash; it seems not to actually generate the completions we want. - [x] add a zsh equivalent and `_compgen_w` to abstract it away - [x] use `_compgen_w` instead of `compgen -W`
2023-08-30completion: add alias handlingTodd Gamblin4-0/+103
Bash completion is now smarter about handling aliases. In particular, if all completions for some input command are aliased to the same thing, we'll just complete with that thing. If you've already *typed* the full alias for a command, we'll complete the alias. So, for example, here there's more than one real command involved, so all aliases are shown: ```console $ spack con concretise concretize config containerise containerize ``` Here, there are two possibilities: `concretise` and `concretize`, but both map to `concretize` so we just complete that: ```console $ spack conc concretize ``` And here, the user has already typed `concretis`, so we just go with it as there is only one option: ```console spack concretis concretise ```
2023-08-30Add `concretise` and `containerise` aliases for our UK usersTodd Gamblin3-2/+40
From a user: > Aargh. > ``` > ==> Error: concretise is not a recognized Spack command or extension command; check with `spack commands`. > ``` To make things easier for our friends in the UK, this adds `concretise` and `containerise` aliases for the `spack concretize` and `spack containerize` commands. - [x] add aliases - [x] update completions
2023-08-30[procps] New versions (#38650)Chris Green4-2/+70
* [procps] New versions 3.3.14, 3.3.3.15..3.3.17, 4.0.0..4.0.3 * Put upper bound on patch application * [Patch was merged](https://gitlab.com/procps-ng/procps/-/merge_requests/189) for upcoming 4.0.4.
2023-08-29py-parsl: add v2023.08.21 (#39642)Ryan Marcellino1-8/+19
* py-parsl: add v2023.08.21 * fix style * add missing deps
2023-08-29amg2023 package: cmake build (#39618)Dewi1-56/+24
Switch from makefile to CMake-based build. CMake support is currently in a specific branch of the amg2023 repo, so add this branch as a version in the package.
2023-08-29Upgrading py-pika versions (#39670)Loïc Pottier1-2/+13
* Upgraded py-pika versions Signed-off-by: Loïc Pottier <pottier1@llnl.gov> * Upgraded py-pika versions Signed-off-by: Loïc Pottier <pottier1@llnl.gov> * added variants and adding setuptools constraint Signed-off-by: Loïc Pottier <pottier1@llnl.gov> * missing setuptools for older versions Signed-off-by: Loïc Pottier <pottier1@llnl.gov> --------- Signed-off-by: Loïc Pottier <pottier1@llnl.gov>
2023-08-29libpng: add libs property (#39638)Adam J. Stewart1-0/+7
2023-08-29boxlib: Add BL_USE_PARTICLES cmake var (#39660)Tom Payerle1-0/+1
Set BL_USE_PARTICLES to 1, which should case boxlib build to include Particles classes according to CMakeLists.txt. This seems to fix #18172 The aforementioned error seems to occur in cmake phase while processing CMakeLists.txt in Src/C_ParticleLib, and appears to be due to the variable containing the list of src files for the add_library() call being empty unless BL_USE_PARTICLES is set to 1.
2023-08-29Added release 2023.08.25 (#39665)G-Ragghianti3-0/+11
2023-08-29[mathematica] added version 13.0.1 (#39675)Jen Herting1-0/+5
2023-08-29Jedwards/parallelio262 (#39676)Jim Edwards1-2/+3
* add parallelio@2.6.2 * add comments
2023-08-29justbuild: add v1.2.1 (#39679)Alberto Sartori1-1/+6
2023-08-29[py-tiktoken] added verison 0.3.1 (#39677)Jen Herting1-0/+1
2023-08-29py-torchmetrics: add v1.1.1 (#39685)Adam J. Stewart1-0/+1
2023-08-29mapl: Fix pflogger dependency (#39683)Matthew Thompson1-3/+3
2023-08-29[py-gradio] New package (#39304)Jen Herting1-0/+46
* [py-gradio] New package * [py-gradio] added deps from requirements.txt * [py-gradio] py-pillow -> pil
2023-08-29py-lightly: add v1.4.17 (#39686)Adam J. Stewart1-0/+1
2023-08-29py-distributed: use py-jinja2 versions from 2.10.3 (#39658)LydDeb1-1/+1
In depends_on py-jinja2, use versions from 2.10.3, instead of strict equality, according to the pyproject.toml of py-distributed 2023.4.1
2023-08-29Revert "Add style tool to fix fish file formatting (#39155)" (#39680)Harmen Stoppels5-434/+410
This reverts commit 70c71e8f935b3c5152036a993295df13c5fe69ca.
2023-08-29Automated git version fixes (#39637)Harmen Stoppels148-586/+1273
Use full length commit sha instead of short prefixes, to improve reproducibility (future clashes) and guard against compromised repos and man in the middle attacks. Abbreviated commit shas are expanded to full length, to guard against future clashes on short hash. It also guards against compromised repos and man in the middle attacks, where attackers can easily fabricate a malicious commit with a shasum prefix collision. Versions with just tags now also get a commit sha, which can later be used to check for retagged commits.
2023-08-29build(deps): bump sphinx from 7.2.3 to 7.2.4 in /lib/spack/docs (#39668)dependabot[bot]1-1/+1
Bumps [sphinx](https://github.com/sphinx-doc/sphinx) from 7.2.3 to 7.2.4. - [Release notes](https://github.com/sphinx-doc/sphinx/releases) - [Changelog](https://github.com/sphinx-doc/sphinx/blob/master/CHANGES) - [Commits](https://github.com/sphinx-doc/sphinx/compare/v7.2.3...v7.2.4) --- updated-dependencies: - dependency-name: sphinx dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-08-29build(deps): bump docker/setup-buildx-action from 2.9.1 to 2.10.0 (#39669)dependabot[bot]1-1/+1
Bumps [docker/setup-buildx-action](https://github.com/docker/setup-buildx-action) from 2.9.1 to 2.10.0. - [Release notes](https://github.com/docker/setup-buildx-action/releases) - [Commits](https://github.com/docker/setup-buildx-action/compare/4c0219f9ac95b02789c1075625400b2acbff50b1...885d1462b80bc1c1c7f0b00334ad271f09369c55) --- updated-dependencies: - dependency-name: docker/setup-buildx-action dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-08-29fmt: 10.1.1 (#39664)Harmen Stoppels1-0/+1
2023-08-28Add style tool to fix fish file formatting (#39155)Adam J. Stewart5-410/+434
2023-08-28modules: copy matched config to prevent bleed (#39421)Jonathon Anderson1-1/+1
2023-08-28Patch VTK to enable python 3.8 in VTK 8.2 (#38735)kwryankrattiger11-59/+413
* VTK: Add patch for python 3.8 support * CI: Re-enable VisIt in CI * Configure spec matrix for stack with VisIt * Add pugixml dep for 8.2.0 * Make VTK and ParaView consistent on proj dep * OpenMPI 3: provides MP support by default * Add details on proj dep in ParaView * Add python 3.8 to test mock repo * Patches to get VisIt VTK interface * CI: Disable VisIt with GUI in DAV
2023-08-28singularityce: arg handling fix (#39663)Brian Vanderwende1-2/+2
2023-08-28kokkos: avoid setting multiple `cuda_arch` (#38723)Loris Ercole1-5/+21
The kokkos package does not support building with cuda with multiple `cuda_arch`. An error is raised if multiple `cuda_arch` are specified.
2023-08-28mapl: add 2.40, deprecate old versions (#39615)Matthew Thompson1-21/+74
* Add MAPL 2.40, deprecated old versions * Undo some variant changes * style fixes * Make variants reflect Cmake options * Remove pnetcdf variant * Clean up depends_on
2023-08-28security: change `SECURITY.md` to recommend GitHub's private reporting (#39651)Todd Gamblin1-14/+16
GitHub's beta private security issue reporting feature is enabled on the Spack repo now, so we can change `SECURITY.md` to recommend using it instead of `maintainers@spack.io`. - [x] Update `SECURITY.md` to direct people to the GitHub security tab. - [x] Update working in `SECURITY.md` to say "last two major releases" with a link to the releases page, instead of explicitly listing release names. This way we don't have to update it (which we keep forgetting to do).
2023-08-28octopus: specify the scalapack library not the directory (#39109)Ashwin Kumar Karnad1-2/+2
* octopus: specify the scalapack library not the directory * octopus: use spec.scalapack.libs.ld_flags
2023-08-28GnuPG: add v2.4.3 (#39654)Massimiliano Culpo3-0/+3
Also updates a few dependencies
2023-08-28Fix a few issues with git versions / moving targets in packages (#39635)Harmen Stoppels8-7/+12
2023-08-28py-scikit-optimize: add v0.9.0 and move gptune patch (#38738)Jen Herting3-7/+9
Co-authored-by: liuyangzhuan <liuyangzhuan@gmail.com>
2023-08-28Remove mxnet from darwin aarch64 since theres no supported release (#39644)Harmen Stoppels1-2/+2
2023-08-28libarchive: use openssl by default (#39640)Harmen Stoppels1-1/+1
2023-08-28magma: add v2.7.2 (#39645)Stan Tomov1-0/+1
2023-08-28libarchive: new versions (#39646)Harmen Stoppels1-0/+2
2023-08-28libuv: add versions up to v1.46.0 (#39647)Harmen Stoppels1-0/+5
2023-08-27py-igraph: new package with version 0.10.6 (#39179)Christopher Christofi2-1/+64
2023-08-27llvm: ensure runtimes set rpaths (#39641)Nichols A. Romero1-1/+8
Ensure that CMAKE_INSTALL_RPATH_USE_LINK_PATH is propagated to sub-make when building runtimes.
2023-08-26External ROCm: add example configuration (#39602)Peter Scheibel2-0/+114
* add an example of an external rocm configuration * include more info * generalize section to all GPU support
2023-08-26CMake: add versions 3.26.4|5 and 3.27.* (#39628)John W. Parent1-0/+10
Co-authored-by: Harmen Stoppels <me@harmenstoppels.nl>
2023-08-26py-scipy: re-apply scipy/scipy#14935 workaround (#39555)Daryl W. Grunau1-3/+2
* re-apply scipy/scipy#14935 workaround * restrict to %intel and eliminate Version() check --------- Co-authored-by: Daryl W. Grunau <dwg@lanl.gov>
2023-08-26py-dask: use py-jinja2 versions from 2.10.3 (#39631)LydDeb1-1/+1
In depends_on py-jinja2, use versions from 2.10.3, instead of strict equality, according to the pyproject.toml of dask 2023.4.1
2023-08-26Update package.py (#39619)Tim Gymnich1-1/+3