From owner-freebsd-bugs  Tue Jan 14 21:41:28 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id VAA09066
          for bugs-outgoing; Tue, 14 Jan 1997 21:41:28 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA09044
          for <freebsd-bugs@freefall.freebsd.org>; Tue, 14 Jan 1997 21:41:20 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id QAA06876; Wed, 15 Jan 1997 16:38:07 +1100
Date: Wed, 15 Jan 1997 16:38:07 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199701150538.QAA06876@godzilla.zeta.org.au>
To: freebsd-bugs@freefall.freebsd.org, thompson@tgsoft.com
Subject: Re: bin/2493: make $DESTDIR work
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>    I think ${DESTDIR} is only guaranteed to what its name says: a
>    destination directory.  This will only work to _install_ an already
>    compiled tree (and this feature is heavily relied on during the
>    release build process).

That's all that FreeBSD currently attempts to support.  I'm not sure if
it was once an attempt at supporting cross-building.

>    I'm not sure what other people think, but i'm of the opinion that your
>    patches try to extend the idea of ${DESTDIR}.

They should use another macro name, e.g. TARGETDIR.

> I believe that whether or not ${DESTDIR} was 'guaranteed' to do what i
> want (allow you to do a make world without overwritting your running
> system), 90% of the Makefiles are coded so you can do just that. The
> changes that i submitted take you to between 95-99% of the way there and
> *should not* break anything. 

I was surprised that you only needed 30K of changes.  But does ${DESTDIR}
as a plain installation directory still work?  No files from ${DESTDIR}
should be used for building things.  This is already broken by use of
${LDDESTDIR}.  -nostdlib isn't used, so ${LDDESTDIR} just gives some
standard libraries and some target libraries.  It's hard to say which,
but attempting to use -nostdlib and watching what breaks is a start :-).

Things like `CFLAGS+=-I/sys' in ps should be fixed in another way, probably
by removing them and using `-nostdinc -I- -I${TARGETDIR}/usr/include' in
a central makefile and populating the target usr/include with correct
versions of <sys> and <machine>, etc.

Bruce