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. 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++? Perry
