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

&gcc-url;

GCC If building on x86_64, change the default directory name for 64-bit libraries to lib: case $(uname -m) in x86_64) sed -e '/m64=/s/lib64/lib/' \ -i.orig gcc/config/i386/t-linux64 ;; esac The GCC documentation recommends building GCC in a dedicated build directory: mkdir -v build cd build Prepare GCC for compilation: ../configure --prefix=/usr \ LD=ld \ --enable-languages=c,c++ \ --disable-multilib \ --disable-bootstrap \ --with-system-zlib Note that for other programming languages there are some prerequisites that are not yet available. See the BLFS Book GCC page for instructions on how to build all of GCC's supported languages. LD=ld This parameter makes the configure script use the ld installed by the binutils built earlier in this chapter, rather than the cross-built version which would otherwise be used. --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 default stack, so increase the stack size prior to running the tests: ulimit -s 32768 Test the results as a non-privileged user, but do not stop at errors: chown -Rv tester . su tester -c "PATH=$PATH make -k check" To receive a summary of the test suite results, run: ../contrib/test_summary For only the summaries, pipe the output through grep -A7 Summ. Results can be compared with those located at and . Six tests related to get_time are known to fail. These are apparently related to the en_HK locale. Additionally the following tests related to the following files are known to fail with glibc-2.32: asan_test.C, co-ret-17-void-ret-coro.C, pr95519-05-gro.C, pr80166.c. A few unexpected failures cannot always be avoided. The GCC developers are usually aware of these issues, but have not resolved them yet. Unless the test results are vastly different from those at the above URL, it is safe to continue. Install the package and remove an unneeded directory: make install rm -rf /usr/lib/gcc/$(gcc -dumpmachine)/&gcc-version;/include-fixed/bits/ The GCC build directory is owned by tester now and the ownership of the installed header directory (and its content) will be incorrect. Change the ownership to root user and group: chown -v -R root:root \ /usr/lib/gcc/*linux-gnu/&gcc-version;/include{,-fixed} Create a symlink required by the FHS for "historical" reasons. ln -sv ../usr/bin/cpp /lib Add a compatibility symlink to enable building programs with Link Time Optimization (LTO): install -v -dm755 /usr/lib/bfd-plugins ln -sfv ../../libexec/gcc/$(gcc -dumpmachine)/&gcc-version;/liblto_plugin.so \ /usr/lib/bfd-plugins/ 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 some sanity checks: /usr/lib/gcc/x86_64-pc-linux-gnu/&gcc-version;/../../../../lib/crt1.o succeeded /usr/lib/gcc/x86_64-pc-linux-gnu/&gcc-version;/../../../../lib/crti.o succeeded /usr/lib/gcc/x86_64-pc-linux-gnu/&gcc-version;/../../../../lib/crtn.o succeeded Depending on your machine architecture, the above may differ slightly. The difference will be the name of the directory after /usr/lib/gcc. 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/x86_64-pc-linux-gnu/&gcc-version;/include /usr/local/include /usr/lib/gcc/x86_64-pc-linux-gnu/&gcc-version;/include-fixed /usr/include Again, the directory named after your target triplet may be different than the above, depending on your system architecture. SEARCH_DIR("/usr/x86_64-pc-linux-gnu/lib64") SEARCH_DIR("/usr/local/lib64") SEARCH_DIR("/lib64") SEARCH_DIR("/usr/lib64") SEARCH_DIR("/usr/x86_64-pc-linux-gnu/lib") SEARCH_DIR("/usr/local/lib") SEARCH_DIR("/lib") SEARCH_DIR("/usr/lib"); A 32-bit system may see a few different directories. For example, here is the output from an i686 machine: 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"); 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, gcov, gcov-dump, and gcov-tool libasan.{a,so}, libatomic.{a,so}, libcc1.so, libgcc.a, libgcc_eh.a, libgcc_s.so, libgcov.a, libgomp.{a,so}, libitm.{a,so}, liblsan.{a,so}, liblto_plugin.so, libquadmath.{a,so}, libssp.{a,so}, libssp_nonshared.a, libstdc++.{a,so}, libstdc++fs.a, libsupc++.a, libtsan.{a,so}, and libubsan.{a,so} /usr/include/c++, /usr/lib/gcc, /usr/libexec/gcc, and /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 optimization" 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 optimization" 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 optimization" 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 gcov-dump Offline gcda and gcno profile dump tool gcov-dump gcov-tool Offline gcda profile processing tool gcov-tool libasan The Address Sanitizer runtime library libasan libatomic GCC atomic built-in runtime library libatomic libcc1 The C preprocessing library libcc1 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 liblsan The Leak Sanitizer runtime library liblsan liblto_plugin GCC's Link Time Optimization (LTO) plugin allows GCC to perform optimizations across compilation units liblto_plugin 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++ libstdc++fs ISO/IEC TS 18822:2015 Filesystem library libstdc++fs libsupc++ Provides supporting routines for the C++ programming language libsupc++ libtsan The Thread Sanitizer runtime library libtsan libubsan The Undefined Behavior Sanitizer runtime library libubsan