OpenPMIx Update #1773
Open
OpenPMIx Update #1773
Conversation
This file contains 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
|
@mghpcsim Prototyping the PMIx/PRRTE update. It seems to work, but see my notes in the summary. |
|
@adrianreber Is the devel repo not active for CI on RHEL-type builds? |
No, so far it was not necessary. You can enable it. CI can also not handle packages that dependent on each other. You would need to split this in two PRs. |
Signed-off-by: jcsiadal <[email protected]>
Signed-off-by: jcsiadal <[email protected]>
|
A friendly reminder that this PR had no activity for 30 days. |
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.
This is a prototype package I'm placing here for review, or to move into the development tree.
One major change is moving it under its proper name.
This update also adds PRRTE to the build, but I needed to add as a second spec. The full OpenPMIx package is required to build PRRTE, but I was not able to merge the two into a single build. There are a lot of hardcoded paths added during build and I was only able to get a successful build with PMIx in its final location. Even doing a temp build and install of PMIX introduced different errors in PRRTE.
If our build system can handle both specs in one directory, great; otherwise, we'll need to have a new package under RMS for PRRTE.
These both are using RCs, as they will likely be full releases before 3.0 and these specs also work with the current production releases.