> {standard input}:768: Error: no such 386 instruction: `rdmsr'
> {standard input}:770: Error: no such 386 instruction: `wrmsr'
> make[1]: *** [time.o] Error 1
At the suggestion of several people who wrote me, I upgraded my binutils to
2.7.0.3 which made no difference in the problem. as reports:
gat:~> as --version
GNU assembler version 2.7 (i486-unknown-linux), using BFD version 2.7.0.3
I also tried upgrading my gcc from 2.7.2 to 2.7.2.1 as was suggested (using
the bin file from ftp://sunsite/unc.edu/pub/Linux/GCC), but it was a
disaster! gcc quit on the first file with the following complaints:
> gateway:/usr/src/linux# make zImage
> gcc -D__KERNEL__ -I/usr/src/linux-2.0.25/include -Wall -Wstrict-prototypes
> -O2 -fomit-frame-pointer -fno-strength-reduce -pipe -m486 -DCPU=486 -c -o
> init/main.o init/main.c
> stdin:1: numeric constant with no digits
> stdin:1: numeric constant with no digits
> stdin:1: invalid #line
> stdin:13: numeric constant with no digits
> stdin:13: numeric constant with no digits
> stdin:13: invalid #line
> stdin:65: parse error at null character
> stdin:65: virtual memory exhausted
> cpp: output pipe has been closed
> make: *** [init/main.o] Error 1
I reverted to gcc 2.7.2 which has worked for me for dozens of kernel
compiles (as well as numerous other package compiles) with no problem.
It's been suggested that the quick and dirty solution here is to compile
with APM support which will bypass compilation of the problem asm code. I'm
happily running kernel 2.0.22 and don't need 2.0.25 unless it is a step
forward, and having to compile with APM support which I don't need is, IMHO,
a step backward. Can I expect this problem to be fixed in 2.0.26?
-- Lindsay Haisley | "Everything works | PGP public key FMP Computer Services | if you let it" | available via fmouse@fmp.com | (The Roadie) | Internet finger http://www.fmp.com | |