as 2.14 -mips3 with -n32 option gives Invalid bfd target

[Ken Faiczak]

I'm trying to upgrade our tool chain to
gcc 3.3.1 and binutils 2.14

While building the gcc libraries as part of the compiler build
I build for a bunch of multilib options
mips3/mips64 o64/n32

It builds all the o64 items fine but all the n32 ones give
FATAL: can't create libgcc/mips3/n32/_muldi3.o: Invalid bfd target

/m/ken3/Compiler/mips/gcc/xgcc -B/m/ken3/Compiler/mips/gcc/
-I/m/ken3/Tornado/target/h -DCPU=R4000 -O2  -DIN_GCC -DCROSS_COMPILE   -W
-Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem
./include -I/m/ken3/Tornado/target/h -DCPU=R4000  -G 0 -g
-DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc -I.
-I. -I../../gcc/gcc -I../../gcc/gcc/. -I../../gcc/gcc/config
-I../../gcc/gcc/../include  -mips3 -mabi=n32 -DL_muldi3 -c
../../gcc/gcc/libgcc2.c -o libgcc/mips3/n32/_muldi3.o
FATAL: can't create libgcc/mips3/n32/_muldi3.o: Invalid bfd target

target is mips-wrs-vxworks
host if cygwin/win2k

any ideas on what is wrong here??
or what other debugging tricks to look at...


If I replace as (2.14) with as 2.13.2.1 then it compiles fine...

-----------------------------------

This all worked fine with gcc 3.2.3 and binutils 2.13.2.1
despite some early issues with relocations missing
the n32 stuff worked fine for us in 2.13.2.1

Thanks for any help...
Ken