NightStrike wrote:
Are you suggesting that 'fixincludes' should be phased out, and not
used at all on a cross-build?
No, I only would suggest something being done with the 'sys-include'
"feature" !
Trying to 'fix' something like the newlib headers in cases where one
uses the most uptodate newlib headers of course sounds weird so
using '--with-newlib' in GCC configure could generally disable the
header-fixing!
If one then thinks a typical "update" case where the current target C
library (newlib) is (only) in '$prefix/$target/include' and
'$prefix/$target/lib',
the 'sys-include' "feature" causes the target headers in 'include' not
being seen
by 'fixincludes' etc. In a native GCC build there is nothing like this
"feature", no need to put the '/usr/include' stuff to be seen also in the
'/usr/sys-include' during the GCC build for instance!
So at least those "maybe-needing-some-fixing" target headers should
be searched from the 'include', not from 'sys-include' during the GCC
build, just as the "GCC Internals" manual says!
