[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Arghh! Can't compile the kernel!

could be a sign of bad hardware, last week i got similar symtoms from a
brand new Abit BE6-II with both a P3-800 and P2-450 in it, swapped
mainboards and the problem went away, piece of shit abits every single one
ive ever had has failed.

linux does stress a system out more then the average OS, so it is also
more likely to show problems with flaky hardware.


On Fri, 4 Aug 2000, Karl Matheson wrote:

mkarl1 >Alright,
mkarl1 >
mkarl1 >I finally got Slink installed and running on my new computer, but I need
mkarl1 >more help.  When I try to compile the kernel, I got the following errors (I
mkarl1 >think when it's almost done):
mkarl1 >
mkarl1 ><SNIP>
mkarl1 >kernel is compiling fine
mkarl1 ></SNIP>
mkarl1 >xdr.c: In function 'nlmsvc_decode_lockargs':
mkarl1 >xdr.c:271: internal error--unrecognizable insn:
mkarl1 >(jump_insn 1127 1123 1128 (return) -1 (nil)
mkarl1 >    (nil))
mkarl1 >gcc: Internal compiler error: program cc1 got fatal signal 6
mkarl1 >make [3]: *** [xdr.o] Error 1
mkarl1 >make [3]: Leaving directory '/usr/src/linux/fs/lockd'
mkarl1 >make [2]: *** [first_rule] Error 2
mkarl1 >make [2]: Leaving directory '/usr/src/linux/fs/lockd'
mkarl1 >make [1]: *** [_subdir_lockd] Error 2
mkarl1 >make [1]: Leaving directory '/usr/src/linux/fs'
mkarl1 >make: *** [_dir_fs] Error 2
mkarl1 >tux:/usr/src/linux# cpp: output pipe has been closed
mkarl1 >
mkarl1 >What's going on?
mkarl1 >
mkarl1 >Thanks for your time,
mkarl1 >Cameron Matheson
mkarl1 >
mkarl1 >
mkarl1 >-- 
mkarl1 >Unsubscribe?  mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null
mkarl1 >

6:52pm up 27 days, 2:29, 2 users, load average: 0.46, 0.13, 0.03

Reply to: