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

Compiling Kernel: Problem with sparc64-linux-ld



Hello,

I tried to compile 2.4.12 on my Ultra1, but I got an error message
that the 'sparc64-linux-ld' command would be missing.
In the debian mailing list archiv, it was said that one only has to do
a symlink to the 'ld' command. I did so, but now I get the following
error:

-----------
sparc64-linux-ld  -r -o kernel.o sched.o dma.o fork.o exec_domain.o panic.o 
printk.o
module.o exit.o itimer.o info.o time.o softirq.o resource.o sysctl.o acct.o 
capability.o ptrace.o timer.o user.o signal.o sys.o kmod.o context.o ksyms.o
sparc64-linux-ld: warning: sparc:v9a architecture of input file `sched.o' is 
incompatible with sparc output
sparc64-linux-ld: warning: sparc:v9 architecture of input file `dma.o' is 
incompatible with sparc output
sparc64-linux-ld: warning: sparc:v9 architecture of input file `fork.o' is 
incompatible with sparc output
sparc64-linux-ld: warning: sparc:v9 architecture of input file 
`exec_domain.o' is incompatible with sparc output
sparc64-linux-ld: warning: sparc:v9 architecture of input file `panic.o' is 
incompatible with sparc output
sparc64-linux-ld: warning: sparc:v9 architecture of input file `printk.o' is 
incompatible with sparc output
sparc64-linux-ld: warning: sparc:v9 architecture of input file `module.o' is 
incompatible with sparc output
sparc64-linux-ld: warning: sparc:v9 architecture of input file `exit.o' is 
incompatible with sparc output
sparc64-linux-ld: warning: sparc:v9 architecture of input file `itimer.o' is 
incompat
le with sparc output
sparc64-linux-ld: warning: sparc:v9 architecture of input file `time.o' is 
incompatible with sparc output
sparc64-linux-ld: warning: sparc:v9 architecture of input file `softirq.o' is 
incompatible with sparc output
sparc64-linux-ld: warning: sparc:v9 architecture of input file `resource.o' 
is incompatible with sparc output
sparc64-linux-ld: warning: sparc:v9 architecture of input file `sysctl.o' is 
incompatible with sparc output
sparc64-linux-ld: warning: sparc:v9 architecture of input file `acct.o' is 
incompatible with sparc output
sparc64-linux-ld: warning: sparc:v9 architecture of input file `capability.o' 
is incompatible with sparc output
sparc64-linux-ld: warning: sparc:v9 architecture of input file `ptrace.o' is 
incompatible with sparc output
sparc64-linux-ld: warning: sparc:v9 architecture of input file `timer.o' is 
incompatible with sparc output
sparc64-linux-ld: warning: sparc:v9 architecture of input file `user.o' is 
incompatible with sparc output
sparc64-linux-ld: warning: sparc:v9 architecture of input file `signal.o' is 
incompatible with sparc output
sparc64-linux-ld: warning: sparc:v9 architecture of input file `sys.o' is 
incompatible with sparc output
sparc64-linux-ld: warning: sparc:v9 architecture of input file `kmod.o' is 
incompatible with sparc output
sparc64-linux-ld: warning: sparc:v9 architecture of input file `context.o' is 
incompatible with sparc output
sparc64-linux-ld: warning: sparc:v9 architecture of input file `ksyms.o' is 
incompatible with sparc output
make[2]: *** [kernel.o] Segmentation fault
make[2]: *** Deleting file `kernel.o'
make[2]: Leaving directory `/usr/src/linux-2.4.12/kernel'
make[1]: *** [first_rule] Error 2
make[1]: Leaving directory `/usr/src/linux-2.4.12/kernel'
make: *** [_dir_kernel] Error 2
----------------

Well, I made a link in /usr/bin/ called 'sparc64-linux-ld' to
'/usr/bin/ld'. But it looks as if this is not the right, sparc64
compatible 'ld'.
Why isn't there a 'make bzImage'?? I've to do 'make vmlinux', but I
think that this image won't be compressed. Will SILO be able to load
it?

thanks,
 Moritz

-- 
Once upon a time there was a DOS user who saw Unix, and saw that it was
good.  After typing cp on his DOS machine at home, he downloaded GNU's
unix tools ported to DOS and installed them.  He rm'd, cp'd, and mv'd
happily for many days, and upon finding elvis, he vi'd and was happy.  After
a long day at work (on a Unix box) he came home, started editing a file,
and couldn't figure out why he couldn't suspend vi (w/ ctrl-z) to do
a compile.
	-- Erik Troan, ewt@tipper.oit.unc.edu



Reply to: