From owner-freebsd-current  Sat Sep 27 19:37:37 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id TAA00178
          for current-outgoing; Sat, 27 Sep 1997 19:37:37 -0700 (PDT)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA00173
          for <freebsd-current@FreeBSD.ORG>; Sat, 27 Sep 1997 19:37:34 -0700 (PDT)
Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id TAA27280; Sat, 27 Sep 1997 19:37:18 -0700 (PDT)
To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Make Release failures 
In-reply-to: Your message of "Sat, 27 Sep 1997 17:12:45 +0200."
             <19970927171245.WM37928@uriah.heep.sax.de> 
Date: Sat, 27 Sep 1997 19:37:18 -0700
Message-ID: <27276.875414238@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> Huh?  Never did it... :-)  Can't work for cross-release buildings
> anyway (i.e., 2.2 under -current, or vice versa).

Yes, but it makes *sure* that you have a fully populated /usr/obj
when the install pass is run.  Whether the installed binaries
actually work is another thing, but at least you're not going
to blow up in the release during the chrootdir population pass. :)

Remember Murphy's law.  Build the friggin' world if you're going to do
a release and that's one less area to worry about it falling over
in. ;)

					Jordan