On Mon, Oct 21, 2002 at 10:18:17PM -0700, nitin panjwani wrote: > I am attaching to samples of my compilation, can you > please check it and tell me what can be the problem. gcc -D__KERNEL__ -I/usr/src/linux-2.4.19/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i386 -nostdinc -I /usr/lib/gcc-lib/i386-linux/2.95.4/include -DKBUILD_BASENAME=vt -c -o vt.o vt.c gcc: Internal compiler error: program cc1 got fatal signal 4 [...] gcc -D__KERNEL__ -I/usr/src/linux-2.4.19/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i386 -nostdinc -I /usr/lib/gcc-lib/i386-linux/2.95.4/include -DKBUILD_BASENAME=ide_cd -c -o ide-cd.o ide-cd.c gcc: Internal compiler error: program cc1 got fatal signal 4 You can look up signal 4 with "kill -l": 1) SIGHUP 2) SIGINT 3) SIGQUIT 4) SIGILL [...] SIGILL is Illegal Instruction. I can think of two reasons for this: (a) you've installed a 586 or 686 or athlon or other processor-specific optimized compiler or libraries -- when that instruction gets executed on a processor that doesn't support the instruction, the kernel sends the process SIGILL. (b) you've got bad memory. The cpu tries to execute some instructions stored in memory that has become corrupted. This one can be discovered by using a tool such as memtest86 to test your memory. -- Nothing says, "Superpower" like bombing a country that is poor and hungry. -- Ken Brush
Attachment:
pgp00187.pgp
Description: PGP signature
