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 UD> explicitly say it's the way we've implemented it. You cannot UD> override a RPATH (or nowadays RUNPATH) with LD_LIBRARY_PATH. UD> Read the spcification, it's freely available from SCO's web site. GN> Uh, Solaris conforms to the ABI referred to above. Could you GN> repeat why you think otherwise (sorry for my lack of attention GN> earlier). According to the Linker and Libraries Guide from Sun: html: http://docs.sun.com:80/ab2/coll.45.10/LLM/＠Ab2PageView/4733?DwebQuery=Lin... PDF: ftp://192.18.99.138/805-3050/805-3050.pdf Page 48 on a printed copy: "Another way to add to the runtime linker's search path is to set the environment variable LD_LIBRARY_PATH. This environment variable (which is analyzed once at process start-up) can be set to a colon-separated list of directories, and these directories will be searched by the runtime linker before any runpath specification or default directory. 64-bit executables can have an LD_LIBRARY_PATH_64 variable, which overrides any active LD_LIBRARY_PATH setting." Also under Solaris(sparc) where prog has been linked with an RPATH: $ LD_LIBRARY_PATH=/no/such/directory ldd -s prog The output will show that LD_LIBRARY_PATH is searched before RPATH, so it is Solaris that does not conform to the ABI. -Jimi X BTW: I'm not sure if the SPARC ABI supplement can override the Generic ABI on this function (or even if it does), but if the same happens on Solaris x86 (Georg?) and the x86 supplement does not seem to mention (I couldn't find it) then Solaris clearly does not conform.