Error compiling GCC 3.2.1

LLeweLLyn Reese
Fri Dec 27 20:56:00 GMT 2002

Max Bane <> writes:

> Hi all. Having difficulting compiling gcc 3.2.1. I'm currently running gcc 
> 2.95.3 on an x86 machine. I've downloaded and extracted the source tarball, 
> and when i do this:
> unset CFLAGS &&
> unset CXXFLAGS &&
> mkdir ../gcc-build &&
> cd ../gcc-build &&
> ../gcc-3.2.1/configure --prefix=/usr --enable-shared \
> --enable-languages=c,c++,objc,f77,java --enable-threads=posix \
> --with-slibdir=/lib --enable-__cxa_atexit --enable-clocale=gnu &&
> make bootstrap
> I get this:
> [... Snip]
> Bootstrapping the compiler
> make[1]: Entering directory `/home/max/dl/gcc-build/gcc'
> make CC="stage1/xgcc -Bstage1/ -B/usr/i686-pc-linux-gnu/bin/" \
>          STAGE_PREFIX=stage1/ \
> STRICT_WARN="-Wtraditional -pedantic -Wno-long-long" libdir=/usr/lib 
> LANGUAGES="c gcov c++ f77 java objc" MAKEOVERRIDES= OUTPUT_OPTION="-o \$@"
> make[2]: Entering directory `/home/max/dl/gcc-build/gcc'
> stage1/xgcc -Bstage1/ -B/usr/i686-pc-linux-gnu/bin/ -c -DIN_GCC    -g -O2 -W 
> -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional 
> -pedantic -Wno-long-long  -DHAVE_CONFIG_H -DGENERATOR_FILE    -I. -I. 
> -I../../gcc-3.2.1/gcc -I../../gcc-3.2.1/gcc/. -I../../gcc-3.2.1/gcc/config 
> -I../../gcc-3.2.1/gcc/../include ../../gcc-3.2.1/gcc/read-rtl.c -o read-rtl.o
> ../../gcc-3.2.1/gcc/read-rtl.c: In function `read_rtx':
> ../../gcc-3.2.1/gcc/read-rtl.c:541: internal error: Segmentation fault
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <URL:> for instructions.
> make[2]: *** [read-rtl.o] Error 1
> make[2]: Leaving directory `/home/max/dl/gcc-build/gcc'
> make[1]: *** [stage2_build] Error 2
> make[1]: Leaving directory `/home/max/dl/gcc-build/gcc'
> make: *** [bootstrap] Error 2
> Any idea what's going on here? I'd really like to get gcc 3 working so I can 
> compile a bunch of other stuff.
> Thanks.

Weird. There are lots of people reporting sucessful builds under

Here are my ideas:

        Double check the install instructions, this time more

    (b) Compare your system and configure options to those found at:

    For both (a) and (b) pay careful attention to the versions of
        software required to build gcc.

    (c) And finally - gcc is *very* sensitive to bad memory - much
        more so than any ram tester you know of.

        Pick a large ball of source you *know* compiles on your
        machine (linux kernel is often a good choice) and build it
        about 10 times. If it fails once, you likely have bad memory,
        and should try replacing it.

More information about the Gcc-help mailing list