Hundreds of g++ testsuite failures?

[Brad Lucier]

A change made since yesterday fixes the problem below (at least it
doesn't segfault) and cuts the number of g++ unexpected errors to 430.
Now there are somehow 500 expected errors, however.

In the libstdc++-v3 tests, all the tests now fail to build, either
shared or static.

Brad

> 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
>