Robert,
I don't think this is a problem with the patch or the inode.c
source file. Signal 4 is SIGILL: Illegal instruction.
I have compiled it twice on my PC without errors.
Anybody know what would cause this? Does Robert need
a newer compiler or what?
~Randy
> From: Robert L. Harris [mailto:[EMAIL PROTECTED]]
>
> When compiling I get some errors, this is the only one that
> wouldn't go away when I re-ran make:
>
> make -C usb
> make[2]: Entering directory `/usr/src/linux-2.2.14/drivers/usb'
> make all_targets
> make[3]: Entering directory `/usr/src/linux-2.2.14/drivers/usb'
> gcc -D__KERNEL__ -I/usr/src/linux-2.2.14/include -Wall
> -Wstrict-prototypes -O2 -fomit-frame-pointer
> -fno-strict-aliasing -D__SMP__ -pipe -fno-strength-reduce
> -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2
> -DCPU=686 -c -o inode.o inode.c
> gcc: Internal compiler error: program cc1 got fatal signal 4
> make[3]: *** [inode.o] Error 1
> make[3]: Leaving directory `/usr/src/linux-2.2.14/drivers/usb'
> make[2]: *** [first_rule] Error 2
> make[2]: Leaving directory `/usr/src/linux-2.2.14/drivers/usb'
> make[1]: *** [_subdir_usb] Error 2
> make[1]: Leaving directory `/usr/src/linux-2.2.14/drivers'
> make: *** [_dir_drivers] Error 2
> {0}:lh:/usr/src/linux>cpp: output pipe has been closed
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
