Why is fixincludes not doing anything? (was: Re: Fixincludes permanence & questions on cross compilers)

[Ian Lance Taylor]

rbmj <rbmj@verizon.net> writes:

> Refine my question: anyone know why fixincludes does not appear to be
> doing *anything*?  I can't seem to find any fixed headers anywhere in
> GCC's build tree.  And the compile keeps failing...

In your specific case, I don't know.  But it is possible for a target to
disable fixincludes by setting STMP_FIXINC in a config/CPU/t-XXX file.
Or, since this is a cross-compiler, GCC may simply be confused about
where to find the header files that it is supposed to fix.  Normally
those header files will be found in the directory printed by gcc
-print-sysroot-headers-suffix.  What does that print for you?  Did you
configure GCC with the right --with-sysroot option?

Ian