Re: bootstrap w/o compiler chestnut.

[Eric Christopher <echristo at redhat dot com>]

> Is there a way to get the fixincludes part of the build proces to
> behave as if ALL the includes need fixing, so that a full set is
> created for the "destination" compiler?  (I think this would have
> the advantage that the Free compiler could be built with a non-free
> compiler, and the result would be distributable. [This may be a
> spurious point, I find these issues tend to be more subtle than I
> expect!])
> 

Nope. Fixincludes only fixes the include files you have.

> 
> Another way to get the compiler built correctly for the 'far'
> machine might be to start on machine A, build a cross compiler on A
> to produce code for machine B, say gccA->B, then somehow build
> gccB->B with this cross-compiler.  There is documentation on how to
> build a cross compiler, but not on how to create a new native
> compiler with this cross-compiler, at least that I can find with the
> usual searching techniques.  Is this process described anywhere,
> please?
> 

Possibly, but you'll still need the development headers and libraries of
the target machine. You can't get away from that.

-eric

-- 
o/~ got caught stealing fire from the sky o/~