Date: Thu, 15 May 2003 18:31:42 +0200 From: John Hay <jhay@icomtek.csir.co.za> To: obrien@freebsd.org Cc: freebsd-bugs@freebsd.org Subject: Re: misc/52122: make release does not use proper binar Message-ID: <20030515163142.GA75538@zibbi.icomtek.csir.co.za> In-Reply-To: <200305151600.h4FG0Uwt088142@freefall.freebsd.org> References: <200305151600.h4FG0Uwt088142@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> > I'm adding this from John Baldwin <jhb@FreeBSD.org> > Message-ID: <XFMail.20030514102336.jhb@FreeBSD.org> as its useful: > > A better solution would be to do what I have said before but > you and others whined that you didn't want: We should _still_ > do a full make world in the chroot _like_ we used to and then > do a further make buildworld for the cross-build case. ru@ > didn't like that and tried to change everything to use > cross-built tools or some such garbage. Since ru@ is the one > who broke this in revision 1.672 we should at least ask him > for input on how to fix this. Ruslan, the problem is that we > need up to date tools in the release chroot. Why not just update the source and do a buildworld in the native environment? You can either do it before every release snapshot or like me, when it seems necesary. This way I save a few cycles. 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. Just my 2 bits. (I'm not on RE, but have two machines building a -stable and -current snap every night.) John -- John Hay -- John.Hay@icomtek.csir.co.za / jhay@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030515163142.GA75538>