%general-entities; ]> GCC The following patch contains a number of updates to the &gcc-version; branch by the GCC developers: patch -Np1 -i ../&gcc-branch_update-patch; Apply a sed subsitution that will suppress the execution of the fixincludes script: 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: SED=sed CC="gcc -isystem /usr/include" \ CXX="g++ -isystem /usr/include" \ LDFLAGS="-Wl,-rpath-link,/usr/lib:/lib" \ ../gcc-&gcc-version;/configure --prefix=/usr \ --libexecdir=/usr/lib --enable-shared --enable-threads=posix \ --enable-__cxa_atexit --enable-c99 --enable-long-long \ --enable-clocale=gnu --enable-languages=c,c++ \ --disable-multilib --disable-libstdcxx-pch \ --disable-isl-version-check --with-system-zlib \ --enable-checking=release --enable-libstdcxx-time Compile the package: make The test suite for GCC is considered critical. Do not skip it under any circumstance. Increase the stack size prior to running the tests: ulimit -s 32768 Test the results, but do not stop at errors: make -k check The -k flag is used to make the test suite run through to completion and not stop at the first failure. The GCC test suite is very comprehensive and is almost guaranteed to generate a few failures. 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. A few unexpected failures cannot always be avoided. The GCC developers are usually aware of these issues, but have not resolved them yet. Install the package: make install Install the libiberty header file that is needed by some packages: cp -v ../gcc-&gcc-version;/include/libiberty.h /usr/include 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 Finally, move a misplaced file: 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, 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/share/gcc-&gcc-version; Short Descriptions 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 c++ The C++ compiler c++ g++ The C++ compiler g++ gcc The C compiler gcc 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 Library that is linked into 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 libmudflap The libmudflap libraries are used by GCC for instrumenting pointer and array dereferencing operations. 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++ libtsan The Thread Sanitizer runtime library libtsan