On 01/30/2013 04:56 PM, David Edelsohn wrote: > On Wed, Jan 30, 2013 at 10:44 AM, Michael Haubenwallner > <michael.haubenwall...@salomon.at> wrote: >> >> On 01/30/2013 03:16 PM, David Edelsohn wrote: >>> <michael.haubenwall...@salomon.at> wrote: >>>> 4: Also, LD_LIBRARY_PATH points to ppc64/libstdc++-v3/.libs/ while using >>>> 32bit gcc/xgcc to build libatomic.a. >>>> => This is the one that /does/ break, as that 64bit libstdc++.a is there >>>> now. >> >>> Originally, I was using --boot-ld-flags which included /usr/gnu/lib >>> first in the path, so an older version of libstdc++ was found. >> >> Yes, but - sorry for being nit-picky - could you find out if your >> /usr/gnu/lib/libstdc++.a was a static-only archive? > > libstdc++.a is a shared library. 32 bit version. But it was first in > the path, so satisfying GCC cc1, cc1plus, etc. built as a 32 bit > executable. The libstdc++ ABI has not changed, so the library provide > all of the necessary functions.
Erm - the question is why the 64bit libstdc++ found via LD_LIBRARY_PATH (set during libatomic build) didn't break these 32bit executables in your case. /haubi/
