This is the mail archive of the crossgcc@sourceware.cygnus.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more infromation.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: libiberty can't find target header files


Troy Cauble wrote:

> 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.

 Yes, the new 'relative search path' in gcc-2.95.2 tries now to use :
${prefix}/lib/gcc-lib/${target}/${version}/../../../../${target}/include
which is quite a different thing and so causes a 'Catch-22' situation.

 If you have created the directory
'${prefix}/lib/gcc-lib/${target}/${version}',
there is no problems finding the headers.

> I didn't see anything in the 'configure' stuff that would
> trigger that.  What am I missing?

 Editing the main 'Makefile.in' and adding a '-B${prefix}/${target}/'
before the
'-B${prefix}/${target}/bin/' in the *CFLAGS* definitions would fix this
'Catch-22'
bug...

> /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

 After the suggested fix this would result into :

  /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/ \                  <-----
!!!!!!
  -B/opt/wind/host/linux/arm-wrs-vxworks/bin/ \
  -c -DHAVE_CONFIG_H -g -O2 -I. -I../../../libiberty/../include \
  ../../../libiberty/choose-temp.c

 I made this fix into my sources sometimes in last summer and have
suggested this
fix in this list at least once before...

 Ok, the other possible 'hacks' are :

 1. Create the directory '${prefix}/lib/gcc-lib/${target}/${version}'
before starting
    to build GCC

 2. Try to toy with the '--with-headers=....' (never tried)

Cheers, Kai



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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]