From owner-freebsd-questions@FreeBSD.ORG Tue Nov 9 16:50:09 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B80116A4D0 for ; Tue, 9 Nov 2004 16:50:09 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9EEA043D5A for ; Tue, 9 Nov 2004 16:50:08 +0000 (GMT) (envelope-from elvstone@gmail.com) Received: by rproxy.gmail.com with SMTP id a36so69422rnf for ; Tue, 09 Nov 2004 08:50:06 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=NgBuL4JCDzU/pXM5Om/Et7/M53DOvAbZGGOX+OCEbhJaB/4+ezeeSI0KHNDwUKGmnRuE2BL/65dfX0vdD2KbVOqDrAnDtWMiKWZNQrp9JNM9KklEYzmO11oZiujfazA8E1GiPLNKQNC1FVmxVWKw12or9XWgbIAfeN8UyOQyYBI= Received: by 10.38.74.76 with SMTP id w76mr431086rna; Tue, 09 Nov 2004 08:50:05 -0800 (PST) Received: by 10.38.70.52 with HTTP; Tue, 9 Nov 2004 08:50:05 -0800 (PST) Message-ID: <751a4f8704110908502a14c349@mail.gmail.com> Date: Tue, 9 Nov 2004 17:50:05 +0100 From: Aron Stansvik To: freebsd-questions@freebsd.org In-Reply-To: <751a4f87041109062939061dac@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <751a4f87041109062939061dac@mail.gmail.com> Subject: Re: RELENG_5_3 buildworld fails (cannot find -lc) FIXED X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Aron Stansvik List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Nov 2004 16:50:09 -0000 Sorry, my mistake. Network wasn't available at boot, so ntpdate couldn't sync, so the clock was off, so the build system tried to build libmagic two times. I'm so stupid. This was exactly like when I was setting up some x509 certificates for isakmpd a while ago, with the clock set way into the future on the machine where I was issuing the certificates, I couldn't understand why the certs wouldn't work: Because their lifetime hadn't started yet! Lesson learned (twice!): Check your clock! Best regards, Aron Stansvik