This is the mail archive of the
mailing list for the GCC project.
Re: what should bootstrap *really* do?
- To: Hans-Peter Nilsson <hans-peter dot nilsson at axis dot com>
- Subject: Re: what should bootstrap *really* do?
- From: ebiederm at xmission dot com (Eric W. Biederman)
- Date: 16 Nov 2000 21:07:01 -0700
- Cc: dj at redhat dot com, kenner at vlsi1 dot ultra dot nyu dot edu, gcc at gcc dot gnu dot org
- References: <200011141609.RAA20193@ignucius.axis.se>
Hans-Peter Nilsson <firstname.lastname@example.org> writes:
> > Date: Tue, 14 Nov 2000 09:58:59 -0500
> > From: DJ Delorie <email@example.com>
> > I, personally, want a restartable bootstrap because I, personally,
> > work on systems that can't reliably complete a full bootstrap. Other
> > people have other needs. I'm trying to change the system so that more
> > than one option is available.
> Then why not have a *new* target with the *new* (restart-in-middle)
> functionality instead of changing the "bootstrap" target? The name
> "bootstrap-restart" comes to mind. :-)
> BTW, all stages should be built in the same directory (like
> now), or you risk debugging info being different and failing to
So why not do:
stage1/foo.o : foo.c
cc -c foo.c -o foo.o && mv foo.o stage1/foo.o
stage2/foo.o : foo.c stage1/gcc
stage1/gcc -c foo.c -o foo.o && mv foo.o stage2/foo.o
stage3/foo.o : foo.c stage2/gcc
stage2/gcc -c foo.c -o foo.o && mv foo.o stage3/foo.o
Then you can restart when ever you want.
Nice simple, builds in the normal directory, stores the files in
the stage directories.
Then everything is simple and follows normal make rules, and doesn't
need any special files.