On 4/20/07, anirudh vij <[EMAIL PROTECTED]> wrote: > hi, > i compiled gcc 4.1.2.the configure command was: > ../gcc-4.1.2/configure --prefix=/opt/gcc-4.1.2 --enable-shared > --enable-languages=c,c++ --enable-threads=posix --with-system-zlib > --enable-bootstrap > i am not sure whether the zlib should be there,but the make bootstap > finished without errors. > make -k check gave the following after a very long time: > > > make[3]: Entering directory > `/home/hackman/to-be-built/gcc-build/i686-pc-linux-gnu/libiberty/testsuite' > make[3]: Nothing to be done for `check'. > make[3]: Leaving directory > `/home/hackman/to-be-built/gcc-build/i686-pc-linux-gnu/libiberty/testsuite' > make[2]: Leaving directory > `/home/hackman/to-be-built/gcc-build/i686-pc-linux-gnu/libiberty' > make[1]: Target `check-target' not remade because of errors. > make[1]: Leaving directory > `/home/hackman/to-be-built/gcc-build' > make: *** [do-check] Error 2 > make: Target `check' not remade because of errors. > /home/hackman/to-be-built/gcc-build > > ../gcc-4.1.2/contrib/test_summary |more > > cat <<'EOF' | > LAST_UPDATED: Obtained from SVN: tags/gcc_4_1_2_release revision 121944 > > Native configuration is i686-pc-linux-gnu > > === libmudflap tests === > > > Running target unix > > === libmudflap Summary === > > # of expected passes 1799 > === libstdc++ tests === > > > Running target unix > XPASS: 26_numerics/cmath/c99_classification_macros_c.cc > (test for excess errors) > > === libstdc++ Summary === > > # of expected passes 3390 > # of unexpected successes 1 > # of expected failures 12 > # of unsupported tests 328 > === g++ Summary === > > # of expected passes 12408 > # of unexpected successes 1 > # of expected failures 67 > # of unsupported tests 69 > /home/hackman/to-be-built/gcc-build/stage3-gcc/testsuite/g++/../../g++ > version 4.1.2 > > === gcc tests === > > > Running target unix > > === gcc Summary === > > # of expected passes 173 > /home/hackman/to-be-built/gcc-build/stage3-gcc/xgcc > version 4.1.2 > > > Compiler version: 4.1.2 > Platform: i686-pc-linux-gnu > > configure flags: --prefix=/opt/gcc- 4.1.2 --enable-shared > --enable-threads=posix --with-sys > tem-zlib --enable-bootstrap --enable-languages=c,c++ > EOF > Mail -s "Results for 4.1.2 testsuite on i686-pc-linux-gnu" > [EMAIL PROTECTED] && > mv > /home/hackman/to-be-built/gcc-build/./i686-pc-linux-gnu/libmudflap/testsuite/libmudflap > .sum > /home/hackman/to-be-built/gcc-build/./i686-pc-linux-gnu/libmudflap/testsuite/libmudfl > ap.sum.sent && > mv > /home/hackman/to-be-built/gcc-build/./i686-pc-linux-gnu/libstdc++-v3/testsuite/libstdc+ > +.sum > /home/hackman/to-be-built/gcc-build/./i686-pc-linux-gnu/libstdc++-v3/testsuite/libst > dc++.sum.sent && > mv > /home/hackman/to-be-built/gcc-build/./stage3-gcc/testsuite/g++/g++.sum > /home/hackman/to > -be-built/gcc-build/./stage3-gcc/testsuite/g++/g++.sum.sent > && > mv > /home/hackman/to-be-built/gcc-build/./stage3-gcc/testsuite/gcc/gcc.sum > /home/hackman/to > -be-built/gcc-build/./stage3-gcc/testsuite/gcc/gcc.sum.sent > && > mv > /home/hackman/to-be-built/gcc-build/./i686-pc-linux-gnu/libmudflap/testsuite/libmudflap > .log > /home/hackman/to-be-built/gcc-build/./i686-pc-linux-gnu/libmudflap/testsuite/libmudfl > ap.log.sent && > mv > /home/hackman/to-be-built/gcc-build/./i686-pc-linux-gnu/libstdc++-v3/testsuite/libstdc+ > +.log > /home/hackman/to-be-built/gcc-build/./i686-pc-linux-gnu/libstdc++-v3/testsuite/libst > dc++.log.sent && > mv > /home/hackman/to-be-built/gcc-build/./stage3-gcc/testsuite/g++/g++.log > /home/hackman/to > -be-built/gcc-build/./stage3-gcc/testsuite/g++/g++.log.sent > && > mv > /home/hackman/to-be-built/gcc-build/./stage3-gcc/testsuite/gcc/gcc.log > /home/hackman/to > -be-built/gcc-build/./stage3-gcc/testsuite/gcc/gcc.log.sent > && > true > > > > i planned to install the new gcc in /opt/gcc-4.1.2.Is it right to do it in > face of the make -k check error.Most of the tests seem to pass,but as i am > not very experienced in this,i would like some advice.
Seems nothing wrong with your logs, no unexpected failures. And well, you could test your new GCC with the test code used in the LFS book (At the toolchain part). Tijnema > -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
