%general-entities; ]> gcc &gcc-version;

&gcc-url;

GCC Apply a sed substitution that will suppress the installation of libiberty.a. The version of libiberty.a provided by Binutils will be used instead: sed -i 's/install_to_$(INSTALL_DEST) //' libiberty/Makefile.in The bootstrap build performed in built GCC with the -fomit-frame-pointer compiler flag. Non-bootstrap builds omit this flag by default, so apply the following sed to use it in order to ensure consistent compiler builds: sed -i 's/^XCFLAGS =$/& -fomit-frame-pointer/' gcc/Makefile.in The fixincludes script is known to occasionally erroneously attempt to "fix" the system headers installed so far. As the headers installed by GCC-&gcc-version; and Glibc-&glibc-version; are known to not require fixing, issue the following command to prevent the fixincludes script from running: sed -i 's@\./fixinc\.sh@-c true@' gcc/Makefile.in The GCC documentation recommends building GCC outside of the source directory in a dedicated build directory: mkdir -v ../gcc-build cd ../gcc-build Prepare GCC for compilation: ../gcc-&gcc-version;/configure --prefix=/usr \ --libexecdir=/usr/lib --enable-shared \ --enable-threads=posix --enable-__cxa_atexit \ --enable-clocale=gnu --enable-languages=c,c++ \ --disable-bootstrap Compile the package: make In this section, the test suite for GCC is considered critical. Do not skip it under any circumstance. Test the results, but do not stop at errors: make -k check To receive a summary of the test suite results, run: ../gcc-&gcc-version;/contrib/test_summary For only the summaries, pipe the output through grep -A7 Summ. Results can be compared with those located at . A few unexpected failures cannot always be avoided. The GCC developers are usually aware of these issues, but have not resolved them yet. In particular, the libmudflap tests are known be particularly problematic as a result of a bug in GCC (). Unless the test results are vastly different from those at the above URL, it is safe to continue. Install the package: make install Some packages expect the C preprocessor to be installed in the /lib directory. To support those packages, create this symlink: ln -sv ../usr/bin/cpp /lib Many packages use the name cc to call the C compiler. To satisfy those packages, create a symlink: ln -sv gcc /usr/bin/cc Now that our final toolchain is in place, it is important to again ensure that compiling and linking will work as expected. We do this by performing the same sanity checks as we did earlier in the chapter: /usr/lib/gcc/i686-pc-linux-gnu/&gcc-version;/../../../crt1.o succeeded /usr/lib/gcc/i686-pc-linux-gnu/&gcc-version;/../../../crti.o succeeded /usr/lib/gcc/i686-pc-linux-gnu/&gcc-version;/../../../crtn.o succeeded grep -B3 '^ /usr/include' dummy.log #include <...> search starts here: /usr/local/include /usr/lib/gcc/i686-pc-linux-gnu/&gcc-version;/include /usr/include SEARCH_DIR("/usr/i686-pc-linux-gnu/lib") SEARCH_DIR("/usr/local/lib") SEARCH_DIR("/lib") SEARCH_DIR("/usr/lib"); Installed programs Installed libraries c++, cc (link to gcc), cpp, g++, gcc, gccbug, and gcov libgcc.a, libgcc_eh.a, libgcc_s.so, libmudflap.{a,so}, libssp.{a,so}, libstdc++.{a,so}, and libsupc++.a Short Descriptions c++ The C++ compiler c++ cc The C compiler cc cpp The C preprocessor; it is used by the compiler to expand the #include, #define, and similar statements in the source files cpp g++ The C++ compiler g++ gcc The C compiler gcc gccbug A shell script used to help create useful bug reports gccbug gcov A coverage testing tool; it is used to analyze programs to determine where optimizations will have the most effect gcov libgcc Contains run-time support for gcc libgcc* libmudflap Contains routines that support GCC's bounds checking functionality libmudflap* libssp Contains routines supporting GCC's stack-smashing protection functionality libssp* libstdc++ The standard C++ library libstdc++ libsupc++ Provides supporting routines for the C++ programming language libsupc++