-
Notifications
You must be signed in to change notification settings - Fork 859
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
need ability to not use --enable-new-dtags option in linker scripts. #1089
Comments
@adammoody Does |
@jsquyres I worked with @adammoody and @hppritcha on this and am following up on it now. Using Removing all references of I also wonder why |
Please allow an option to disable adding the --enable-new-dtags flag. I can hack the configure scripts, etc. to mimic an loader which does not support --enable-new-dtags, |
AUTHORS: Fix an errant reference to Subversion IDs
@hppritcha we recently stumbled into this issue again. Any update here? For now, I'm planning to hack configure to remove the --enable-new-dtags, but that's my ugly solution. I'm hoping we could get a --disable-new-dtags configure option added to config/opal_setup_wrappers.m4 to do the same. Basically, the idea would be to skip running OPAL_SETUP_RUNPATH if --disable-new-dtags is thrown. I could post a PR for this. Just let me know. Thanks! |
@adammoody let me know if the patch works |
The --enable-new_dtags option for the compiler wrappers is often great, but for some particular install/usage scenarios causes issues. This commit provides a new configury option to all for use of rpath in the compiler wrappers, but disables the use of --enable-new-dtags in the link line. Fixes open-mpi#1089 Signed-off-by: Howard Pritchard <[email protected]>
The --enable-new-dtags option for the compiler wrappers is often great, but for some particular install/usage scenarios causes issues. This commit provides a new configury option to use of rpath in the compiler wrappers, but disables the use of --enable-new-dtags in the link line. Fixes open-mpi#1089 Signed-off-by: Howard Pritchard <[email protected]>
The --enable-new-dtags option for the compiler wrappers is often great, but for some particular install/usage scenarios causes issues. This commit provides a new configury option to use of rpath in the compiler wrappers, but disables the use of --enable-new-dtags in the link line. Fixes open-mpi#1089 Signed-off-by: Howard Pritchard <[email protected]>
The --enable-new-dtags option for the compiler wrappers is often great, but for some particular install/usage scenarios causes issues. This commit provides a new configury option to use of rpath in the compiler wrappers, but disables the use of --enable-new-dtags in the link line. The new configury option is --enable-wrappers-runpath To disable use of --enable-new-dtags in the wrappers, add --disable-wrappers-runpath to the Open MPI configury line. Fixes open-mpi#1089 Signed-off-by: Howard Pritchard <[email protected]>
The --enable-new-dtags option for the compiler wrappers is often great, but for some particular install/usage scenarios causes issues. This commit provides a new configury option to use of rpath in the compiler wrappers, but disables the use of --enable-new-dtags in the link line. The new configury option is --enable-wrappers-runpath To disable use of --enable-new-dtags in the wrappers, add --disable-wrappers-runpath to the Open MPI configury line. Fixes open-mpi#1089 Signed-off-by: Howard Pritchard <[email protected]>
reopening issue because some sites are wanting this back ported to 3.x.y releases. |
Isn't this already in 3.1.x? At least, the configure option is there... |
@hppritcha I think @icdragn is right:
Are you talking about something else? |
Actually, I think the configure parameter that @hppritcha is looking for is
|
The --enable-new-dtags option for the compiler wrappers is often great, but for some particular install/usage scenarios causes issues. This commit provides a new configury option to use of rpath in the compiler wrappers, but disables the use of --enable-new-dtags in the link line. The new configury option is --enable-wrappers-runpath To disable use of --enable-new-dtags in the wrappers, add --disable-wrappers-runpath to the Open MPI configury line. Fixes open-mpi#1089 Signed-off-by: Howard Pritchard <[email protected]> (cherry picked from commit ebb30c1)
@jsquyres you're right. the admin is wanting to install 3.0.x which apparently didn't get this patch |
@hppritcha We're gearing up for v3.0.x and v3.1.x releases. I confirm that this fix is in v3.0.x, but it is NOT in v3.1.x. Did you want this in v3.1.x? If so, please file a PR ASAP. Refs #7040 |
@jsquyres i'll see into opening a pr for 3.1.x |
The --enable-new-dtags option for the compiler wrappers is often great, but for some particular install/usage scenarios causes issues. This commit provides a new configury option to use of rpath in the compiler wrappers, but disables the use of --enable-new-dtags in the link line. The new configury option is --enable-wrappers-runpath To disable use of --enable-new-dtags in the wrappers, add --disable-wrappers-runpath to the Open MPI configury line. Fixes open-mpi#1089 Signed-off-by: Howard Pritchard <[email protected]> (cherry picked from commit ebb30c1)
The --enable-new-dtags option for the compiler wrappers is often great, but for some particular install/usage scenarios causes issues. This commit provides a new configury option to use of rpath in the compiler wrappers, but disables the use of --enable-new-dtags in the link line. The new configury option is --enable-wrappers-runpath To disable use of --enable-new-dtags in the wrappers, add --disable-wrappers-runpath to the Open MPI configury line. Fixes open-mpi#1089 Signed-off-by: Howard Pritchard <[email protected]> (cherry picked from commit ebb30c1)
Forgot to include a fix for the fortran test used to check if new dtags is supported. Related to open-mpi#7268 Related to open-mpi#6539 open-mpi#1089 This patch is already included on v4.0.x branch. Signed-off-by: Howard Pritchard <[email protected]> (cherry picked from commit 5354b9b)
won't fix. not planning to release 3.0.x update unless there's something critical. and this issue doesn't fall into that category. |
The flag showed up with compiling OpenACC 5.0.5 on an ARM system running Rocky Linux release 9.3 (Blue Onyx) using the NVHPC 24.9 compiler:
I set these to bypass it
but it didn't show up in the failing phase. Is there some other place I need to put it, like
though I'm not setting |
Passing it as part of the compiler invocation worked:
Is there a variable that would do it, though? I tried LDFLAGS but it didn't show up in the linkage-line. |
It turns out the --enable-new-dtags linker option in the Open MPI compiler scripts is causing issues for some users:
Here's what a sysadmin reported:
Many of our users want to encode an RPATH to the MPI library in their executable at link time. In fact, they like to encode paths to all of their other libraries this way. On Linux, RPATH overrides anything a user sets in LD_LIBRARY_PATH, which provides one way for our app developers to ensure that thier users are getting the correct set of libraries (they can't mess things up with a wrong LD_LIBRARY_PATH setting). The --enable-new-dtags flag changes things so that LD_LIBRARY_PATH settings now override any RPATH setting, which breaks our apps.
MVAPICH recently added the --enable-new-dtags flag to their wrappers starting with MV2-2.1, which broke many of our applications. At that point, I also looked into Open MPI and found that this option was added somewhere by the time 1.8.3 was released. Apparently, this particular set of users wasn't using Open MPI, and so we didn't notice the change in Open MPI until now.
I asked MVAPICH to add a configure flag to avoid the --enable-new-dtags option. I now configure MV2-2.1 to drop this flag in the wrappers. I was looking to see if there's a similar fix already in Open MPI that we could use, and if not, if something could be added.
-Adam
@adammoody
The text was updated successfully, but these errors were encountered: