From owner-freebsd-bugs@FreeBSD.ORG Thu May 15 11:40:10 2003 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A5F5637B404 for ; Thu, 15 May 2003 11:40:10 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id B1AA743FA3 for ; Thu, 15 May 2003 11:40:09 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h4FIe9Up005245 for ; Thu, 15 May 2003 11:40:09 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h4FIe9PC005244; Thu, 15 May 2003 11:40:09 -0700 (PDT) Date: Thu, 15 May 2003 11:40:09 -0700 (PDT) Message-Id: <200305151840.h4FIe9PC005244@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: "David O'Brien" Subject: Re: misc/52122: make release does not use proper binar X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: David O'Brien List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2003 18:40:11 -0000 The following reply was made to PR misc/52122; it has been noted by GNATS. From: "David O'Brien" To: Ruslan Ermilov Cc: John Hay , bug-followup@freebsd.org Subject: Re: misc/52122: make release does not use proper binar Date: Thu, 15 May 2003 11:30:01 -0700 On Thu, May 15, 2003 at 08:55:52PM +0300, Ruslan Ermilov wrote: > On Thu, May 15, 2003 at 09:58:44AM -0700, David O'Brien wrote: > > On Thu, May 15, 2003 at 06:31:42PM +0200, John Hay wrote: > > > One reason why it isn't that useful inside the chroot area, is that > > > if your running kernel and the newly built bits gets too much out of > > > sync you will need to update the machine in any case, so you will > > > end up with "new" binaries and a kernel on the machine and so it > > > is a "waste" to recompile world inside the chroot area. > > > > In this case the release died near the end (release.9 target). It was > > easy to update the running kernel and reboot. Now we wanted to restart > > the release w/o starting from scratch. This release build included ports > > README's and Docs, and thus takes a very long time to build. To not have > > to start from scratch, I did "chroot ${CHROOT} /bin/sh" and then ran "rm > > /tmp/.world_done ; /mk" which should have restarted the release build and > > done the mimimum work to finish the release. It didn't because of the > > cross-release commit that removed the installworld w/in the ${CHROOT}. > > This bit not only me, but another person also building an Alpha snapshot. > > > Now you know what to do -- you have to buildworld at the minimum I did build world. But you're being vauge -- which world??? Give a list of specific steps.