This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: what should bootstrap *really* do?
> IMO, whatever works best for users, since that's the recommended
> installation procedure. Thinking of someone whose build machine
> crashes part-way through the build, runs out of disk space, needs to
> tweak a configuration parameter here or there, I think `make
> bootstrap' should proceed from the stage in which the previous build
> stopped, not from stage1.
Hmmm... This means that the "last" stage should always be built in
cwd, not in a stage directory, so that "make install" works. Good
tip!
> Needs of developers are certainly different.
That's why I'm asking ;-)
> I like the idea of cleanstrap,
Has anyone actually *tried* "make clean bootstrap" yet?
> and that of cleaning the next stage in case you rebuild anything in
> a certain stage, but I'd rather have give this a different target
> name, such as depstrap.
Part of my goals with this question is what should the *default* do.
> Another alternative is to have this stuff in some other directory,
> and have each stage `cd that/directory && $(MAKE) fixinc' or
> `libgcc1'.
Judicious use of symlinks can make all the stages see the same real
directories for those.