%general-entities; %patches-entities; ]> GCC-&gcc-version; GCC <para>The GCC package contains the GNU compiler collection, which includes the C and C++ compilers.</para> <segmentedlist> <segtitle>&buildtime;</segtitle> <segtitle>&diskspace;</segtitle> <seglistitem> <seg>Not checked yet</seg> <seg>Not checked yet</seg> </seglistitem> </segmentedlist> <segmentedlist> <segtitle>&dependencies;</segtitle> <seglistitem> <seg>Bash, Binutils, Coreutils, Diffutils, Findutils, Gawk, Gettext, Glibc, Grep, Make, Perl, Sed, and Texinfo</seg> </seglistitem> </segmentedlist> </sect2> <sect2 role="installation"> <title>Installation of GCC This package is known to have issues when its default optimization flags (including the and options) are changed. If any environment variables that override default optimizations have been defined, such as CFLAGS and CXXFLAGS, unset them when building 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 GCC documentation recommends building GCC outside of the source directory in a dedicated build directory: mkdir ../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-c99 --enable-long-long \ --enable-clocale=gnu --enable-languages=c,c++ --disable-libstdcxx-pch 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 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. 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. 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 -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 Contents of GCC Installed programs Installed libraries c++, cc (link to gcc), cpp, g++, gcc, gccbug, and gcov libgcc.a, libgcc_eh.a, libgcc_s.so, libstdc++.[a,so], and libsupc++.a 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 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* libstdc++ The standard C++ library libstdc++ libsupc++ Provides supporting routines for the C++ programming language libsupc++