Linux From Scratch: Version 5.0-pre2
Prev | Chapter 6. Installing basic system software | Next

# Installing GCC-3.3.1

    Estimated build time:           11.7 SBU
    Estimated required disk space:  221 MB

## Contents of GCC

(Last checked against version 3.1.)

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

GCC installs the following files:

### Program Files

c++, c++filt, cc (link to gcc), cc1, cc1plus, collect2, cpp, cpp0, g++, gcc, gccbug, gcov and tradcpp0

### Library Files

libgcc.a, libgcc_eh.a, libgcc_s.so, libiberty.a, libstdc++.[a,so], libsupc++.a

##

## GCC Installation Dependencies

(Last checked against version 2.95.3.)

Bash: sh
Binutils: ar, as, ld, nm, ranlib
Coreutils: basename, cat, chmod, cp, dirname, echo, expr, hostname, ln
ls, mkdir, mv, rm, sleep, tail, touch, tr, true, uname
Diffutils: cmp
Find: find
GCC: cc, cc1, collect2, cpp0, gcc
Grep: egrep, grep
Make: make
Sed: sed
Tar: tar
Texinfo: install-info, makeinfo

##

## Installation of GCC

> Note: The test suite for GCC in this section is considered critical. Our advice is to not skip it under any circumstances.

This package is known to behave badly when you have changed its default optimization flags (including the -march and -mcpu options). Therefore, if you have defined any environment variables that override default optimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting or modifying them when building GCC.

This time we will build both the C and the C++ compiler, so you'll have to unpack the GCC-core and the GCC-g++ tarball -- they will unfold into the same directory. You should likewise extract the GCC-testsuite package. The full GCC package contains even more compilers. Instructions for building these can be found at http://www.linuxfromscratch.org/blfs/view/cvs/general/gcc.html.

    patch -Np1 -i ../gcc-3.3.1-no_fixincludes-2.patch
    patch -Np1 -i ../gcc-3.3.1-suppress-libiberty.patch

The second patch here suppresses the installation of libiberty from GCC, as we will use the one provided by binutils instead.

The GCC documentation recommends building GCC outside of the source directory in a dedicated build directory:

    mkdir ../gcc-build
    cd ../gcc-build

Now prepare GCC for compilation:

    ../gcc-3.3.1/configure --prefix=/usr \
        --enable-shared --enable-threads=posix \
        --enable-__cxa_atexit --enable-clocale=gnu \
        --enable-languages=c,c++

Compile the package:

    make

> Note: At this point it is strongly recommended to repeat the sanity check we performed earlier in the chapter. Refer back to the "Re-adjusting the toolchain" section and repeat the check. If the results are wrong then most likely, you erroneously applied the GCC Specs patch from Chapter 5.

Test the results, but don't stop at errors (you'll remember the few known ones):

    make -k check

And install the package:

    make install

Some packages expect the C PreProcessor to be installed in the `/lib` directory. To honor 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

Prev | Home | Next
Installing Binutils-2.14 | Up | Installing Coreutils-5.0