forked from spack/spack
-
Notifications
You must be signed in to change notification settings - Fork 14
Update spack-stack-dev from spack develop a9c879d #534
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
climbfuji
wants to merge
1,581
commits into
JCSDA:spack-stack-dev
Choose a base branch
from
climbfuji:feature/update_spack_stack_dev_from_spack_a9c879d
base: spack-stack-dev
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Update spack-stack-dev from spack develop a9c879d #534
climbfuji
wants to merge
1,581
commits into
JCSDA:spack-stack-dev
from
climbfuji:feature/update_spack_stack_dev_from_spack_a9c879d
+57,951
−46,909
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Update py-psyclone package.py to refer to 3.1.0 release * Fix hash for 3.1.0 tarball
Signed-off-by: Loic Pottier <pottier1@llnl.gov>
* oniguruma: add v6.9.10 * oniguruma: update url to trigger ci
…#49385) When requiring a constraint on a virtual package, it makes little sense to use anonymous specs, and our documentation shows no example of requirements on virtual packages starting with `^`. Right now, due to how `^` is implemented in the solver, writing: ```yaml mpi: require: "^openmpi" ``` is equivalent to the more correct form: ```yaml mpi: require: "openmpi" ``` but the situation will change when `%` will shift its meaning to be a direct dependency. To avoid later errors that are both unclear, and quite slow to get to the user, this commit makes anonymous specs under virtual requirements an error, and shows a clear error message pointing to the file and line where the spec needs to be changed. Signed-off-by: Massimiliano Culpo <massimiliano.culpo@gmail.com>
* Include OpenMP support * Add many new versions of NCO * Add maintainers --------- Co-authored-by: Xylar Asay-Davis <xylarstorm@gmail.com>
In Spack v1.0 we plan to parse caret ^ and percent % the same. Their meaning is direct and transitive dependency respectively. It means that variants, versions, arch, platform, os, target and dag hash should go before the %, so that they apply to dependent not the %dependency.
post_configure_fixes assumed py-tensorflow depends on patchelf, but that dependency is platform dependent.
* Create allow-empty-config-environment-variables.patch * Apply patch from last commit * [@spackbot] updating style on behalf of elfprince13 --------- Co-authored-by: elfprince13 <elfprince13@users.noreply.github.com>
Windows paths with drives were being interpreted as network protocols in canonicalize_path (which was expanded to handle more general URLs in spack#48784). This fixes that and adds some tests for it.
... for now. Will turn them back on for Windows when necessary adjustments are made to the package to support them.
* Add package libglvnd Signed-off-by: Shane Nehring <snehring@iastate.edu> * libglvnd: add virtual defaults Signed-off-by: Shane Nehring <snehring@iastate.edu> --------- Signed-off-by: Shane Nehring <snehring@iastate.edu>
Signed-off-by: Shane Nehring <snehring@iastate.edu>
* onnx/py-onnx: update to 1.17.0 * (py-)onnx: depends_on cmake@3.14: when=@1.17: --------- Co-authored-by: Joseph C Wang <joequant@gmail.com>
* py-setuptools-scm: add v8.1.0, v8.2.0 and refactor deps * fixup! py-setuptools-scm: add v8.1.0, v8.2.0 and refactor deps * fixup! fixup! py-setuptools-scm: add v8.1.0, v8.2.0 and refactor deps
Compatibility with Python 3.6 is still tested by the rhel8-platform-python job, and Ubuntu 20.04 will be removed soon from the list of runners: actions/runner-images#11101 Signed-off-by: Massimiliano Culpo <massimiliano.culpo@gmail.com>
…kage.py, revert forced variants in var/spack/repos/builtin/packages/py-netcdf4/package.py
7 tasks
…en netCDF was built with +mpi
…~mpi ^netcdf-c~mpi ^hdf5+mpi'
Co-authored-by: Sergey Kosukhin <skosukhin@gmail.com>
…-pick changes from spack#48694, change numpy@2 dependency to @1.26
…ttps://github.com/climbfuji/spack into feature/update_spack_stack_dev_from_spack_a9c879d
45ce9ee
to
a0cf42e
Compare
…ng rpath for Python libraries to all binaries built by met (post-install)
…/package.py: when Cray compiler wrappers are used, set MPICC instead of --with-mpi
…ge.py to match spack develop
c2885c9
to
c3f20fa
Compare
stiggy87
approved these changes
Apr 23, 2025
ulmononian
approved these changes
Apr 23, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Update spack-stack-dev from spack develop a9c879d. This is the last commit before the compilers as nodes (dependencies) PR was merged".
Additional PRs cherry-picked from spack develop:
Additional changes:
Upstream PRs for most of these changes and other spack-stack-dev changes that were missing in spack develop:
Merge conflicts resolved (see also file
merge-conflicts.txt
, temporarily committed to this branch):Testing
Issues
Closes #497
Working towards JCSDA/spack-stack#1604