On Oct 25, 2012, at 1:31 PM, Perry Smith wrote: > > On Oct 25, 2012, at 11:31 AM, David Edelsohn wrote: > >> On Thu, Oct 25, 2012 at 12:20 PM, Jonathan Wakely <jwakely....@gmail.com> >> wrote: >>> On 25 October 2012 14:16, Perry Smith wrote: >>>> >>> For trunk, yes, see the top entry of http://gcc.gnu.org/gcc-4.8/changes.html >>> >>> That isn't the case for 4.5.2, so as I said, 4.5.2 isn't built with >>> the C++ compiler so doesn't link to libstdc++.so so doesn't care if >>> you have incompatible versions in your LD_LIBRARY_PATH. >> >> I bootstrap GCC on AIX with GCC 4.6. > > Does the group / team have an AIX 6.1 build machine to build the trunk on? > Or am I the first to person walk into this?
I'm still curious in the question above But moving on: I wrapped xgcc with this script: ===== #!/bin/ksh unset LD_LIBRARY_PATH exec /usr/work/build/gcc.git/gcc/.hide/xgcc "$@" ===== I got into my build tree, did: rm -r powerpc-ibm-aix6.1.0.0/libatomic make configure-target-libatomic which completed successfully. This was my short test I was doing before to recreate / debug the issue. Can anyone help me understand why LD_LIBRARY_PATH is being set? Is it needed for another platform? For AIX, the executable has one already built into it and should be valid until the executable is installed -- at which time it is often relinked (I believe). The other question -- for AIX, why was LD_LIBRARY_PATH picked (which is just post 6.1) and not LIBPATH? This is part of why I'm asking my question above... is it maybe the case that this code has just never been ported to AIX? (the multi-lib configure code) Thank you, Perry Smith
