Eric Lemings wrote:
-----Original Message-----
From: Travis Vitek [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 29, 2008 12:10 PM
To: [email protected]
Subject: RE: ABI problem on Darwin (was: Re: [VOTE] stdcxx
4.2.1 release)
Eric Lemings wrote:
The workaround is to remove the link flags for version info (i.e.
-compatibility_version and -current_version) from the file
etc/config/gcc.config. This takes care of the runtime link error.
We should probably commit the fix to 4.2.x to get the ball rolling.
Hold up on that. I've found the problem may actually have been the
result of an anomoly in my environment. I suspect I may have had
another version of the library installed in a standard location which
is why the observation I posted was so puzzling. My latest builds
are running fine.
I'm afraid I'm confused about what exactly is the problem,
or if there even is one. Can you summarize what symptoms
users might see in the following two scenarios, and what
is the workaround:
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).
Thanks
Martin
