any problems with gcc 3.0/3.1 and compiling 2.4.18 on ppc?

Andrew Bradley andrew-bradley at
Wed Apr 3 07:36:45 EST 2002


I set the switches on my G3 card to the factory processor speed and a
setting lower on the factory cache speed and now the intermittent crash
has disappeared.

Thanks to your voice of reason.

I shall get back to building GCC 3.x and using GCC 3.0.2 to replicate my
work environment.


On Tuesday, April 2, 2002, at 09:33  pm, Franz Sirl wrote:

> On Tuesday 02 April 2002 22:22, Andrew Bradley wrote:
>> Hi Chris,
>> I recently built the  2.4.18+patch kernel (patch details where on
>> using "gcc version 2.95.3 20010319 (2.95.4
>> CVS + prerelease/franzo/20010912)" with out a hitch.
>> But my main goal is to use g++ 3.x as my default compiler to mimic GCC
>> 3.0.2 on my solaris and linux systems I be using since November.
>> I tried  ( and found that there
>> seems
>> to be an intermittent crash with the compiler.
>> I also tried building many of the snap shots. My last try was
>> gcc-20020318.
>> The Intermittent crashes sometimes go a way when I retry.
>> stage1/xgcc -Bstage1/ -B/usr/local/powerpc-unknown-linux-gnu/bin/ -c
>> -DIN_GCC    -g -O2 -W -Wall -Wwrite-strings -Wstrict-prototypes
>> -Wmissing-prototypes -Wtradi
>> ../../gcc-20020318/gcc/expmed.c: In function `expand_mult':
>> ../../gcc-20020318/gcc/expmed.c:2574: internal error: Segmentation
>> fault
>> Please submit a full bug report,
>> with preprocessed source if appropriate.
>> See <URL:> for instructions.
>> make[2]: *** [expmed.o] Error 1
>> make[2]: Leaving directory `/root/snap_shot/config/gcc'
>> make[1]: *** [stage2_build] Error 2
>> make[1]: Leaving directory `/root/snap_shot/config/gcc'
>> make: *** [bootstrap] Error 2
> Are you sure you don't have any HW problems here? I'm building the
> compiler
> nearly daily on 2 different machines without such problems.
>> I also tried downloading code sourcery's snap shots at
>> The gcc-20020318 was incomplete.
> The build machine had some troubles, should be fixed now.
> Franz.

** Sent via the linuxppc-dev mail list. See

More information about the Linuxppc-dev mailing list