On Thu, Oct 25, 2012 at 12:20 PM, Jonathan Wakely <jwakely....@gmail.com> wrote: > On 25 October 2012 14:16, Perry Smith wrote: >> >> On Oct 25, 2012, at 3:25 AM, Jonathan Wakely wrote: >> >>> On 25 October 2012 02:12, Perry Smith wrote: >>>> >>>> This also changes a previous statement I made: while I did build 4.5.2 on >>>> a different level of AIX, it was a 6.1 level and has the same >>>> LD_LIBRARY_PATH feature. Thus, something has changed in the build process >>>> of gcc to include LD_LIBRARY_PATH into the environment before calling xgcc >>>> since 4.5.2 was released. At least, that is my current theory. >>> >>> I assume the difference is that 4.5.2 wasn't built with the C++ >>> compiler so didn't need libstdc++.so, so it's not a problem if the >>> wrong libstdc++.so is in your LD_LIBRARY_PATH, because it's not used >>> anyway. >> >> Close but not really. I am building c and c++ in all cases. > > That's not what I meant. > > Let me rephrase, 4.5.2 isn't built *using* the C++ compiler. > >> The difference is that cc1 now (the trunk build) links with libstdc++ which >> has its different bit versions in different paths. >> >> Is it normal for cc1 to link to libstdc++? > > 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. - David
