Some C tests are linked against libgcc.so.1 when the new binutils is used: +FAIL: gcc.dg/cleanup-10.c execution test +FAIL: gcc.dg/cleanup-11.c execution test +FAIL: gcc.dg/cleanup-5.c execution test +FAIL: gcc.dg/cleanup-8.c execution test +FAIL: gcc.dg/cleanup-9.c execution test But nothing is done to ensure that the newly built libgcc.so.1 is used. We need to do something similar to C++ tests to make sure the newly built libgcc.so.1 is used.
*** Bug 16510 has been marked as a duplicate of this bug. ***
I have been wondering this as I see it on the mainline off and on but it might because other changes. But I know that LD_LIBRARY_PATH is set though.
I can tell you for sure that in my case LD_LIBRARY_PATH is not set, at least, not correctly since the error is libunwind.so.7 can't be found, which won't happen if LD_LIBRARY_PATH is correctly set to use the newly built libgcc_s.so.1.
Patch here: <http://gcc.gnu.org/ml/gcc-patches/2004-07/msg01881.html> and for me.
Subject: Bug 16633 CVSROOT: /cvs/gcc Module name: gcc Changes by: hjl@gcc.gnu.org 2004-09-06 23:36:12 Modified files: gcc/testsuite : ChangeLog gcc/testsuite/lib: gcc-dg.exp Log message: 2004-09-06 H.J. Lu <hongjiu.lu@intel.com> PR c/16633: * lib/gcc-dg.exp: Set up LD_LIBRARY_PATH, SHLIB_PATH, LD_LIBRARYN32_PATH, LD_LIBRARY64_PATH and DYLD_LIBRARY_PATH. Patches: http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/ChangeLog.diff?cvsroot=gcc&r1=1.4247&r2=1.4248 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/lib/gcc-dg.exp.diff?cvsroot=gcc&r1=1.34&r2=1.35
Fixed for 3.5.0.