Re: Problem building a cross-gcc for arm target

[Igor Zafievsky <gosha at cannon dot rosinter dot ru>]

Hello!

On Tue, 16 Jan 2001, Igor Trevisan wrote:

> /gcc-2.95.2/libiberty/choose-temp.c../../../gcc-
> 2.95.2/libiberty/choose-temp.c:29: stdio.h: No such file or directory
> ../../../gcc-2.95.2/libiberty/choose-temp.c:30: sys/types.h: No such 
> file or directory
> ../../../gcc-2.95.2/libiberty/choose-temp.c:32: unistd.h: No such file 
> or directory
> ../../../gcc-2.95.2/libiberty/choose-temp.c:35: stdlib.h: No such file 
> or directory
> ../../../gcc-2.95.2/libiberty/choose-temp.c:38: sys/file.h: No such 
> file or directory
> make[1]: *** [choose-temp.o] Error 1
> make[1]: Leaving directory `/root/mytmp/tmp-gcc/arm-
> elf/libiberty'make: *** [all-target-libiberty] Error 2
> root ~/mytmp
> 
> I'm trying to build the cross-compiler in the /tools/bin
> directory and I added it to the PATH.
> I saw in the list of FAQ that someone else had a similar problem 
> and the suggested solution was to configure the cross gcc with the 
> option:
> 
> --with-headers=/root/mytmp/newlib-1.8.2/newlib/libc/include
> 
> But I tried it without any good news.
> Can anyone suggest something else to go on?
> Thanks in advance to every good guy that will save my work and 
> my patience!

  When you configure gcc, invoke 'configure' with --with-newlib option. Hope, this helps

Igor (too:)


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