> -----Original Message----- > From: Martin Sebor [mailto:[EMAIL PROTECTED] > Sent: Wednesday, April 30, 2008 10:43 AM > To: dev@stdcxx.apache.org > Subject: Re: ABI problem on Darwin > > Eric Lemings wrote: > [...] > >> 1) In a program compiled and linked with 4.2.0 the user > >> replaces libstd.dylib.4.2.0 with libstd.dylib.4.2.1. > >> > >> 2) In a program compiled and linked with 4.2.1 the user > >> replaces libstd.dylib.4.2.1 with libstd.dylib.4.2.0. > >> > >> In both of these, the library is NOT in BUILDDIR/lib but > >> rather under PREFIX/lib (e.g., /usr/local/lib). > > > > In this situation, the user would have to set the DYLD_LIBRARY_PATH > > as they would have to set LD_LIBRARY_PATH on other Unix platforms. > > I assume "this situation" refers to case (2) above. On most > platforms setting LD_LIBRARY_PATH can be avoided by installing > the lib in one of the usual locations that the dynamic linker > searches by default (e.g., /usr/lib or /usr/local/lib). Does > hardcoding BUILDDIR have any impact on this? (I can't tell > from the Mac OS X ld man page: http://tinyurl.com/4grw9o)
I believe it works the same on Darwin: if the library is installed in a standard location, it will be found without needing to set DYLD_LIBRARY_PATH or whether it matches @install_name. I'll verify that to make sure. Brad.
