From owner-freebsd-stable@FreeBSD.ORG Thu Sep 9 16:25:37 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DAA561065693 for ; Thu, 9 Sep 2010 16:25:37 +0000 (UTC) (envelope-from O.Seibert@cs.ru.nl) Received: from kookpunt.science.ru.nl (kookpunt.science.ru.nl [131.174.30.61]) by mx1.freebsd.org (Postfix) with ESMTP id 6D0D98FC0C for ; Thu, 9 Sep 2010 16:25:37 +0000 (UTC) Received: from twoquid.cs.ru.nl (twoquid.cs.ru.nl [131.174.142.38]) by kookpunt.science.ru.nl (8.13.7/5.31) with ESMTP id o89GPXVG009965; Thu, 9 Sep 2010 18:25:33 +0200 (MEST) Received: by twoquid.cs.ru.nl (Postfix, from userid 4100) id A92512E04F; Thu, 9 Sep 2010 18:25:33 +0200 (CEST) Date: Thu, 9 Sep 2010 18:25:33 +0200 From: Olaf Seibert To: Jeremy Chadwick Message-ID: <20100909162533.GT4404@twoquid.cs.ru.nl> References: <20100909141702.GP4404@twoquid.cs.ru.nl> <20100909152400.GS4404@twoquid.cs.ru.nl> <20100909153529.GA79356@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100909153529.GA79356@icarus.home.lan> User-Agent: Mutt/1.5.19 (2009-01-05) X-Spam-Score: -1.799 () ALL_TRUSTED,BAYES_50 X-Scanned-By: MIMEDefang 2.63 on 131.174.30.61 Cc: freebsd-stable@freebsd.org, Olaf Seibert , Thomas Ronner Subject: Re: Can't build 8.1 GENERIC kernel X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Sep 2010 16:25:37 -0000 On Thu 09 Sep 2010 at 08:35:29 -0700, Jeremy Chadwick wrote: > Regardless, when it comes to building world and kernel, you should > follow the instructions in /usr/src/Makefile (there's 11 steps). Do not > skip steps, and do not avoid steps (such as doing installkernel then > skipping the boot-into-single-user step before doing installworld; this > may work the majority of the time, but I've seen cases where /libexec > binaries don't get updated without going into single-user, and the > result is a system that breaks immediately). Fortunately, I was not upgrading anything, just reducing my kernel size a bit (well, almost by half) by eliminating support for hardware that isn't applicable. Sources and installed kernel and userland were the result of ``freebsd-update'' so they should all be up to date and in sync. I'm now trying a cross-build run, I'm curious how it compares with NetBSD. (NetBSD always builds (cross-) tools when building the world. In particular when building a major upgrade this is convenient, since then you can always be sure to be building with up-to-date tools) -Olaf. --