Re: LD_LIBRARY_PATH and --rpath

UD> Martin Buchholz <martin(a)xemacs.org&gt; writes: UD> If Sun does it this way, they are wrong. The standards explicitly say UD> it's the way we've implemented it. You cannot override a RPATH (or UD> nowadays RUNPATH) with LD_LIBRARY_PATH. Read the spcification, it's UD> freely available from SCO's web site. You know, I really try to check the standards whenever I have a question like this. I had previously made sure this stuff wasn't part of Unix98. I couldn't find any `specification' referenced on www.sco.com. I did find some man pages, and yes, they are consistent with glibc's handling of LD_LIBRARY_PATH. At the very least, please document the current behavior, and provide a reference to the `specification' on the web, and make it clear that the current behavior is _deliberately_ different from the Solaris behavior - else you're likely to get more bug reports on this. It would be nice if someone made it clear what an app's configure script is supposed to do. I wonder if libtool currently tries to provide a complete solution. Certainly on Solaris the configure script _must_ provide an RPATH. But whether to do so on Linux? My latest idea on this for XEmacs is for the XEmacs configure script to look in /etc/ld.so.conf, and then add those to the linker commands automatically, but not to use --rpath, except possibly for directories used at link time containing shared libraries, but not in /etc/ld.so.conf. Martin