From owner-freebsd-current@FreeBSD.ORG Mon Jun 28 05:54:55 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DC9BF106566B for ; Mon, 28 Jun 2010 05:54:55 +0000 (UTC) (envelope-from ru@freebsd.org) Received: from mail.vega.ru (mail.vega.ru [90.156.167.5]) by mx1.freebsd.org (Postfix) with ESMTP id 985CC8FC19 for ; Mon, 28 Jun 2010 05:54:55 +0000 (UTC) Received: from [10.100.124.99] (helo=edoofus.dev.vega.ru) by mail.vega.ru with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.71 (FreeBSD)) (envelope-from ) id 1OT7Iz-000Og0-MT; Mon, 28 Jun 2010 09:54:53 +0400 Date: Mon, 28 Jun 2010 09:54:12 +0400 From: Ruslan Ermilov To: Garrett Cooper Message-ID: <20100628055411.GC8478@edoofus.dev.vega.ru> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: FreeBSD Current Subject: Re: Coming back to the btxld: No such file or directory installworld error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jun 2010 05:54:55 -0000 On Sun, Jun 27, 2010 at 01:14:59PM -0700, Garrett Cooper wrote: > Hi Ruslan, > I've run into this particular error twice now in the past couple > of weeks when building with -j24 on a memory disk and I was wondering > if there was an missing dependency / race somewhere or something > (perhaps make obj?): > > ===> sys/boot/i386/boot2 (install) > # ... > btxld -v -E 0x2000 -f bin -b > /usr/obj/scratch/freebsd/current/sys/boot/i386/boot2/../btx/btx/btx -l > boot2.ldr -o boot2.ld -P 1 boot2.bin > btxld: No such file or directory > *** Error code 1 The "install" target isn't supposed to build stuff, only install it. When you see it trying to build something, this can be indicative of: - build wasn't run (e.g., after an update); - a computer's date/time is set to the past (causing wrong date/time to be set on output files => causing them to be considered out-of- date by make(1)); check with date(1). - source files have modification times pointing to the future which fools make(1) into thinking that it should rebuild some target; check with "find /usr/src -mtime -0". HTH, -- Ruslan Ermilov ru@FreeBSD.org FreeBSD committer