[RFC] patch LD_LIBRARY_PATH_64 for sparc solaris testing
Eric Botcazou
ebotcazou@libertysurf.fr
Sun Jan 11 23:16:00 GMT 2004
> And here the ChangeLogs:
>
> gcc/testsuite/ChangeLog:
>
> 2004-01-10 Andreas Tobler <a.tobler@schweiz.ch>
>
> * g++.dg/compat/compat.exp: Add LD_LIBRARY_PATH_32/64 for solaris.
> * lib/g77.exp: Likewise.
> * lib/objc.exp: Likewise.
> * lib/g++.exp: Likewise.
>
> libjava/testsuite/ChangeLog:
>
> 2004-01-10 Andreas Tobler <a.tobler@schweiz.ch>
>
> * lib/libjava.exp: Add LD_LIBRARY_PATH_32/64 to get proper
> path setting for solaris 32/64 bit testing.
> Reorganize LD_LIBRARY_PATH setting.
>
> libstdc++-v3/ChangeLog:
>
> 2004-01-10 Andreas Tobler <a.tobler@schweiz.ch>
>
> * testsuite/lib/libstdc++.exp: Set LD_LIBRARY_PATH_32 for
> solaris.
>
> libffi/ChangeLog:
>
> 2004-01-10 Andreas Tobler <a.tobler@schweiz.ch>
>
> * testsuite/lib/libffi-dg.exp: Set LD_LIBRARY_PATH_32 for
> solaris.
Looks ok to me, but I have no authority. Perhaps if you have 2 minutes to
kill: s/solaris/Solaris/ s/32 bit/32-bit/ s/64 bit/64-bit.
> > Still testing. Will take at least another 20 hours to check against a
> > full build on solaris with test :)
>
> Ok, here are the results for sol9:
>
> http://gcc.gnu.org/ml/gcc-testresults/2004-01/msg00461.html
They are mostly correct (except for the disastrous libjava), but
FAIL: g++.dg/eh/simd-1.C (test for excess errors)
WARNING: g++.dg/eh/simd-1.C compilation failed to produce executable
FAIL: g++.dg/eh/simd-2.C (test for excess errors)
WARNING: g++.dg/eh/simd-2.C compilation failed to produce executable
in 32-bit mode should be XFAILed as in 64-bit mode. Could you take a look at
objdir/gcc/testsuite/g++.log and post the error messages?
FAIL: gcc.dg/sparc-ret.c (test for excess errors)
ERROR: gcc.dg/sparc-ret.c: error executing dg-final: couldn't open
"sparc-ret.s": no such file or directory
UNRESOLVED: gcc.dg/sparc-ret.c: error executing dg-final: couldn't open
"sparc-ret.s": no such file or directory
This one is unexpected too. Could you take a look at
objdir/gcc/testsuite/gcc.log and post the error message?
--
Eric Botcazou
More information about the Libstdc++
mailing list