Estimated build time: &gcc-time; Estimated required disk space: &gcc-compsize; &aa-gcc-shortdesc; &aa-gcc-desc;   The test suite for GCC in this section is considered critical. Our advice is to not skip it under any circumstance. This package is known to behave badly when you have changed its default optimization flags (including the -march and -mcpu options). Therefore, if you have defined any environment variables that override default optimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting or modifying them when building GCC. This time we will build both the C and the C++ compiler, so you'll have to unpack the GCC-core and the GCC-g++ tarball -- they will unfold into the same directory. You should likewise extract the GCC-testsuite package. The full GCC package contains even more compilers. Instructions for building these can be found at . patch -Np1 -i ../&gcc-nofixincludes-patch; patch -Np1 -i ../&gcc-suppress-libiberty-patch; The second patch here suppresses the installation of libiberty from GCC, as we will use the one provided by binutils instead. Be careful not to apply the GCC specs patch from Chapter 5 here. The GCC documentation recommends building GCC outside of the source directory in a dedicated build directory: mkdir ../gcc-build cd ../gcc-build Now prepare GCC for compilation: ../gcc-&gcc-version;/configure --prefix=/usr \     --enable-shared --enable-threads=posix \     --enable-__cxa_atexit --enable-clocale=gnu \     --enable-languages=c,c++ Compile the package: make Test the results, but don't stop at errors (you'll remember the few known ones): make -k check The test suite notes from are still very much appropriate here. Be sure to refer back there should you have any doubts. And install the package: make install Some packages expect the C PreProcessor to be installed in the /lib directory. To honor those packages, create this symlink: ln -s ../usr/bin/cpp /lib Many packages use the name cc to call the C compiler. To satisfy those packages, create a symlink: ln -s gcc /usr/bin/cc At this point it is strongly recommended to repeat the sanity check we performed earlier in this chapter. Refer back to and repeat the check. If the results are wrong, then most likely you erroneously applied the GCC Specs patch from Chapter 5.