Take the 2-minute tour ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.

After getting the latest gcc-4.8.2 from one of the gcc mirrors, I issued the following commands as a mere mortal:

./gcc-4.8.2/configure --enable-languages=ada,c,c++,fortran
make
ulimit -s 32768
make -k check

I was going to run make install, but I saw something at the end of make -k check that concerned me:

vis:

make: *** [do-check] Error 2
make: Target `check' not remade because of errors.

Alas, When I scroll up, I can not find the error output that would explain this last statement.

Here is the output from test_summary:

    === acats tests ===

    === acats Summary ===
# of expected passes        2320
# of unexpected failures    0
Native configuration is x86_64-unknown-linux-gnu

    === gcc tests ===


Running target unix

    === gcc Summary ===

# of expected passes        93833
# of expected failures      261
# of unsupported tests      1371
/home/ted/gcc-build/gcc/xgcc  version 4.8.2 (GCC) 

    === gfortran tests ===


Running target unix
FAIL: gfortran.dg/guality/pr41558.f90  -O0  line 7 s == 'foo'
FAIL: gfortran.dg/guality/pr41558.f90  -O1  line 7 s == 'foo'
FAIL: gfortran.dg/guality/pr41558.f90  -O2  line 7 s == 'foo'
FAIL: gfortran.dg/guality/pr41558.f90  -O3 -fomit-frame-pointer  line 7 s == 'foo'
FAIL: gfortran.dg/guality/pr41558.f90  -O3 -fomit-frame-pointer -funroll-loops  line 7 s == 'foo'
FAIL: gfortran.dg/guality/pr41558.f90  -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions  line 7 s == 'foo'
FAIL: gfortran.dg/guality/pr41558.f90  -O3 -g  line 7 s == 'foo'
FAIL: gfortran.dg/guality/pr41558.f90  -Os  line 7 s == 'foo'

    === gfortran Summary ===

# of expected passes        43596
# of unexpected failures    8
# of expected failures      42
# of unsupported tests      69
/home/ted/gcc-build/gcc/testsuite/gfortran/../../gfortran  version 4.8.2 (GCC) 

    === g++ tests ===


Running target unix

    === g++ Summary ===

# of expected passes        54194
# of expected failures      290
# of unsupported tests      890
/home/ted/gcc-build/gcc/testsuite/g++/../../xg++  version 4.8.2 (GCC) 

    === gnat tests ===


Running target unix

    === gnat Summary ===

# of expected passes        1175
# of expected failures      17
# of unsupported tests      2
/home/ted/gcc-build/gcc/gnatmake version 4.8.2

    === libatomic tests ===


Running target unix

    === libatomic Summary ===

# of expected passes        54
    === libgomp tests ===


Running target unix

    === libgomp Summary ===

# of expected passes        3007
    === libitm tests ===


Running target unix

    === libitm Summary ===

# of expected passes        26
# of expected failures      3
# of unsupported tests      1
    === libmudflap tests ===


Running target unix
FAIL: libmudflap.c++/pass41-frag.cxx ( -O) execution test
FAIL: libmudflap.c++/pass41-frag.cxx (-O2) execution test
FAIL: libmudflap.c++/pass41-frag.cxx (-O3) execution test

    === libmudflap Summary ===

# of expected passes        1433
# of unexpected failures    3
    === libstdc++ tests ===


Running target unix

    === libstdc++ Summary ===

# of expected passes        8642
# of expected failures      45
# of unsupported tests      527

Compiler version: 4.8.2 
Platform: x86_64-unknown-linux-gnu
configure flags: --enable-languages=ada,c,c++,fortran

Does the output above provide the information to explain what went awry during the make -k check command? If so, I'd like to understand... If you obtained the above output, would you feel confident enough in the build of gcc to proceed with installing it and using it, even in a production environment? Note, there are a number of sections that are a complete mystery to me. For example, I have no idea what acats is, or mudflap or itm or gomp.

One last question about the output from test-summary. Right after the above output, I saw the following:

Mail -s "Results for 4.8.2 testsuite on x86_64-unknown-linux-gnu" [email protected] &&
mv /home/ted/gcc-build/./gcc/testsuite/ada/acats/acats.sum /home/ted/gcc-build/./gcc/testsuite/ada/acats/acats.sum.sent &&
mv /home/ted/gcc-build/./gcc/testsuite/gcc/gcc.sum /home/ted/gcc-build/./gcc/testsuite/gcc/gcc.sum.sent &&
mv /home/ted/gcc-build/./gcc/testsuite/gfortran/gfortran.sum /home/ted/gcc-build/./gcc/testsuite/gfortran/gfortran.sum.sent &&
mv /home/ted/gcc-build/./gcc/testsuite/g++/g++.sum /home/ted/gcc-build/./gcc/testsuite/g++/g++.sum.sent &&
mv /home/ted/gcc-build/./gcc/testsuite/gnat/gnat.sum /home/ted/gcc-build/./gcc/testsuite/gnat/gnat.sum.sent &&
mv /home/ted/gcc-build/./x86_64-unknown-linux-gnu/libatomic/testsuite/libatomic.sum /home/ted/gcc-build/./x86_64-unknown-linux-gnu/libatomic/testsuite/libatomic.sum.sent &&
mv /home/ted/gcc-build/./x86_64-unknown-linux-gnu/libgomp/testsuite/libgomp.sum /home/ted/gcc-build/./x86_64-unknown-linux-gnu/libgomp/testsuite/libgomp.sum.sent &&
mv /home/ted/gcc-build/./x86_64-unknown-linux-gnu/libitm/testsuite/libitm.sum /home/ted/gcc-build/./x86_64-unknown-linux-gnu/libitm/testsuite/libitm.sum.sent &&
mv /home/ted/gcc-build/./x86_64-unknown-linux-gnu/libmudflap/testsuite/libmudflap.sum /home/ted/gcc-build/./x86_64-unknown-linux-gnu/libmudflap/testsuite/libmudflap.sum.sent &&
mv /home/ted/gcc-build/./x86_64-unknown-linux-gnu/libstdc++-v3/testsuite/libstdc++.sum /home/ted/gcc-build/./x86_64-unknown-linux-gnu/libstdc++-v3/testsuite/libstdc++.sum.sent &&
mv /home/ted/gcc-build/./gcc/testsuite/ada/acats/acats.log /home/ted/gcc-build/./gcc/testsuite/ada/acats/acats.log.sent &&
mv /home/ted/gcc-build/./gcc/testsuite/gcc/gcc.log /home/ted/gcc-build/./gcc/testsuite/gcc/gcc.log.sent &&
mv /home/ted/gcc-build/./gcc/testsuite/gfortran/gfortran.log /home/ted/gcc-build/./gcc/testsuite/gfortran/gfortran.log.sent &&
mv /home/ted/gcc-build/./gcc/testsuite/g++/g++.log /home/ted/gcc-build/./gcc/testsuite/g++/g++.log.sent &&
mv /home/ted/gcc-build/./gcc/testsuite/gnat/gnat.log /home/ted/gcc-build/./gcc/testsuite/gnat/gnat.log.sent &&
mv /home/ted/gcc-build/./x86_64-unknown-linux-gnu/libatomic/testsuite/libatomic.log /home/ted/gcc-build/./x86_64-unknown-linux-gnu/libatomic/testsuite/libatomic.log.sent &&
mv /home/ted/gcc-build/./x86_64-unknown-linux-gnu/libgomp/testsuite/libgomp.log /home/ted/gcc-build/./x86_64-unknown-linux-gnu/libgomp/testsuite/libgomp.log.sent &&
mv /home/ted/gcc-build/./x86_64-unknown-linux-gnu/libitm/testsuite/libitm.log /home/ted/gcc-build/./x86_64-unknown-linux-gnu/libitm/testsuite/libitm.log.sent &&
mv /home/ted/gcc-build/./x86_64-unknown-linux-gnu/libmudflap/testsuite/libmudflap.log /home/ted/gcc-build/./x86_64-unknown-linux-gnu/libmudflap/testsuite/libmudflap.log.sent &&
mv /home/ted/gcc-build/./x86_64-unknown-linux-gnu/libstdc++-v3/testsuite/libstdc++.log /home/ted/gcc-build/./x86_64-unknown-linux-gnu/libstdc++-v3/testsuite/libstdc++.log.sent && true

What, exactly, is that doing, and why?

share|improve this question

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.