Re: problem compiling newlib

[Dave Murphy <wintermute2k4 at ntlworld dot com>]

Oliver Kania wrote:
> Hello Dave!!
>
> Thanks.
>
> I tried using the bash files you provide.
> Binutils compile fine.
> With gcc I run into problems ::
>
> =============================================
> ./xgcc -B./ -B/usr/local/arm-elf/bin/ -isystem /usr/local/arm-elf/include 
> -isystem /usr/local/arm-elf/sys-include -L/root/arm-elf/arm-elf/gcc/gcc/../ld 
> -O2  -DIN_GCC -DCROSS_COMPILE   -W -Wall -Wwrite-strings -Wstrict-prototypes 
> -Wmissing-prototypes -Wold-style-definition  -isystem ./include  
> -Dinhibit_libc -fno-inline -g  -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED 
> -Dinhibit_libc -I. -I. -I../../../gcc-3.4.5/gcc -I../../../gcc-3.4.5/gcc/. 
> -I../../../gcc-3.4.5/gcc/../include  -DL_udivsi3 -xassembler-with-cpp 
> -c ../../../gcc-3.4.5/gcc/config/arm/lib1funcs.asm -o libgcc/./_udivsi3.o
> as: unrecognized option `-mcpu=arm7tdmi'
> make[1]: *** [libgcc/./_udivsi3.o] Error 1
> make[1]: Leaving directory `/root/arm-elf/arm-elf/gcc/gcc'
> make: *** [stmp-multilib] Error 2
> ==================================================
> A make -k results in multiple unrecognized mcpu-arm7tdmi
> This is strange because it is listed as an option in the info.
>   
This looks like you haven't added the arm-elf binutils tools to the path 
before configuring and building gcc so it's using the native assembler 
instead of the arm-elf assembler.

Dave