Re: cross-compiler build failure, egcs-19990502

[Jeffrey A Law <law at upchuck dot cygnus dot com>]

  In message <Pine.LNX.4.05.9905191426300.5480-100000@moshier.ne.mediaone.net>y
ou write:
  > > http://egcs.cygnus.com/install/configure.html
  > 
  > This does not mention that the compilation will fail if no
  > --with-headers option is given.
  > 
  > You have somehow made this option mandatory, where previously, 
  > in gcc, it did not even exist.  That is a significant behavior
  > change.    It ought to be listed in the release notes.
I think the configuration and installation guide is a reasonable place to
put this.  That is where people should be looking every time they try to
configure & install the compiler.  Those of us who do this on a regular
basis are the worst offenders to that rule since we think we always know
how things are supposed to work.

--


I also looked more deeply into the problem, and in fact it was the relative
pathname changes that are causing us not to find the stuff in the "install"
directory during the build phase.  Note:

./xgcc -v -B./ foo.c
Using builtin specs.
gcc version gcc-2.96 19990518 (experimental)
 ./cpp -lang-c -v -isystem ./include -D__GNUC__=2 -D__GNUC_MINOR__=96 -Darm -D__arm__ -D__arm -Acpu(arm) -Amachine(arm) -D__CHAR_UNSIGNED__ -D__ARM_ARCH_3__ -D__APCS_26__ foo.c /tmp/ccLedaaa.i
GNU CPP version gcc-2.96 19990518 (experimental) (ARM/generic)
#include "..." search starts here:
#include <...> search starts here:
 include
End of search list.
The following default directories have been omitted from the search path:
 /usr/lib/gcc-lib/arm-aout/gcc-2.96/../../../../include/g++-2
 /usr/lib/gcc-lib/arm-aout/gcc-2.96/include
 /usr/lib/gcc-lib/arm-aout/gcc-2.96/../../../../arm-aout/sys-include
 /usr/lib/gcc-lib/arm-aout/gcc-2.96/../../../../arm-aout/include
End of omitted list.
foo.c:1: stdio.h: No such file or directory


Note the relative pathnames to get to various include directories.  Since
the install dir does not exist yet we omit those directories from the 
search path.

With this information I think your patch may be the reasonable thing to do,
I'm going to take another look at it.

Note that I still recommend --with-headers and --with-libs as the best way
to find cross includes and libraries.  That's why they're in the configuration
guide.


jeff