Date: Thu, 15 May 2003 12:00:33 -0700 (PDT) From: Ruslan Ermilov <ru@freebsd.org> To: freebsd-bugs@FreeBSD.org Subject: Re: misc/52122: make release does not use proper binar Message-ID: <200305151900.h4FJ0X6D006422@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR misc/52122; it has been noted by GNATS.
From: Ruslan Ermilov <ru@freebsd.org>
To: "David O'Brien" <obrien@freebsd.org>
Cc: John Hay <jhay@icomtek.csir.co.za>, bug-followup@freebsd.org
Subject: Re: misc/52122: make release does not use proper binar
Date: Thu, 15 May 2003 21:56:24 +0300
On Thu, May 15, 2003 at 11:30:01AM -0700, David O'Brien wrote:
> 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.
>
Normal world, David, nothing magical.
Option 1:
cd /usr/src && \
make buildworld (if you're sure the installed kernel can run it)
Option 2:
cd /usr/src && make world kernel (in the order documented in
UPDATING)
Then:
cd /usr/src/release
make release ...
Like I said, if you hit a problem before May 5, it's totally
different from the "fresh world bits" issue. Rather, it's
just a WIP of twiddling with bsdlabel/disklabel, and not
committing the supporting patches to release/Makefile and
friends (some of them are still necessary). bsdlabel(8) is
only linked to disklabel(8) after
$FreeBSD: src/sbin/bsdlabel/Makefile,v 1.15 2003/05/05 21:28:08 phk Exp $
commit. My patch that I sent to phk@ on May 3 dealt with
this, by using bsdlabel(8) if it exists. This is now
less of an issue, except for bsdlabel not ending up on
the fixit floppy and a non-working sparc64/mkisoimages.sh.
Cheers,
--
Ruslan Ermilov Sysadmin and DBA,
ru@sunbay.com Sunbay Software AG,
ru@FreeBSD.org FreeBSD committer,
+380.652.512.251 Simferopol, Ukraine
http://www.FreeBSD.org The Power To Serve
http://www.oracle.com Enabling The Information Age
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200305151900.h4FJ0X6D006422>