misc/52122: make release does not use proper binar

David O'Brien obrien at freebsd.org
Thu May 15 11:31:55 PDT 2003

On Thu, May 15, 2003 at 08:13:50PM +0200, John Hay 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.
> Maybe the issue is more of documentation? I know hindsight makes it easy,
> but an installworld inside the chroot area or "world DESTDIR=/chrootarea"
> should have been enough to get the binaries updated.

It is, and was.  The problem is restarting with /mk used to do this for
you.  It stopped and the only documentation was hidding in the commit

-- David  (obrien at FreeBSD.org)

More information about the freebsd-bugs mailing list