This is the mail archive of the
mailing list for the GCC project.
Re: Bootstrap fixincludes
- From: Geoffrey Keating <geoffk at geoffk dot org>
- To: Daniel Jacobowitz <drow at false dot org>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: 01 Dec 2004 15:51:57 -0800
- Subject: Re: Bootstrap fixincludes
- References: <20041128191831.GA21935@localhost.localdomain> <20041128195858.GA2960@nevyn.them.org>
Daniel Jacobowitz <email@example.com> 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).