Re: cc1 - fatal signal 11 during build
Steven N. Hirsch (shirsch@ibm.net)
Sun, 17 Nov 1996 12:49:29 -0500
Victor Vaughn wrote:
>
> I am trying to compile kernels for my new AMD-K5-PR100 and for my
> old Intel 386-25MHz. I'll be testing out the 386 as a firewall with PPP
> over a dial-up connection.
>
> Each time I try 'make clean ; make zImage', GCC stops compiling with an
> error similar to the following, usually on sys.c or module.c:
>
> gcc -D__KERNEL__ -I/usr/src/linux-2.0.25/include -Wall
> -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strength-reduce -pipe
> -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2 -DCPU=586 -c
> -o sys.o sys.c
> gcc: Internal compiler error: program cc1 got fatal signal 11
> make[2]: *** [sys.o] Error 1
> make[2]: Leaving directory `/usr/src/linux-2.0.25/kernel'
> make[1]: *** [first_rule] Error 2
> make[1]: Leaving directory `/usr/src/linux-2.0.25/kernel'
>
> I've deleted the source for 2.0.25 and loaded 2.1.10 instead. I also
> reinstalled GCC from a partition holding Slackware 3.1. Compiling still
> stops on the same kind of error.
>
> I've built 2.0.25 not too long ago without fatal errors. What could be
> causing this internal error?
Unfortunately, this is usually an indication of defective DRAM and/or
inappropriate chipset configuration. I'll bet that it occurs
non-deterministically, correct? Try slowing down memory access in the
appropriate CMOS screen.
Steve