-
Notifications
You must be signed in to change notification settings - Fork 119
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
Upgrade to spack-stack-1.7.0 #1070
base: develop
Are you sure you want to change the base?
Conversation
|
||
load(pathJoin("stack-intel", os.getenv("stack_intel_ver") or "2021.10.0")) | ||
load(pathJoin("stack-cray-mpich", os.getenv("stack_cray_mpich_ver") or "8.1.25")) | ||
load(pathJoin("cmake", os.getenv("cmake_ver") or "3.26.3")) | ||
load(pathJoin("cmake", os.getenv("cmake_ver") or "3.23.1")) |
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.
Is there a reason for this CMake version downgrade?
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.
@mkavulich, just used cmake build by spack-stack vs. using one built by admins. It was to be consistent with other machines which use spack-stack built cmake (3.23.1).
For Derecho, we can go with 3.26.3 if needed.
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.
Thanks for the explanation, I didn't realize we were previously using the platform build instead of through spack. It's not necessary, I was just curious.
DESCRIPTION OF CHANGES:
We have new version of spack-stack available. This pull request make sure we load correct modules for SRW.
Type of change
TESTS CONDUCTED:
DEPENDENCIES:
N/A
DOCUMENTATION:
N/A
ISSUE:
Solves issue #1069
CHECKLIST
LABELS (optional):
A Code Manager needs to add the following labels to this PR: