I suspect you're doing a build with possibly different version of gcc 
having compiled different object files. Or maybe it's just a question of 
a confused toolchain.
It looks like you're building the kernel by "hand" (without using build.sh).

Maybe rebuild the toolchain first, and then rebuilt the kernel, with a 
make clean in between...?

	Johnny

lucc@alge.anart.no skrev:
> Kernel compile on VAXstation 4k60:
> 
> #      link  MAINFRAME/netbsd
> ld -N -Ttext 80000000 -e start -S -o netbsd ${SYSTEM_OBJ} ${EXTRA_OBJ} vers.o
> sha2.o(.text+0x16): In function `SHA256_Init':
> : undefined reference to `memcpy'
> sha2.o(.text+0x26): In function `SHA256_Init':
> : undefined reference to `memset'
> sha2.o(.text+0x2ec): In function `SHA256_Update':
> : undefined reference to `memcpy'
> <snip all references to SHA{?}>
> 
> What the... ? Isen't this in the C library (man memset)?
> AFAIK this should not happen... and never has before on
> any other NetBSD compile I have done. Either something is
> wrong with my installation, or I have missed something.
> 
> /Luke
> 
> 

-- 
Johnny Billquist                  || "I'm on a bus
                                   ||  on a psychedelic trip
email: bqt@softjar.se             ||  Reading murder books
pdp is alive!                     ||  tryin' to stay hip" - B. Idol