Re: IRIX inheriting RPATH of libraries

[Albert Chin]

On Mon, Jul 21, 2003 at 05:02:45PM -0500, Tim Mooney wrote:
> In regard to: IRIX inheriting RPATH of libraries, Albert Chin said (at...:
> 
> >Ugh! Looks like IRIX will inherit the RPATH of a library. So, say
> >program foo is linked against libbar2.so and libbar2.so is dependent
> >on libbar1.so. At build time, the runtime path of the .libs directory
> >containing libbar1.so will be added to the RPATH entry of libbar2.so.
> >Then, when program foo is created, this .libs directory is added to
> >the RPATH entry of program foo. Because program foo is not relinked at
> >install time, it keeps this RPATH entry.
> >
> >Looks like we need another variable, inherit_rpath, that relinks
> >programs when true.
> 
> I must be missing something, because I'm not seeing how that's different
> from other osf-style linkers.  Tru64 executables pick up the DT_RPATH
> from each and every library they link directly against -- I guess I've
> never thought about or checked whether they pick up the RPATH for
> libraries that their libraries depend on.
> 
> I know you're very familiar with the Tru64 linker/loader behavior.  Can
> you explain what's different that you're surprised about in the IRIX
> linker vs. the Tru64 linker or other osf-style linkers?
> 
> I actually like and have made great use of the "executables pick up
> the RPATH entries for libraries they link against".  It can be very handy.

This isn't a problem for Tru64 UNIX because hardcode_into_libs=no. If
hardcode_into_libs=yes, Tru64 UNIX would have the same problem.

-- 
albert chin (address@hidden)