Greg Earle wrote:
> > It seems it doesn't do quite what you want, well, I agree with you that it
> > would be nice to have what you want.  But I'm not prepared to call DESTDIR
> > useless because of that.
> 
> I didn't say it was useless, but it's currently an agonizingly-close-to-100%
> (call it 98%) solution.  If <curses.h> properly got installed in the
> beginning stages, and there were a way to build the -current gcc2 from the
> existing 1.1 gcc 2.4.5 without it gagging on libgcc2.c, it would be at
> least 99 44/100ths %.  Then one could build into $DESTDIR, see that everything
> built correctly, and then either try some chroot'ed tests (as Phil Knaack
> mentioned) or risk it all and boot from floppy, mount the disk(s) and tar up
> $DESTDIR on top of the existing system.  If I have install a small part of
> the -current system - especially something as vital as the *compiler* - to
> get everything to go, then I see little point in trying to use DESTDIR.  If
> I have to blow away something important, might as well blow it all away, eh?

Hmmm...

Can you install the new gcc into $DESTDIR/bin, and then put that at the top of your
path for the next stage of compilation?

Similarly, do a make install in src/include into $DESTDIR/include, and then put
this include dir at the front of the options in a -I option?

Jules