FYI - I wasn’t bothered by the default behavior... I was just looking for a sanctioned way for an installer (e.g. a sysadmin) to make the UCX be loaded based on LD_LIBRARY_PATH so that there was an ability for the user to swap in a debug build of UCX at runtime.
On Mon, Feb 1, 2021 at 10:14 AM Peter Kjellström via devel < devel@lists.open-mpi.org> wrote: > On Mon, 1 Feb 2021 14:46:22 +0000 > "Jeff Squyres \(jsquyres\) via devel" <devel@lists.open-mpi.org> wrote: > > > On Jan 27, 2021, at 7:19 PM, Gilles Gouaillardet <gil...@rist.or.jp> > > wrote: > > > > > > What I meant is the default Linux behavior is to first lookup > > > dependencies in the rpath, and then fallback to LD_LIBRARY_PATH > > > *unless* -Wl,--enable-new-dtags was used at link time. > > > > > > In the case of Open MPI, -Wl,--enable-new-dtags is added to the MPI > > > wrappers, but Open MPI is *not* built with this option. > > > > Oh, I see where I got confused: Open MPI (core and DSO components) is > > built with -rpath, but not --enable-new-dtags. > > > > Hmm. ...trying to remember why we would have made that choice... > > > > I don't see any obvious reason cited in the git history. Do you > > remember? > > Many centers deploying OpenMPI on clusters probably DONT want runpath > instead of rpath (what new-dtags does). > > For many "protection" against LD_LIBRARY_PATH in user environments is > the whole point. > > In my opinion -rpath that doesn't win over LD_LIBRARY_PATH is near > useless. > > my .02€ > Peter > -- Tim Mattox (Sent from Gmail Mobile)
