Date: Thu, 28 Oct 1999 09:11:23 +1000 From: Peter Jeremy <jeremyp@gsmx07.alcatel.com.au> To: freebsd-current@FreeBSD.ORG Subject: Re: make buildworld problem... Message-ID: <99Oct28.090631est.40344@border.alcanet.com.au> In-Reply-To: <19991027143653.B21727@dragon.nuxi.com> References: <NCBBIAEGCKECIGCKDPPBAEMAFJAA.tps@ncc.nextra.sk> <19991027143653.B21727@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1999-Oct-28 07:36:53 +1000, David O'Brien wrote: >IF you are going to run -CURRENT, you need to read this list. And read /usr/src/UPDATING which also warns about this >(/me wonders how many MORE times we are going to have to say this because >of the signal changes...) A very large number I suspect. IMHO, the correct solution is to for the entire make world process to be re-worked. I believe the process should always be to boot a new kernel first (as bde(?) commented - it's much easier to recover from a broken kernel than a broken world), and then install a new world. Getting there from here is non-trivial - the major problem being that our build process does not adequately differentiate between compiling code that must run now and code that must run with the new kernel. Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5982 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?99Oct28.090631est.40344>