-
Notifications
You must be signed in to change notification settings - Fork 64
{2025.06} OpenMPI/5.0.3-GCC-13.3.0
+ foss/2024a
#1164
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
{2025.06} OpenMPI/5.0.3-GCC-13.3.0
+ foss/2024a
#1164
Conversation
# now Autotools/Automake/libtool/M4 are retained as (build) dependency because the newer versions | ||
# in EESSI 2025.06 compat layer can cause problems with some installations (like OpenMPI); | ||
# see also https://github.com/EESSI/software-layer-scripts/pull/74 | ||
- M4-1.4.19.eb |
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.
note: this is required to fix missing installations check that will pop up once EESSI/software-layer-scripts#74 is deployed/merged...
About ipv6, seemingly it matters most for OpenMPI 5 where you have PRRTE and PMIX as external deps, someone in the EasyBuild community has parse hooks which do:
This is enough for version 4 but not for version 5, where PRRTE and PMIx are separate, additionally there is:
I've read that there is some overhead to this as it is another option to test at runtime (which can be avoided via MPI tuning), so it does seem like something we want to put in a hook. |
Can you clarify what you mean by overhead? If so, we definitely want to do what's necessary to only make it consider IPv4 by default, and document what to do on IPv6 systems (which are an exception for sure, I would guess) |
Just a test build for now, still need to look into the IPv6 aspect... bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen3 |
New job on instance
|
New job on instance
|
New job on instance
|
Only checked the zen3 job, but all those builds actually succeeded. The |
…r of builds correct
Another test build, still need to look into the IPv6 aspect... bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen3 |
New job on instance
|
New job on instance
|
New job on instance
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen3 |
New job on instance
|
New job on instance
|
New job on instance
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws for:arch=x86_64/generic |
New job on instance
|
New job on instance
|
New job on instance
|
New job on instance
|
New job on instance
|
New job on instance
|
New job on instance
|
New job on instance
|
New job on instance
|
New job on instance
|
New job on instance
|
All builds succeeded, ready to deploy... 🥳 |
Ugh, I meant to set |
Not to worry, I would do it anyway |
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.
LGTM
draft since we want to make sure that OpenMPI is built with IPv6 support, but I'll go ahead and do a test build already, should once we stop filtering
Autotools
& co for EESSI 2025.06, see:edit: requires: