gcc 3.3.3 (and 3.4.2?) build failure (M68k)

Peter Barada peter@the-baradas.com
Mon Oct 25 12:52:00 GMT 2004

>I actually mentioned this earlier, but it sort got buried in a thread 
>starting off with something else:
>My attempts to build gcc 3.3.3 form m68k-coff fail as follows:
>make[2]: Entering directory 
>[ ... ]
>-B/usr/m68k-coff/bin/ -B/usr/m68k-coff/lib/ -isystem 
>/usr/m68k-coff/include -O2  -DIN_GCC -DCROSS_COMPILE   -W -Wall 
>-Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem 
>./include   -g  -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc -I. 
>-I. -I../../gcc-3.3.3/gcc -I../../gcc-3.3.3/gcc/. 
>-I../../gcc-3.3.3/gcc/config -I../../gcc-3.3.3/gcc/../include -DL_mulsi3 
>-xassembler-with-cpp -c ../../gcc-3.3.3/gcc/config/m68k/lb1sf68.asm -o 
>as: unrecognized option `-mc68020'
>make[2]: *** [libgcc/./_mulsi3.o] Error 1
>make[2]: Leaving directory 
>make[1]: *** [stmp-multilib] Error 2
>make[1]: Leaving directory 
>make: *** [all-gcc] Error 2
>I think I get the same problem with 3.4.2, too, but I'll check again. In 
>any case, I suspect the problem is that xgcc calls the native as, not 
>the m68k-coff-as, but I don't understand why.
>Has anyone else seen this? Any way to fix it?

Are you sure you have the cross-assembler in your PATH when you
configure/build the compiler?  If not then the compiler defaults to
the system assembler which is probably *not* an m68k assembler...

Peter Barada

Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com

More information about the crossgcc mailing list