-
Notifications
You must be signed in to change notification settings - Fork 13
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
release/1.60: bug fix for mapl with mvapich2 #449
release/1.60: bug fix for mapl with mvapich2 #449
Conversation
@climbfuji Ah. Apologies. I guess I haven't used mvapich2 in a while and didn't realize there was an One suggestion would be: elif self.spec.satisfies("^mvapich2"):
args.append(self.define("MPI_STACK", "mvapich")) to match the Footnotes
|
Co-authored-by: Matt Thompson <[email protected]>
Thanks @mathomp4 also pushed your bug fix to the spack develop PR |
Huh. I'll have to look at that license style issue. I mean, I think it's right... |
That's only because it's an old release of spack-stack. As long as it works for spack develop and our spack-stack-dev fork, all good. |
…ils modulefile (wgrib env var) (#1190) 1. Bug fix for mapl with mvapich2 (see JCSDA/spack#449) 2. Bugf ix for grib-utils module file (wgrib env var)
Description
Yet another bug fix for
mapl
forrelease/1.6.0
because it wants to configure MPI providers itself. Need to addmvapich2
, because Hercules usesmvapich2
for spack-stack-1.6.0 withgcc
. I will also cherry-pick this and send it to spack develop.Ignore the failing style tests!
Testing
Corresponding spack-stack PR: JCSDA/spack-stack#1190