Re: Compiling problems 1.3.85

tim middlekoop (mtim@lab.housing.fsu.edu)
Tue, 9 Apr 1996 10:34:57 -0400 (EDT)


I am starting to beleve that these signal 11 problems are a result of AMD
cpu's and a quicker memcpy. Many people suggest that disabling the
secondary cash solves signal 11 problems, It does for me. Possibly
disabling the secondary cache has the same problem solving effect as the
slower memcpy.
tim...

--
Tim Middelkoop                                   O
http://intrism.hcsys.com/~mtim                  /\,
mtim@freenet.tlh.fl.us                        \/\
----Try linux today----                         /

GE d- s+:- a22 C++ UL++ P++++ L+++ E+> W++ N+ o? K? w--(++) O M V-- PS+ PE Y+ PGP t 5 X R- tv b++ DI? D+ G e+ h-- r-- y+

On Tue, 9 Apr 1996, Antoine Reid wrote:

> On Tue, 9 Apr 1996, Alex Frausin wrote: > > > Date: Tue, 9 Apr 1996 10:28:49 +0200 (MET DST) > > From: Alex Frausin <alex@gd.chalmers.se> > > To: linux-kernel@vger.rutgers.edu > > Subject: Compiling problems 1.3.85 > > > > > > gcc -D__KERNEL__ -I/usr/src/linux/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 floppy.o floppy.c > > cpp: output pipe has been closed > > gcc: Internal compiler error: program cc1 got fatal signal 11 > > make[3]: *** [floppy.o] Error 1 > > > > Any suggestions/patches/fixes ???? > > > > /Alex > > -- > > I got the same error, _only_ with 1.3.85 AND gcc 2.7.2p > I was using a Fresh complete new source and it did this more than once, > after deleting the source and restarting from the freshly untarred tree. > I just reinstalled the 2.7.2 binary GCC and all works well. > > Hope this helps. > > > --- > Antoine Reid > Reply to: fluke@Mlink.NET > "We all live in a yellow subroutine..." > Look at http://www.Mlink.NET/~fluke for more info. > >