From owner-freebsd-sparc64@FreeBSD.ORG Thu Jul 15 14:57:07 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 F197616A4CE for ; Thu, 15 Jul 2004 14:57:07 +0000 (GMT) Received: from rikwade.com (rikwade.com [212.13.208.233]) by mx1.FreeBSD.org (Postfix) with ESMTP id C063943D45 for ; Thu, 15 Jul 2004 14:57:07 +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 A50D718088; Thu, 15 Jul 2004 15:57:05 +0100 (BST) Message-ID: <40F69B39.9050602@rikwade.com> Date: Thu, 15 Jul 2004 15:56:57 +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: Garance A Drosihn References: <40F4DE72.5010500@rikwade.com> In-Reply-To: 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: Thu, 15 Jul 2004 14:57:08 -0000 Garance A Drosihn wrote: > At 8:19 AM +0100 7/14/04, Rik Wade wrote: > This sentence does not sound good. What do you mean by "buildworld > on the new kernel"? If you are following the instructions, you > will have to do `make buildworld' *before* you have installed any > new kernel. I was at step 3 of installing the 64-bit time_t system. This is being built on a kernel compiled with step pre-2. i.e. the new kernel source but with time_t still set to __int32_t. > Based on that comment, my guess is that you are running on a 64-bTT > kernel, and a userland which was built for an earlier (32-bTT) > system. If that is true, then you will run into many problems. I believe this may have been the case due to a mistaken reboot on to the 64-bTT kernel image prior to successful compilation of the 64-bTT userland binaries. Whatever the reason, it's down to user error. I've bounced on to the 32-bTT kernel and things are progressing once again (thanks to kernel.old). -- rik