add libopen-orted-mpir when statically linking#9609
add libopen-orted-mpir when statically linking#9609bwbarrett merged 1 commit intoopen-mpi:v4.1.xfrom
Conversation
This is a one-off commit for the v4 series since v5 and later moved to prrte. Thanks Matt Thompson for reporting this issue. Signed-off-by: Gilles Gouaillardet <gilles@rist.or.jp>
|
@rhc54 could you please have a look at this PR? Currently, if Open MPI is configure'd with |
|
I'm not the correct person - haven't had anything to do with MPIR in ages. @awlauria I think you folks deal with this now? |
|
The change makes sense to me. @jsquyres / @gpaulsen / @bwbarrett ? |
|
@ggouaillardet would you mind opening an equivalent PR for the v4.0.x series? |
|
@bwbarrett This looks correct to me. Can you think of any problems with it? |
|
I can't think of anything; it raises the question why we're leaving it in a standalone library, but let's not worry about that for now. |
|
It was compiled into its stand-alone library to compile it with its own CFLAGS, otherwise they would be compiled with -O3 and the like: |
|
the PR for the |
|
@awlauria thanks for the insight. |
|
@awlauria @bwbarrett I think I understand ... and I messed up (!) the library used to be installed, but is now slurped (aka that means this PR should be reverted (!) do you concur? |
|
Ah shoot. Yes, there's the reason this PR shouldn't have been merged. Oh well; let's revert... |
|
FWIW, I confirm with my own local build that the v4.1.x branch is now broken: Why didn't CI catch this? Weird. |
|
I'm not sure why CI didn't catch this. I'll dig into that; very weird. |
|
The issue only occurs if Open MPI is configured with |
This is a one-off commit for the v4 series since
v5 and later moved to prrte.
bot:notacherrypick
Thanks Matt Thompson for reporting this issue.
Signed-off-by: Gilles Gouaillardet gilles@rist.or.jp