This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: what should bootstrap *really* do?
- To: aoliva at redhat dot com (Alexandre Oliva)
- Subject: Re: what should bootstrap *really* do?
- From: Joern Rennecke <amylaar at redhat dot com>
- Date: Tue, 14 Nov 2000 11:49:22 +0000 (GMT)
- Cc: dj at redhat dot com (DJ Delorie), gcc at gcc dot gnu dot org
>
> On Nov 14, 2000, DJ Delorie <dj@redhat.com> wrote:
>
> > Hmmm... This means that the "last" stage should always be built in
> > cwd, not in a stage directory, so that "make install" works.
>
> The problem is how to define `last'. Currently, one can do `make
> all', `make bootstrap' and `make bootstrap4' all in the same tree. If
> we start building stages in subdirectories, we'd probably lose this
> ability, and I can see people complaining more loudly about this loss
> than about the need for deleting stage stamp files before bootstrap
> will start scratch.
I think we should just build the stages in their stage directories, but
whenever a new stage is started, make / change a symlink to point to
the new stage directory.
Or we could use a plain text file with the contents being the stage
directory to allow for systems that don't have symlinks.