# GCC-&gcc-version;

The GCC package contains the GNU compiler collection, which includes the C and C++ compilers.

## Installation of 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` 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 -v ../gcc-build
    cd ../gcc-build

Prepare GCC for compilation:

    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

Compile the package:

    make

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`.

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

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

## Contents of GCC

Installed programs Installed libraries Installed directories
- c++, cc (link to gcc), cpp, g++, gcc, gccbug, and gcov libgcc.a, libgcc_eh.a, libgcc_s.so, libgcov.a, libgomp.[a,so], libmudflap.[a,so], libmudflapth.[a,so], libssp.[a,so], libssp_nonshared.a, libstdc++.[a,so], and libsupc++.a /usr/include/c++, /usr/lib/gcc

Short Descriptions

`cc`

- The C compiler

`cpp`

- The C preprocessor; it is used by the compiler to expand the #include, #define, and similar statements in the source files

`c++`

- The C++ compiler

`g++`

- The C++ compiler

`gcc`

- The C compiler

`gccbug`

- A shell script used to help create useful bug reports

`gcov`

- A coverage testing tool; it is used to analyze programs to determine where optimizations will have the most effect

`libgcc`

- Contains run-time support for `gcc`

`libgcov`

- Library that is linked into a program when `gcc` is instructed to enable profiling

`libgomp`

- GNU implementation of the OpenMP API for multi-platform shared-memory parallel programming in C/C++ and Fortran

`libmudflap`

- The libmudflap libraries are used by GCC for instrumenting pointer and array dereferencing operations.

`libssp`

- Contains routines supporting GCC's stack-smashing protection functionality

`libstdc++`

- The standard C++ library

`libsupc++`

- Provides supporting routines for the C++ programming language