%general-entities; ]> Check if there is PTYs for the test suites: expect -c "spawn ls" Apply two patches: patch -Np1 -i ../gcc-&gcc-version;-no_fixincludes-1.patch patch -Np1 -i ../gcc-&gcc-version;-specs-2.patch Create a separate build directory again: mkdir ../gcc-build cd ../gcc-build Now prepare GCC for compilation: ../gcc-&gcc-version;/configure --prefix=/tools \ --libexecdir=/tools/lib --with-local-prefix=/tools \ --enable-clocale=gnu --enable-shared \ --enable-threads=posix --enable-__cxa_atexit \ --enable-languages=c,c++ --disable-libstdcxx-pch Compile the package: make Test the results make -k check To get a summary of the test suite results, run this: ../gcc-&gcc-version;/contrib/test_summary For only the summaries, pipe the output through grep -A7 Summ Results can be compared to those posted to the gcc-testresults mailing list to see similar configurations to the one being built. For an example of how current GCC-&gcc-version; should look on i686-pc-linux-gnu, see . And finally install the package: make install At this point it is strongly recommended to repeat the sanity check we performed earlier in this chapter. Refer back to and repeat the little test compilation. If the result is wrong, then most likely you forgot to apply the above mentioned GCC Specs patch.