From owner-freebsd-sparc64@FreeBSD.ORG Wed Jul 14 13:36:32 2004 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B63B16A4CE for ; Wed, 14 Jul 2004 13:36:32 +0000 (GMT) Received: from rikwade.com (rikwade.com [212.13.208.233]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6B9D43D54 for ; Wed, 14 Jul 2004 13:36:29 +0000 (GMT) (envelope-from rik@rikwade.com) Received: from [10.144.153.43] (gate-isdn.admin.theplanet.net [195.92.70.130]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by rikwade.com (Postfix) with ESMTP id 2E8F018088; Wed, 14 Jul 2004 14:36:28 +0100 (BST) Message-ID: <40F536DA.4040106@rikwade.com> Date: Wed, 14 Jul 2004 14:36:26 +0100 From: Rik Wade User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.1) Gecko/20040707 MultiZilla/1.6.4.0b X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ken Smith References: <40F4DE72.5010500@rikwade.com> <20040714132130.GC7787@electra.cse.Buffalo.EDU> In-Reply-To: <20040714132130.GC7787@electra.cse.Buffalo.EDU> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: sparc64@freebsd.org Subject: Re: don't know how to make dummy.c X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jul 2004 13:36:32 -0000 Ken Smith wrote: > > The times I've seen something weird like this were due to the system's > clock being something totally unreasonable. Check to see what the > current time is on the system and if it's wrong manually set it to > something realistic and try the build again. > > If that's not it let us know. The clock was slightly out (in the future by a couple of minutes) so I reset it and tried again. Same error unfortunately. However, in the process, I noticed that the timestamp for all the files on my system appears to be "Jan 1 1970". If I touch a new file, it is created with the date "Jan 1 1970". If this is not a normal state of affairs (and I'm guessing that it isn't ;-) ) then it seems likely that I've made a mistake somewhere along the upgrade process. In this case, I will regress and start again with an old kernel. -----------------> bash-2.05b# date Wed Jul 14 14:34:12 BST 2004 bash-2.05b# pwd /usr/src/tools/build bash-2.05b# touch a.test bash-2.05b# ls -l total 14 -rw-r--r-- 1 root wheel 1567 Jan 1 1970 Makefile -rw-r--r-- 1 root wheel 0 Jan 1 1970 a.test -rw-r--r-- 1 root wheel 119 Jan 1 1970 dummy.c -rw-r--r-- 1 root wheel 1750 Jan 1 1970 endian.h -rw-r--r-- 1 root wheel 340 Jan 1 1970 langinfo.h drwxr-xr-x 2 root wheel 512 Jan 1 1970 mk -rw-r--r-- 1 root wheel 592 Jan 1 1970 progname.c -rw-r--r-- 1 root wheel 131 Jan 1 1970 regex.h -- rik