This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: cross-compiler build failure, egcs-19990502
- To: Philip Blundell <pb at nexus dot co dot uk>
- Subject: Re: cross-compiler build failure, egcs-19990502
- From: Jeffrey A Law <law at upchuck dot cygnus dot com>
- Date: Wed, 19 May 1999 03:58:55 -0600
- cc: moshier at mediaone dot net, egcs-patches at egcs dot cygnus dot com, Alexandre Oliva <oliva at dcc dot unicamp dot br>
- Reply-To: law at cygnus dot com
In message <E10k2H2-0007Vz-00@fountain.nexus.co.uk>you write:
> the compiler would implicitly look for headers in /usr/arm-aout/include
> during building libgcc. This doesn't seem to happen any longer and I assumed this
> is what Moshier was talking about.
It's certainly not a change I was aware of. The only possibility that
comes to mind which could cause this kind of problem would be the relative
pathname changes.
But I'll repeat, the best way to provide headers for a cross compiler has always
been the --with-headers=<dir> option. While it is true the FSF compilers
never supported it, the FSF compilers were always incredibly lame in their
support for building cross compilers.
jeff