http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49375
--- Comment #4 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot
Uni-Bielefeld.DE> 2011-06-14 15:41:50 UTC ---
IMO this is a clear example why LD_LIBRARY_PATH is evil: the execution
tests in the testsuite should be linked with -R/-rpath/whatever is
required so the correct target libraries are found. This has the
additional advantage that you can manually reexecute a failing tests
without first having to set LD_LIBRARY_PATH to all the directories
necessary to locate the runtime libraries. I think some testsuites get
this right, with the exception of libgcc_s.so.1.
As a workaround, you could link cc1plus with libppl and libstdc++
statically. At least this avoids all RPATH/LD_LIBRARY_PATH issues.
Certainly not pretty, but that's what I've been doing all the time and
what happens for go1 out of the box. I always found the contortions
necessary to correctly link with libppl a nightmare, and it has only
improved a little bit recently.
Rainer
