On Sun, 3 Dec 2000, mike ledoux <[EMAIL PROTECTED]> wrote:
> On Sat, 2 Dec 2000, dsbelile wrote:
>
> >anyone know what the hell is going on here ? ive never seen an error
> >like this. is my compiler crapping out ? maybe im just really tired. im
> >running 2.2.17 on other machines and had no problem till now. here is
> >the error :
> >
> >cc -D__KERNEL__ -I/usr/src/linux-2.2.17/include -Wall
> >-Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe
> >-fno-strength-reduce -m486 -malign-loops=2 -malign-jumps=2
> >-malign-functions=2 -DCPU=586 -DEXPORT_SYMTAB -c ll_rw_blk.c
> >cc: Internal compiler error: program cc1 got fatal signal 11
> >make[3]: *** [ll_rw_blk.o] Error 1
> >make[3]: Leaving directory `/usr/src/linux-2.2.17/drivers/block'
> >make[2]: *** [first_rule] Error 2
> >make[2]: Leaving directory `/usr/src/linux-2.2.17/drivers/block'
> >make[1]: *** [_subdir_block] Error 2
> >make[1]: Leaving directory `/usr/src/linux-2.2.17/drivers'
> >make: *** [_dir_drivers] Error 2
> >{standard input}: Assembler messages:
> >{standard input}:0: Warning: end of file not at end of a line; newline
> >inserted
>
> See the SIG11 FAQ at:
>
> http://www.bitwizard.nl/sig11/
>
> for suggestions on how to deal with this. Most of the time this means
> you've got some bad memory.
Yes, if compiling had been working fine before, this is likely memory
going bad.
However, for my wife's new machine I found the solution to this same
sig11 problem was to dial the Motherboard speed down from 100 MHz to 66
MHz with the machine working fine (1 1/2 years) since then.
Karl
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
