Problems compiling kernel, RH5 2.0.31

Problems compiling kernel, RH5 2.0.31

Post by M » Wed, 20 May 1998 04:00:00



Hi folks! I'm kinda new to Linux, and thought someone could help. I'm running
a Pentium box with 64MB EDO DRAM, and the kernel is compiled for a 386 out of
the box. I ran 'make xconfig' and set all the options as I like them, then
'make dep; make clean' (after saving the options). This was no problem.

However, when I 'make vmlinux' (to compile the final kernel), I get:

gcc -D__KERNEL__ -I/usr/sec/linux-2.0.31/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 panic.o panic.c
gcc: Internal compiler error: program cc1 got fatal signal 11
make[2]: *** [panic.o] Error 1
make[2]: Leaving directory '/usr/src/linux-2.0.31/kernel'
make[1]: *** [first_rule] Error 2
make[1]: Leaving directory '/usr/src/linux-2.0.31/kernel'
make: *** [linuxsubdirs] Error 2

It doesn't always fail on the same file (in this example it's panic.o) -- it
sometimes fails on other files. It always fails within the first 15 seconds of
starting make on some file (usually different each time). What seems to be my
problem, and how can I 'make vmlinux' without errors, or more specifically,
this error?

Thanks in advance.

-- Alex Burke
   Toronto, Ontario, Canada

 
 
 

Problems compiling kernel, RH5 2.0.31

Post by Rolf Magnu » Sat, 30 May 1998 04:00:00


 >
 > Hi folks! I'm kinda new to Linux, and thought someone could help. I'm
running
 > a Pentium box with 64MB EDO DRAM, and the kernel is compiled for a
386 out of
 > the box. I ran 'make xconfig' and set all the options as I like them,
then
 > 'make dep; make clean' (after saving the options). This was no
problem.
 >
 > However, when I 'make vmlinux' (to compile the final kernel), I get:
 >
 > gcc -D__KERNEL__ -I/usr/sec/linux-2.0.31/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 panic.o panic.c
 > gcc: Internal compiler error: program cc1 got fatal signal 11
 > make[2]: *** [panic.o] Error 1
 > make[2]: Leaving directory '/usr/src/linux-2.0.31/kernel'
 > make[1]: *** [first_rule] Error 2
 > make[1]: Leaving directory '/usr/src/linux-2.0.31/kernel'
 > make: *** [linuxsubdirs] Error 2
 >
 > It doesn't always fail on the same file (in this example it's
panic.o) -- it
 > sometimes fails on other files. It always fails within the first 15
seconds of
 > starting make on some file (usually different each time). What seems
to be my
 > problem, and how can I 'make vmlinux' without errors, or more
specifically,
 > this error?

This sounds like a memory problem. Maybe your memory timins are wrong
or you have a bad simm. Compiling the linux kernel using gcc is known
as a good memory test. If possible, ask some friend if you could get
his simms test if it is your memory.
(Btw. I think your kernel is configured to be compiled for a 386 cpu.)

 
 
 

1. Redhat 5.0 (2.0.31) kernel compile errors

Man am I ever having a hard time with Redhat 5.0.  The latest snag is
the following compile error for kernel 2.0.31:

make[2]: Entering directory `/usr/src/linux-2.0.31/fs'
gcc -D__KERNEL__ -I/usr/src/linux-2.0.31/include -Wall
-Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strength-reduce -pipe
-m386 -DCPU=386  -c -o inode.o inode.c
inode.c: In function `clear_inode':
inode.c:192: structure has no member named `i_condemned'
inode.c: In function `__iget':
inode.c:647: structure has no member named `i_condemned'
make[2]: *** [inode.o] Error 1
make[2]: Leaving directory `/usr/src/linux-2.0.31/fs'
make[1]: *** [first_rule] Error 2
make[1]: Leaving directory `/usr/src/linux-2.0.31/fs'
make: *** [linuxsubdirs] Error 2

Anybody have any ideas?

DT

2. bbc = linux

3. ppp-2.3.1 does not compile with Linux kernel 2.0.31

4. An Interview with Dr. Edgar Villanueva

5. Problems compiling 2.0.31

6. Mitsumi FX001D - no boot disk works - solved the problem!

7. ping problem with kernel 2.0.31

8. How can linux be such a great networking platform if it's impossible to connect to the network?

9. Ping problem with Kernel 2.0.31

10. Patches against 2.0.31 (Re: List of bugs in 2.0.31)

11. Problems upgrading kernel 2.0.31

12. Problems with kernel 2.0.31 on an Alpha

13. ping problem with kernel 2.0.31