How to get gcc-2.95.1 to use pre-installed headers without copying?

Graham Stoney greyham@research.canon.com.au
Tue Aug 24 19:04:00 GMT 1999


Hi There,

I've managed to install a powerpc-linux cross compiler tool chain using
gcc-2.95, binutils-990809 snapshot, and glibc-2.1.2pre2 on our
i686-pc-linux-gnu Red Hat 6.0 system. In the mean time, gcc-2.95.1 has been
released, so I want to upgrade. My installation looks like this:

Target stuff:
    /usr/local/powerpc-linux

Host stuff:
    /usr/local/i686-pc-linux-gnu

I've made these symlinks, to avoid needing 2 copies of all the libraries:
    /usr/local/i686-pc-linux-gnu/powerpc-linux/include -> /usr/local/powerpc-linux/include
    /usr/local/i686-pc-linux-gnu/powerpc-linux/lib -> /usr/local/powerpc-linux/lib

My question: how do I get gcc-2.95.1 to use the glibc headers I already have
installed in /usr/local/i686-pc-linux-gnu/powerpc-linux/include when building
libiberty?

If I specify this directory using --with-headers, configure copies the
previously installed glibc headers (while trying to fixinclude them) into
/usr/local/i686-pc-linux-gnu/powerpc-linux/sys-include; but they don't need
fixincluding, and I just want to use them as they are. If I don't specify
--with-headers, the cross compiled build of libiberty fails because it can't
find basic stuff like stdio.h. Is there any easy way to tell the gcc configure/
build how to find these headers without ending up with a duplicate copy?

Thanks,
Graham

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



More information about the crossgcc mailing list