Subject: Re: Problems with alpha->vax kernel
To: Jarkko Teppo <jarkko.teppo@er-grp.com>
From: Jason R Thorpe <thorpej@wasabisystems.com>
List: current-users
Date: 10/24/2002 09:01:01
On Thu, Oct 24, 2002 at 06:35:27PM +0300, Jarkko Teppo wrote:
> I'm getting the following linker warnings compiling a fresh current
> kernel on a 1.6 Alpha (crosscompile alpha->vax):
>
> /src/tooldir_vax/bin/vax--netbsdelf-ld -N -Ttext 80000000 -e start -S -o
> netbsd ${SYSTEM_OBJ} vers.o
> /src/tooldir_vax/bin/vax--netbsdelf-ld: intvec.o: warning: GOT addend of 4
> to `softclock_intrcnt' does not match previous GOT addend of 0
> /src/tooldir_vax/bin/vax--netbsdelf-ld: intvec.o: warning: GOT addend of 4
> to `softnet_intrcnt' does not match previous GOT addend of 0
> /src/tooldir_vax/bin/vax--netbsdelf-ld: intvec.o: warning: GOT addend of 4
> to `softserial_intrcnt' does not match previous GOT addend of 0
> /src/tooldir_vax/bin/vax--netbsdelf-ld: intvec.o: warning: GOT addend of 4
> to `clock_intrcnt' does not match previous GOT addend of 0
You can ignore these linker warnings... They are harmless for static
links (like the kernel).
> The resulting kernel doesn't want to boot on a 4000/90, it hangs after
> detecting the root file system as ffs (correctly). No panic nor anything
> else, just plain hard hang.
This is probably some other problem, though. I am pretty sure that
we specifically did not do alpha->vax on the autobuilder for 1.6 because
of toolchain problems.
--
-- Jason R. Thorpe <thorpej@wasabisystems.com>