Folks...

Bootstrapping a toolchain with MACHINE=arm32 MACHINE_ARCH=arm results
in the following when building a kernel with the resulding toolchain:

making sure the compat library is up to date...
/usr/local/netbsd-tools/current/bin/arm--netbsdelf-gcc -O2 -march=armv4 -mtune=strongarm -Werror -Wall -Wcomment -Wpointer-arith -Wno-uninitialized -Wno-main -I../../. -I../../../../../../arch -I../../../../../.. -nostdinc -DHZ="0x40" -DNMBCLUSTERS="0x400" -DOFW -DSHARK -DNSIO -DDIAGNOSTIC -DMAXUSERS=32 -D_KERNEL -D_KERNEL_OPT -Darm32   -nostdinc -idirafter /usr/include -c ../../../../../../compat/common/compat_exec.c
/usr/local/netbsd-tools/current/bin/arm--netbsdelf-ld: cannot represent machine `arm:arm32'
*** Error code 1

Stop.
nbmake: stopped in /u1/netbsd/src/sys/arch/arm32/compile/SHARK/lib/compat
*** Error code 1

Stop.
nbmake: stopped in /u1/netbsd/src/sys/arch/arm32/compile/SHARK
dr-evil:thorpej 159$ 

I guess the environment is wrong when the ldscripts are created.

Can someone familiar with what's going on there take a look at this?  I
can work around it for now, but this is slightly annoying.

-- 
        -- Jason R. Thorpe <thorpej@wasabisystems.com>