Bootstrap fixincludes
Geoffrey Keating
geoffk@geoffk.org
Wed Dec 1 23:51:00 GMT 2004
Daniel Jacobowitz <drow@false.org> writes:
> On Sun, Nov 28, 2004 at 11:18:32AM -0800, Matt Kraai wrote:
> > Howdy,
> >
> > As reported in comment 4 of PR 18176, when configure is passed
> > --enable-bootstrap, the build fails because all-stage1-gcc depends on
> > maybe-all-stage1-fixincludes. The attached patch makes fixincludes a
> > bootstrap module, which creates the missing target.
> >
> > Tested on powerpc-unknown-linux-gnu until the build failed due to the
> > warnings reported in PR 18176. OK to commit?
>
> Why bootstrap fixincludes? It seems to me that it should be a build
> module, to use during the build, and a host module, so that we can
> install it on the host. Ideally we could build the build copy before
> GCC and the host copy after...
It is; but if host==build, then it should be bootstrapped (like every
other build module).
More information about the Gcc-patches
mailing list