Re: libiberty can't find target header files

[Troy Cauble <troy at lucent dot com>]

I've been tempted to try --with-headers also, but I was going to
set it to /path/to/vxworks/headers .  Since I'm compiling for
vxWorks, I don't think I'll need to build newlib or libc.

If you don't have any other header file candidates (you didn't 
mention a target OS), I suppose you might have done the right 
thing.  The FAQ is unclear here.  It clearly says build GCC 
before newlib.  But then again it says unpack everything first.

Can anyone clarify?

-troy


Peter Evans wrote:
> 
> My build for Hitachi H8 couldn't find those files either.
> 
> I found some clues in the mail archives and then added
> 
> --with-headers=/path/to/newlib-1.8.2/newlib/libc/include
> 
> and finally got a successful build.
> 
> I would appreciate any comments on whether this is the right thing to do or
> not as I've never used the gnu tools before and only managed to do a
> successful build of gcc for H8 yesterday.
> 
> If anyone out there is using gcc/gdb with a Hitachi H8/3048 or 3067
> evaluation board and has got as far as running gcc generated code on it
> please get in touch.
> 
> Peter
> 
>  -----Original Message-----
> From:   Troy Cauble [mailto:troy@lucent.com]
> Sent:   15 March 2000 23:52
> To:     crossgcc@sourceware.cygnus.com
> Subject:        libiberty can't find target header files
> 
> Hi all,
> 
> My arm-wrs-vxworks gcc build is failing to find target
> header files while compiling the cross version of libiberty.
> 
> The 'make' is not trying to use ${prefix}/${target}/include
> like it did for libgcc1 and libgcc2.
> 
> I didn't see anything in the 'configure' stuff that would
> trigger that.  What am I missing?
> 
> If it matters, I had to make some typical configuration mods
> to binutils-2.9.1 for arm-wrs-vxworks, but gcc-2.95.2 didn't
> seem to need any...
> 
> Thanks,
> -troy
> 
> /opt/vxtools/gcc-2.95.2/arm-wrs-vxworks/gcc/xgcc
> -B/opt/vxtools/gcc-2.95.2/arm-w
> rs-vxworks/gcc/ -B/opt/wind/host/linux/arm-wrs-vxworks/bin/ -c
> -DHAVE_CONFIG_H -
> g -O2 -I. -I../../../libiberty/../include  ../../../libiberty/argv.c
> test x"no" != xyes || \
>   /opt/vxtools/gcc-2.95.2/arm-wrs-vxworks/gcc/xgcc
> -B/opt/vxtools/gcc-2.95.2/arm
> -wrs-vxworks/gcc/ -B/opt/wind/host/linux/arm-wrs-vxworks/bin/ -c
> -DHAVE_CONFIG_H
>  -g -O2 -I. -I../../../libiberty/../include
> ../../../libiberty/choose-temp.c -
> o pic/choose-temp.o
> /opt/vxtools/gcc-2.95.2/arm-wrs-vxworks/gcc/xgcc
> -B/opt/vxtools/gcc-2.95.2/arm-w
> rs-vxworks/gcc/ -B/opt/wind/host/linux/arm-wrs-vxworks/bin/ -c
> -DHAVE_CONFIG_H -
> g -O2 -I. -I../../../libiberty/../include  ../../../libiberty/choose-temp.c
> ../../../libiberty/choose-temp.c:29: stdio.h: No such file or directory
> ../../../libiberty/choose-temp.c:30: sys/types.h: No such file or directory
> ../../../libiberty/choose-temp.c:32: unistd.h: No such file or directory
> ../../../libiberty/choose-temp.c:35: stdlib.h: No such file or directory
> ../../../libiberty/choose-temp.c:38: sys/file.h: No such file or directory
> make[1]: *** [choose-temp.o] Error 1
> make[1]: Leaving directory
> `/opt/vxtools/gcc-2.95.2/arm-wrs-vxworks/arm-wrs-vxwo
> rks/libiberty'
> make: *** [all-target-libiberty] Error 2
> 
> ------
> Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
> Want to unsubscribe? Send a note to
> crossgcc-unsubscribe@sourceware.cygnus.com

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