Daniel Jacobowitz wrote: > On Sun, Dec 04, 2005 at 05:51:32AM +0100, Thiemo Seufer wrote: > > Stuart Anderson wrote: > > > On Sun, 4 Dec 2005, Thiemo Seufer wrote: > > > > > > >>ar and ld get confused if they are not set. For some reason, it can't > > > >>decide which binary format to use. It may be a binutils bug, but I was > > > >>trying to not have to dig into that package and create a dependency on > > > >>a specific patch level of yet another package. > > > > > > > >If that's true it is a binutils bug. Ar and ld (are supposed to) default > > > >to use the format of the first input object as output format. But I > > > >wonder why "GNUTARGET = elf64-trad*mips" works for n32 then, it would > > > >need elf32-ntrad*mips in that case. > > > > > > Sorry, it was ar/ranlib (probably not ld) that had the problem. Here is > > > the failure without the GNUTARGET workaround. > > [snip] > > > ranlib 64/libgcc.a > > > ranlib: 64/libgcc.a: File format is ambiguous > > > ranlib: Matching formats: ecoff-littlemips ecoff-bigmips > > > elf64-tradlittlemips > > > make[5]: *** [64/libgcc.a] Error 1 > > > > Hm, this looks like the mips*-linux ar fails to handle 64bit archives. > > IIRC the fix is to just turn off ecoff support. The way archive > formats are detected is a bit ad-hoc...
There still exist bootloaders which need ECOFF support in BFD. Thiemo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]