RE: as.exe 2.14 -mips3 with -n32 option gives Invalid bfd target

[Ken Faiczak <kfaiczak at sandvine dot com>]

its invoked fine, the line is

as.exe -G 0 -EB -mips3 -O2 -g0 -n32 -v -o libgcc/mips3/n32/_muldi3.o

I can get rid of all the args and have "-mips3 -n32" and still get the
error.

I can do it on any source file (not related to gcc 3.3.1)
ie I invoke
as.exe -mips3 -n32 sysALib.s and get the same result.

whereas this works for 2.13.2.1 as.exe

All other abi seem to work
-32
-64
-o64

just n32 fails
also fails with -mabi=n32
but is ok with all others again

Looks like find_target() is failing for some reason
it returns 0.




-----Original Message-----
From: Ian Lance Taylor [mailto:ian@airs.com]
Sent: Friday, August 15, 2003 2:10 PM
To: Ken Faiczak
Cc: 'binutils@sources.redhat.com'
Subject: Re: as.exe 2.14 -mips3 with -n32 option gives Invalid bfd
target


Ken Faiczak <kfaiczak@sandvine.com> writes:

> 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...

The first step is to recreate the problem with the above command.
Then run it with the -v option; that will show you precisely how the
assembler is being invoked.  Look at the assembler options and try to
figure out why you are getting the error.  It may be an error in how
the assembler is being invoked, or it may be something else.  Hard to
say at this point.

Ian