From owner-freebsd-questions@FreeBSD.ORG Thu Feb 21 20:24:55 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 10F2C16A402 for ; Thu, 21 Feb 2008 20:24:55 +0000 (UTC) (envelope-from jmc-freebsd@milibyte.co.uk) Received: from pih-relay04.plus.net (pih-relay04.plus.net [212.159.14.131]) by mx1.freebsd.org (Postfix) with ESMTP id C196E13C4D1 for ; Thu, 21 Feb 2008 20:24:54 +0000 (UTC) (envelope-from jmc-freebsd@milibyte.co.uk) Received: from [84.92.153.232] (helo=kestrel.milibyte.co.uk) by pih-relay04.plus.net with esmtp (Exim) id 1JSHyR-0002D9-CK; Thu, 21 Feb 2008 20:24:55 +0000 Received: by kestrel.milibyte.co.uk with local (Exim 4.69) (envelope-from ) id 1JSHyN-0009mu-QY; Thu, 21 Feb 2008 20:24:52 +0000 From: Mike Clarke To: freebsd-questions@freebsd.org Date: Thu, 21 Feb 2008 20:24:50 +0000 User-Agent: KMail/1.9.7 References: <200802151103.22663.jmc-freebsd@milibyte.co.uk> In-Reply-To: <200802151103.22663.jmc-freebsd@milibyte.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200802212024.51723.jmc-freebsd@milibyte.co.uk> X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: jmc-freebsd@milibyte.co.uk X-SA-Exim-Scanned: No (on kestrel.milibyte.co.uk); SAEximRunCond expanded to false X-Plusnet-Relay: 945942cc57abc41fabc3499d8a0099fb Subject: Re: Buildworld failure with 6.3 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Feb 2008 20:24:55 -0000 On Friday 15 February 2008, Mike Clarke wrote: I recently posted about my problem with buildworld failing in /usr/src/sys/boot/i386/loader/ with the message: /usr/obj/usr/src/sys/boot/i386/loader/../libi386/libi386.a(biosdisk.o) (.text+0x9ff): In function `bd_opendisk': undefined reference to `uuid_is_nil' I've since tried to update the src directory by re-running csup but still got the same errors but did get things working again by recovering /usr/src from an earlier backup and running csup to bring it up to date. I assume that something in the source tree had become corrupted but somehow wasn't being replaced by csup. This has made me start wondering about the best way to diagnose the problem if it should arise again. Is there any utility which can easily check the integrity of the src directory to identify the offending file(s)? -- Mike Clarke