I am building gcc-3.4.6 in the framework of my http://appsfromscratch.berlios.de/ project, and 'make check' for gcc-3.4.6 fails. Basically, my tool builds and installs every lib/app (per source tarball) in a separate directory, other than that it uses the standard ./configure make make check make install scheme. If necessary, I can upload the tool, it's self-contained, downloads sources from the web; to build gcc-3.4.6 one would have to enter a command line like this: ~/AppsFromScratch/20061104/bin/build.pl -targets_to_build gcc3 -make_like 1>build.log 2>&1 & . OK, here is screen output of the failing 'make check': " make[1]: Entering directory `/maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6/gcc' Making a new config file... echo "set tmpdir /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6/gcc/testsuite" >> ./tmp0 test -d testsuite || mkdir testsuite rm -f testsuite/site.exp sed '/set tmpdir/ s|testsuite|testsuite|' < site.exp > testsuite/site.exp (rootme=`${PWDCMD-pwd}`; export rootme; \ srcdir=`cd /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc; ${PWDCMD-pwd}` ; export srcdir ; \ cd testsuite; \ EXPECT=expect ; export EXPECT ; \ if [ -f ${rootme}/../expect/expect ] ; then \ TCL_LIBRARY=`cd .. ; cd /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/../tcl/library ; ${PWDCMD-pwd}` ; \ export TCL_LIBRARY ; fi ; \ runtest --tool gcc ) WARNING: Couldn't find the global config file. Test Run By sergei on Wed Nov 8 01:18:30 2006 Native configuration is i686-pc-linux-gnu === gcc tests === Schedule of variations: unix Running target unix Using /maxtor5/sergei/AppsFromScratchWD/install/dejagnu-1.4.4/share/dejagnu/baseboards/unix.exp as board description file for target. Using /maxtor5/sergei/AppsFromScratchWD/install/dejagnu-1.4.4/share/dejagnu/config/unix.exp as generic interface file for target. Using /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/config/default.exp as tool-and-target-specific interface file. Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/gcc.c-torture/compile/compile.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/gcc.c-torture/execute/builtins/builtins.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/gcc.c-torture/execute/execute.exp ... FAIL: gcc.c-torture/execute/va-arg-25.c execution, -Os Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/gcc.c-torture/execute/ieee/ieee.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/gcc.c-torture/unsorted/unsorted.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/gcc.dg/compat/compat.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/gcc.dg/cpp/cpp.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/gcc.dg/cpp/trad/trad.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/gcc.dg/debug/debug.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/gcc.dg/debug/dwarf2/dwarf2.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/gcc.dg/dg.exp ... FAIL: gcc.dg/cleanup-8.c execution test FAIL: gcc.dg/cleanup-9.c execution test Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/gcc.dg/format/format.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/gcc.dg/noncompile/noncompile.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/gcc.dg/pch/pch.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/gcc.dg/special/mips-abi.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/gcc.dg/special/special.exp ... FAIL: gcc.dg/special/gcsec-1.c (test for excess errors) WARNING: gcc.dg/special/gcsec-1.c compilation failed to produce executable Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/gcc.dg/tls/tls.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/gcc.dg/torture/dg-torture.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/gcc.dg/weak/weak.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/gcc.misc-tests/acker1.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/gcc.misc-tests/arm-isr.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/gcc.misc-tests/bprob.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/gcc.misc-tests/dhry.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/gcc.misc-tests/gcov.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/gcc.misc-tests/i386-prefetch.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/gcc.misc-tests/linkage.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/gcc.misc-tests/matrix1.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/gcc.misc-tests/mg.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/gcc.misc-tests/sieve.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/gcc.misc-tests/sort2.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/gcc.test-framework/test-framework.exp ... skipping test framework tests, CHECK_TEST_FRAMEWORK is not defined === gcc Summary === # of expected passes 25374 # of unexpected failures 4 # of expected failures 70 # of untested testcases 7 # of unsupported tests 211 /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6/gcc/xgcc version 3.4.6 make[1]: [check-gcc] Error 1 (ignored) (rootme=`${PWDCMD-pwd}`; export rootme; \ srcdir=`cd /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc; ${PWDCMD-pwd}` ; export srcdir ; \ cd testsuite; \ EXPECT=expect ; export EXPECT ; \ if [ -f ${rootme}/../expect/expect ] ; then \ TCL_LIBRARY=`cd .. ; cd /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/../tcl/library ; ${PWDCMD-pwd}` ; \ export TCL_LIBRARY ; fi ; \ runtest --tool g++ ) WARNING: Couldn't find the global config file. Test Run By sergei on Wed Nov 8 02:11:32 2006 Native configuration is i686-pc-linux-gnu === g++ tests === Schedule of variations: unix Running target unix Using /maxtor5/sergei/AppsFromScratchWD/install/dejagnu-1.4.4/share/dejagnu/baseboards/unix.exp as board description file for target. Using /maxtor5/sergei/AppsFromScratchWD/install/dejagnu-1.4.4/share/dejagnu/config/unix.exp as generic interface file for target. Using /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/config/default.exp as tool-and-target-specific interface file. Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/g++.dg/bprob/bprob.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/g++.dg/compat/compat.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/g++.dg/debug/debug.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/g++.dg/dg.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/g++.dg/gcov/gcov.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/g++.dg/pch/pch.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/g++.dg/special/ecos.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/g++.dg/tls/tls.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/g++.old-deja/old-deja.exp ... FAIL: g++.old-deja/g++.law/weak.C (test for excess errors) === g++ Summary === # of expected passes 10022 # of unexpected failures 1 # of expected failures 67 # of unsupported tests 43 /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6/gcc/testsuite/../g++ version 3.4.6 make[1]: [check-g++] Error 1 (ignored) (rootme=`${PWDCMD-pwd}`; export rootme; \ srcdir=`cd /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc; ${PWDCMD-pwd}` ; export srcdir ; \ cd testsuite; \ EXPECT=expect ; export EXPECT ; \ if [ -f ${rootme}/../expect/expect ] ; then \ TCL_LIBRARY=`cd .. ; cd /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/../tcl/library ; ${PWDCMD-pwd}` ; \ export TCL_LIBRARY ; fi ; \ runtest --tool g77 ) WARNING: Couldn't find the global config file. Test Run By sergei on Wed Nov 8 02:31:19 2006 Native configuration is i686-pc-linux-gnu === g77 tests === Schedule of variations: unix Running target unix Using /maxtor5/sergei/AppsFromScratchWD/install/dejagnu-1.4.4/share/dejagnu/baseboards/unix.exp as board description file for target. Using /maxtor5/sergei/AppsFromScratchWD/install/dejagnu-1.4.4/share/dejagnu/config/unix.exp as generic interface file for target. Using /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/config/default.exp as tool-and-target-specific interface file. Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/g77.dg/bprob/bprob.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/g77.dg/dg.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/g77.dg/gcov/gcov.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/g77.f-torture/compile/compile.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/g77.f-torture/execute/execute.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/g77.f-torture/noncompile/noncompile.exp ... === g77 Summary === # of expected passes 1824 /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6/gcc/testsuite/../g77 version 3.4.6 (rootme=`${PWDCMD-pwd}`; export rootme; \ srcdir=`cd /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc; ${PWDCMD-pwd}` ; export srcdir ; \ cd testsuite; \ EXPECT=expect ; export EXPECT ; \ if [ -f ${rootme}/../expect/expect ] ; then \ TCL_LIBRARY=`cd .. ; cd /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/../tcl/library ; ${PWDCMD-pwd}` ; \ export TCL_LIBRARY ; fi ; \ runtest --tool objc ) WARNING: Couldn't find the global config file. Test Run By sergei on Wed Nov 8 02:34:24 2006 Native configuration is i686-pc-linux-gnu === objc tests === Schedule of variations: unix Running target unix Using /maxtor5/sergei/AppsFromScratchWD/install/dejagnu-1.4.4/share/dejagnu/baseboards/unix.exp as board description file for target. Using /maxtor5/sergei/AppsFromScratchWD/install/dejagnu-1.4.4/share/dejagnu/config/unix.exp as generic interface file for target. Using /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/config/default.exp as tool-and-target-specific interface file. Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/objc/compile/compile.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/objc/execute/execute.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/objc.dg/dg.exp ... Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/gcc/testsuite/objc.dg/special/special.exp ... === objc Summary === # of expected passes 1352 # of unsupported tests 8 /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6/gcc/xgcc version 3.4.6 make[1]: Leaving directory `/maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6/gcc' make[1]: Entering directory `/maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6/fastjar' make[1]: Nothing to be done for `check'. make[1]: Leaving directory `/maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6/fastjar' make[1]: Entering directory `/maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6/intl' make[1]: Nothing to be done for `check'. make[1]: Leaving directory `/maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6/intl' make[1]: Entering directory `/maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6/libiberty' make[2]: Entering directory `/maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6/libiberty/testsuite' gcc -DHAVE_CONFIG_H -g -O2 -I.. -I/maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/libiberty/testsuite/../../include -o test-demangle \ /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/libiberty/testsuite/test-demangle.c ../libiberty.a /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/libiberty/testsuite/test-demangle.c: In function 'main': /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/libiberty/testsuite/test-demangle.c:181: warning: incompatible implicit declaration of built-in function 'strcspn' /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/libiberty/testsuite/test-demangle.c:217: warning: incompatible implicit declaration of built-in function 'strspn' ./test-demangle < /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/libiberty/testsuite/demangle-expected ./test-demangle: 745 tests, 0 failures make[2]: Leaving directory `/maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6/libiberty/testsuite' make[1]: Leaving directory `/maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6/libiberty' make[1]: Entering directory `/maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6/i686-pc-linux-gnu/libstdc++-v3' Making check in include make[2]: Entering directory `/maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6/i686-pc-linux-gnu/libstdc++-v3/include' make[2]: Nothing to be done for `check'. make[2]: Leaving directory `/maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6/i686-pc-linux-gnu/libstdc++-v3/include' Making check in libmath make[2]: Entering directory `/maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6/i686-pc-linux-gnu/libstdc++-v3/libmath' make[2]: Nothing to be done for `check'. make[2]: Leaving directory `/maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6/i686-pc-linux-gnu/libstdc++-v3/libmath' Making check in libsupc++ make[2]: Entering directory `/maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6/i686-pc-linux-gnu/libstdc++-v3/libsupc++' make[2]: Nothing to be done for `check'. make[2]: Leaving directory `/maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6/i686-pc-linux-gnu/libstdc++-v3/libsupc++' Making check in src make[2]: Entering directory `/maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6/i686-pc-linux-gnu/libstdc++-v3/src' make[2]: Nothing to be done for `check'. make[2]: Leaving directory `/maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6/i686-pc-linux-gnu/libstdc++-v3/src' Making check in po make[2]: Entering directory `/maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6/i686-pc-linux-gnu/libstdc++-v3/po' make[2]: Nothing to be done for `check'. make[2]: Leaving directory `/maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6/i686-pc-linux-gnu/libstdc++-v3/po' Making check in testsuite make[2]: Entering directory `/maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6/i686-pc-linux-gnu/libstdc++-v3/testsuite' touch testsuite_wchar_t make -j1 check-DEJAGNU make[3]: Entering directory `/maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6/i686-pc-linux-gnu/libstdc++-v3/testsuite' Making a new site.exp file... srcdir=`CDPATH="${ZSH_VERSION+.}:" && cd /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/libstdc++-v3/testsuite && pwd`; export srcdir; \ EXPECT=expect; export EXPECT; \ runtest=runtest; \ if /bin/sh -c "$runtest --version" > /dev/null 2>&1; then \ l='libstdc++'; for tool in $l; do \ $runtest --tool $tool --srcdir $srcdir ; \ done; \ else echo "WARNING: could not find \`runtest'" 1>&2; :;\ fi WARNING: Couldn't find the global config file. Test Run By sergei on Wed Nov 8 02:36:45 2006 Native configuration is i686-pc-linux-gnu === libstdc++ tests === Schedule of variations: unix Running target unix Using /maxtor5/sergei/AppsFromScratchWD/install/dejagnu-1.4.4/share/dejagnu/baseboards/unix.exp as board description file for target. Using /maxtor5/sergei/AppsFromScratchWD/install/dejagnu-1.4.4/share/dejagnu/config/unix.exp as generic interface file for target. Using /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/libstdc++-v3/testsuite/config/default.exp as tool-and-target-specific interface file. Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/libstdc++-v3/testsuite/libstdc++-abi/abi.exp ... FAIL: abi_check Running /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6.src/libstdc++-v3/testsuite/libstdc++-dg/normal.exp ... XPASS: 22_locale/locale/cons/12658_thread.cc execution test XPASS: 26_numerics/c99_classification_macros_c.cc (test for excess errors) === libstdc++ Summary === # of expected passes 2736 # of unexpected failures 1 # of unexpected successes 2 # of expected failures 5 make[3]: *** [check-DEJAGNU] Error 1 make[3]: Leaving directory `/maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6/i686-pc-linux-gnu/libstdc++-v3/testsuite' make[2]: *** [check-am] Error 2 make[2]: Leaving directory `/maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6/i686-pc-linux-gnu/libstdc++-v3/testsuite' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6/i686-pc-linux-gnu/libstdc++-v3' make: *** [check-target-libstdc++-v3] Error 2 ". The majority of tests pass. Please let me know whether you need additional info.
Use "make -k check" as documented.
I do not understand you comment. That is, from 'make' manpage: " -k Continue as much as possible after an error. While the target that failed, and those that depend on it, cannot be remade, the other dependencies of these targets can be processed all the same. " - my point was that there were failing tests. And my implied questions were: 1) do the failing tests indicate problems in gcc ? 2) do the failing test fail because they themselves are faulty ? After 'make check': " FAIL: gcc.c-torture/execute/va-arg-25.c execution, -Os FAIL: gcc.dg/cleanup-8.c execution test FAIL: gcc.dg/cleanup-9.c execution test FAIL: gcc.dg/special/gcsec-1.c (test for excess errors) FAIL: g++.old-deja/g++.law/weak.C (test for excess errors) FAIL: abi_check ". After 'make -k check': " FAIL: gcc.c-torture/execute/va-arg-25.c execution, -Os FAIL: gcc.dg/cleanup-8.c execution test FAIL: gcc.dg/cleanup-9.c execution test FAIL: gcc.dg/special/gcsec-1.c (test for excess errors) FAIL: g++.old-deja/g++.law/weak.C (test for excess errors) FAIL: abi_check FAIL: gctest ". Could you please answer the: " 1) do the failing tests indicate problems in gcc ? 2) do the failing test fail because they themselves are faulty ? " questions ? Thanks in advance.
(In reply to comment #2) > I do not understand you comment. Documented at: http://gcc.gnu.org/install/test.html
I read the document: http://gcc.gnu.org/install/test.html, but it doesn't answer my questions. If you need test results reported through the suggested srcdir/contrib/test_summary -p your_commentary.txt \ -m gcc-testresults@gcc.gnu.org |sh command, I can do this, but will you answer the " 1) do the failing tests indicate problems in gcc ? 2) do the failing test fail because they themselves are faulty ? " questions ? If not, why should I bother in the first place ? If yes, what info other than the one produced by srcdir/contrib/test_summary -p your_commentary.txt \ -m gcc-testresults@gcc.gnu.org |sh do you need ?
> 1) do the failing tests indicate problems in gcc ? Depends on the failure. > 2) do the failing test fail because they themselves are faulty ? Depends on the failures. You might want to look at http://gcc.gnu.org/gcc-3.4/buildstat.html And the other buildstat.html for the other releases.
Some failures are also due to faulty glibc, etc. and not related to GCC.
OK, being in /maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6 directory, which is my 'obj' directory, I tried to run the 'test_summary' mentioned at the bottom of http://gcc.gnu.org/install/test.html : " 0.5 Submitting test results If you want to report the results to the GCC project, use the contrib/test_summary shell script. Start it in the objdir with srcdir/contrib/test_summary -p your_commentary.txt \ -m gcc-testresults@gcc.gnu.org |sh This script uses the Mail program to send the results, so make sure it is in your PATH. The file your_commentary.txt is prepended to the testsuite summary and should contain any special remarks you have on your results or your build environment. Please do not edit the testsuite result block or the subject line, as these messages may be automatically processed. ". Please pay attention to " This script uses the Mail program to send the results, so make sure it is in your PATH ". On my system: " [21] 1:20 sergei@comp.home.net:/maxtor5/sergei/AppsFromScratchWD/build/gcc-3.4.6> which mail /bin/mail ". However, here's what I'm getting running the program: " ../gcc-3.4.6.src/contrib/test_summary -p /dev/null -m sergstesh@yahoo.com | sh /usr/sbin/sendmail: No such file or directory "/ibm/home/sergei/dead.letter" 103/2351 . . . message not sent. ". So, should I file a bug against http://gcc.gnu.org/install/test.html because of 'mail' <-> /usr/sbin/sendmail discrepancy ? Anyway, I looked into /ibm/home/sergei/dead.letter file and it contains pretty much the same info I've already posted. If you insist, I can install /usr/sbin/sendmail and try again. Maybe you already have enough info to tell me which of the tests fail due to: 1) problems in the compiler; 2) problems in glibc; 3) problems in the tests themselves ? Thanks in advance.
I looked into source code of 'test_summary' script and it indeed calls the 'Mail' program, the one with capital 'M'. I have never heard of it, I am familiar with 'mail' with small 'm'. On my system it's lrwxrwxrwx 1 root root 14 Jan 12 2006 /usr/bin/Mail -> ../../bin/mail . Is it OK ? I tried ../gcc-3.4.6.src/contrib/test_summary -p /dev/null -m sergstesh@yahoo.com -f | sh - pay attention to '-f', and nothing happens. No mail is sent, no messages on screen. How can I regenerate the Email text produced by the first invokation of 'test_summary' ?