Re: headers and libs

[Kai Ruottu <kai dot ruottu at luukku dot com>]

On Wed, 04 Jul 2001 08:57:29 -0400
Stuart Kenny <skenny@solidum.com> wrote:

> This may be a dumb question, but what exactly are you supposed to point
> --with-headers and --with-libs to?

 Don't use them all, just copy the target headers and libs under

   $prefix/$target/include
and
   $prefix/$target/lib

which are their final official places. The $prefix and $target are the
values given with '--prefix=$prefix' and '--target=$target' in configure.
The default for $prefix is '/usr/local' and this will be used if the
'--prefix=....' is not used.

 This is the common practice documented in the "Using and Porting the GNU
Compiler Collection (GCC)", "Installation / Cross-Compiler" and if it
doesn't work for some reason, please report it as a bug...

 Currently copying/symlinking the 'math.h' and 'limits.h' into the
'$prefix/$target/sys-include', the equivalent-to SYSTEM_INCLUDE_DIR
in a native compiler, may be done because there is a bug in GCC and
the '$prefix/$target/include', the equivalent-to STANDARD_INCLUDE_DIR
(/usr/include) in a native compiler, is not searched for the target
headers. The 'math.h' may need fixing and the 'limits.h' must be seen
to exist.

 The target headers and libs are needed for compiling 'libgcc.a' and
doing a sanity check in the libiberty-configure (scanning 'libc.a' or
'libc.so' for missing functions).

> I understand the importance of setting these, but which headers and
> libs are the supposed to be pointing to?

 As said, don't point to anything with them...

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