Brian, > I'd suggest if you're going to go to the trouble to post the results > that you run the whole testsuite and not just check-gcc. > You can do this with "make -k check" from the toplevel. I did the full "make -k check", but I think I'm doing something wrong. Before each of the each of the test sections (gcc, g++, libstdc++ ) I get a "WARNING: Couldn't find the global config file", but the test continues so I ingored the warning. However, during the libstdc++ tests I get about 40 "FAIL ... *** fatal error - called with threadlist_ix -1". At the end of libstdc++ it prints the summary: # of expected passes 6952 # of unexpected failures 29 # of expected failures 31 # of unsupported tests 439 Then it starts: make[4]: *** [check-DEJAGNU] Error 1 make[4]: Leaving directory `/home/rhodes/src/gcc-obj/i686-pc-cygwin/libstdc++-v3/testsuite' make[3]: *** [check-am] Error 2 make[3]: Target `check' not remade because of errors. It enters into another round of complex make statements then abandons: make[3]: Leaving directory `/home/rhodes/src/gcc-obj/i686-pc-cygwin/libiberty/testsuite' make[2]: Leaving directory `/home/rhodes/src/gcc-obj/i686-pc-cygwin/libiberty' make[1]: Target `check-target' not remade because of errors. make[1]: Leaving directory `/home/rhodes/src/gcc-obj' make: *** [do-check] Error 2 make: Target `check' not remade because of errors. I think I may have something misconfigured for the testsuite. Lee.
