This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: Hundreds of g++ testsuite failures?
- To: ghazi at caip dot rutgers dot edu
- Subject: Re: Hundreds of g++ testsuite failures?
- From: Brad Lucier <lucier at math dot purdue dot edu>
- Date: Thu, 1 Feb 2001 12:32:29 -0500 (EST)
- Cc: gcc-bugs at gcc dot gnu dot org, lucier at math dot purdue dot edu
OK, here's another clue that I haven't been able to unravel.
When the libstdc++-v3 tests begin to run on my alpha box, I get
(chmod + ./mkcheck; \
srcdir=`cd ../../../libstdc++-v3; pwd`; builddir=`pwd`; \
test -d testsuite || (mkdir testsuite; chmod u+w testsuite); \
cd testsuite; ${builddir}/mkcheck 0 ${builddir} ${srcdir})
running mkcheck
/export/u11/lucier/programs/gcc/objdir/alphaev6-unknown-linux-gnu/libstdc++-v3/mkcheck: testing the build directory
making file ./20010201-mkcheckfiles.txt
making utility ./printnow.exe
Detailed test results in ../20010201-mkcheck.txt
+: pass, -b: build failure, -r: run failure, x: disabled
------------------------------------------------------------------------
static shared test
------------------------------------------------------------------------
make[1]: [check] Error 139 (ignored)
make[1]: Leaving directory `/export/u11/lucier/programs/gcc/objdir/alphaev6-unknown-linux-gnu/libstdc++-v3'
Perhaps discovering why this segfaults would move toward a total
solution.
Brad