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

&gcc-url;

GCC As in , apply the following sed to force the build to use the -fomit-frame-pointer compiler flag in order to ensure consistent compiler builds: case `uname -m` in i?86) sed -i 's/^T_CFLAGS =$/& -fomit-frame-pointer/' gcc/Makefile.in ;; esac 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: SED=sed \ ../gcc-&gcc-version;/configure \ --prefix=/usr \ --enable-shared \ --enable-threads=posix \ --enable-__cxa_atexit \ --enable-clocale=gnu \ --enable-languages=c,c++ \ --disable-multilib \ --disable-bootstrap \ --with-system-zlib Note that for other languages, there are some prerequisites that are not available. See the BLFS Book for instructions on how to build all the GCC supported languages. SED=sed Setting this environment variable prevents a hard-coded path to /tools/bin/sed. --with-system-zlib This switch tells GCC to link to the system installed copy of the Zlib library, rather than its own internal copy. Compile the package: make In this section, the test suite for GCC is considered critical. Do not skip it under any circumstance. One set of tests in the GCC test suite is known to exhaust the stack, so increase the stack size prior to running the tests: ulimit -s 32768 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 and . 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 to 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 Depending on your machine architecture, the above may differ slightly, the difference usually being the name of the directory after /usr/lib/gcc. If your machine is a 64-bit system, you may also see a directory named lib64 towards the end of the string. The important thing to look for here is that gcc has found all three crt*.o files under the /usr/lib directory. grep -B4 '^ /usr/include' dummy.log #include <...> search starts here: /usr/lib/gcc/i686-pc-linux-gnu/&gcc-version;/include /usr/local/include /usr/lib/gcc/i686-pc-linux-gnu/&gcc-version;/include-fixed /usr/include Again, note that the directory named after your target triplet may be different than the above, depending on your architecture. As of version 4.3.0, GCC now unconditionally installs the limits.h file into the private include-fixed directory, and that directory is required to be in place. SEARCH_DIR("/usr/i686-pc-linux-gnu/lib32") SEARCH_DIR("/usr/local/lib32") SEARCH_DIR("/lib32") SEARCH_DIR("/usr/lib32") SEARCH_DIR("/usr/i686-pc-linux-gnu/lib") SEARCH_DIR("/usr/local/lib") SEARCH_DIR("/lib") SEARCH_DIR("/usr/lib"); A 64-bit system may see a few different directories. For example, here is the output from an x86_64 machine: SEARCH_DIR("/usr/x86_64-unknown-linux-gnu/lib64") SEARCH_DIR("/usr/local/lib64") SEARCH_DIR("/lib64") SEARCH_DIR("/usr/lib64") SEARCH_DIR("/usr/x86_64-unknown-linux-gnu/lib") SEARCH_DIR("/usr/local/lib") SEARCH_DIR("/lib") SEARCH_DIR("/usr/lib"); Finally, move a misplaced file: mkdir -pv /usr/share/gdb/auto-load/usr/lib mv -v /usr/lib/*gdb.py /usr/share/gdb/auto-load/usr/lib Installed programs Installed libraries Installed directories c++, cc (link to gcc), cpp, g++, gcc, gcc-ar, gcc-nm, gcc-ranlib, and gcov libasan.{a,so}, libatomic.{a,so}, libgcc.a, libgcc_eh.a, libgcc_s.so, libgcov.a, libgomp.{a,so}, libiberty.a, libitm.{a,so}, liblto_plugin.so, libmudflap.{a,so}, libmudflapth.{a,so}, libquadmath.{a,so}, libssp.{a,so}, libssp_nonshared.a, libstdc++.{a,so}, libsupc++.a and libtsan.{a,so} /usr/include/c++, /usr/lib/gcc, /usr/libexec/gcc, /usr/share/gcc-&gcc-version; 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 gcc-ar A wrapper around ar that adds a plugin to the command line. This program is only used to add "link time optization" and is not useful with the default build options. gc-ar gcc-nm A wrapper around nm that adds a plugin to the command line. This program is only used to add "link time optization" and is not useful with the default build options. gc-nm gcc-ranlib A wrapper around ranlib that adds a plugin to the command line. This program is only used to add "link time optization" and is not useful with the default build options. gc-ranlib gcov A coverage testing tool; it is used to analyze programs to determine where optimizations will have the most effect gcov libasan The Address Sanitizer runtime library libasan libgcc Contains run-time support for gcc libgcc* libgcov This library is linked in to a program when GCC is instructed to enable profiling libgcov libgomp GNU implementation of the OpenMP API for multi-platform shared-memory parallel programming in C/C++ and Fortran libgomp libiberty Contains routines used by various GNU programs, including getopt, obstack, strerror, strtol, and strtoul libiberty liblto_plugin GCC's Link Time Optimization (LTO) plugin allows GCC to perform optimizations across compilation units. liblto_plugin* libmudflap Contains routines that support GCC's bounds checking functionality libmudflap* libquadmath GCC Quad Precision Math Library API libquadmath* 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++ libtsan The Thread Sanitizer runtime library libtsan