Fixincludes permanence & questions on cross compilers

[Jonathan Wakely]

On 23 May 2012 17:52, rbmj wrote:
> Hi all,
>
> Two questions:
>
> 1.  Are fixincludes hacks only active during build-time (e.g. they do not
> replace the actual file) or are they permanent?  If they are only
> temporary/local to gcc, but they need to be permanent, is there a way to
> specify this?

They are permanent, but they don't replace the file. GCC puts the
fixed headers in a directory which it searches before the system
directories, so it finds the fixed ones before the original ones.

> 2.  On cross compilers, fixincludes does not appear (to my uneducated eye)
> to be applied to my headers (then again, I may have written the hacks wrong)
> located in sys-include.  Does fixincludes not affect headers in sys-include
> or am I not looking hard enough?

If you're expecting the original headers to be replaced then you're
looking in the wrong place.

Search under the GCC installation tree, you should find the fixed
version of the header.