From owner-freebsd-current@FreeBSD.ORG Mon Nov 28 21:29:53 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E48316A424 for ; Mon, 28 Nov 2005 21:29:53 +0000 (GMT) (envelope-from kstewart@owt.com) Received: from smtp.owt.com (smtp.owt.com [204.118.6.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id CDB7243D4C for ; Mon, 28 Nov 2005 21:29:52 +0000 (GMT) (envelope-from kstewart@owt.com) Received: from topaz-out (owt-207-41-94-233.owt.com [207.41.94.233]) by smtp.owt.com (8.12.8/8.12.8) with ESMTP id jASLSV0U004402; Mon, 28 Nov 2005 13:28:32 -0800 From: Kent Stewart To: freebsd-current@freebsd.org Date: Mon, 28 Nov 2005 13:28:48 -0800 User-Agent: KMail/1.8.3 References: <438AB4FD.60703@forrie.com> <39563421@serv3.int.kfs.ru> In-Reply-To: <39563421@serv3.int.kfs.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511281328.48486.kstewart@owt.com> Cc: Boris Samorodov , Forrest Aldrich Subject: Re: touch: not found 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 Nov 2005 21:29:53 -0000 On Monday 28 November 2005 05:44 am, Boris Samorodov wrote: > On Mon, 28 Nov 2005 02:42:53 -0500 Forrest Aldrich wrote: > > Odd error with building FreeBSD-6 (cvsup'd today): > > > > ===> include (install) > > creating osreldate.h from newvers.sh > > touch: not found > > *** Error code 127 > > > > Though clearly "touch" is in PATH and is found otherwise. > > > > Bug or typo somewhere? > > How did you upgrade the system? > His system clock is mostly likely off and he created files that are older than he got with cvsup. Then, make thinks he needs to generate them again before it does the install. All he has to do is set the system clock to the right time and redo the update. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html