-
Notifications
You must be signed in to change notification settings - Fork 23
Update Spheral to use spack v1.1.0 #421
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
Draft
mcfadden8
wants to merge
66
commits into
develop
Choose a base branch
from
task/spack1.0.2
base: develop
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.
Draft
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
Replace obsolete "spack concretize -U" with spack:concretizer:reuse:false to disable it by default within our build environment. Move compiler definitions from compilers.yaml to packages.yaml since compilers.yaml is obsolete in v1.0 Update specs to handle new semantics for "%" in v1.0 Updated using packages to point to new, separate package repository for spack. Added "depends_on" for package language dependencies (c, cxx, fortran) Renamed "m-aneos" package to "m_aneos" to match new package naming requirements of spack v1.0
Collaborator
Author
|
…, added c and cxx dependencies for packages missing them, added fortran dependency to spheral to avoid known spack bug, python concretize function is called instead of SpackCommand
mcfadden8
commented
Oct 27, 2025
mcfadden8
commented
Oct 27, 2025
mcfadden8
commented
Oct 27, 2025
…or tpl-manager.py
becker33
reviewed
Oct 30, 2025
Member
becker33
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Commeting everything I noticed while looking for the issue we were discussing on slack for setting the working dir.
…o package names are maintained by spack
…m-amdgpu, added llvm-amdgpu package recipe
Signed-off-by: Gregory Becker <[email protected]>
Updated package directory names and spec name to follow spack v1.1 naming requirements
…added environment variable settings for the llvm-amdgpu package recipe
…ed the c, cxx, and fortran depends_on below variants in package recipe, added ~fortran variant to silo
…nvironment variable
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.
Refactor configuration and build scripts to use spack v1.0.2
spack concretize -Uwithspack:concretizer:reuse:falseto disable it by default within our build environment.ToDo :