Which machine?  I had oodles of problems (as did others) with RH 7.0
compiling 2.2.... well, *any* kernel.  Finally had to "downgrade" my gcc,
as well as some include files.  OTOH, if this isn't an RH 7.0 box, what is
it?  How does it differ from the other machines on which you had no
problems compiling?

-Ken

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
> 
> [1]+  Exit 2                  make dep && make clean && make bzImage
> [root@elf linux]#
> 
> thanks in advance.
> 
> chris
> 
> 
> 
> **********************************************************
> 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
> **********************************************************
> 



**********************************************************
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
**********************************************************

Reply via email to