From owner-freebsd-sparc64@FreeBSD.ORG Tue Feb 17 12:05:20 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 EF81316A4CE for ; Tue, 17 Feb 2004 12:05:20 -0800 (PST) Received: from smtp1.server.rpi.edu (smtp1.server.rpi.edu [128.113.2.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB07443D2F for ; Tue, 17 Feb 2004 12:05:20 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp1.server.rpi.edu (8.12.8/8.12.8) with ESMTP id i1HK5JvB002505; Tue, 17 Feb 2004 15:05:19 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20040217040616.GL12181@seekingfire.com> References: <40306CE7.6080104@mindspring.com> <20040216193108.GE12181@seekingfire.com> <20040217040616.GL12181@seekingfire.com> Date: Tue, 17 Feb 2004 15:05:18 -0500 To: Tillman Hodgson , sparc64@freebsd.org From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: CanIt (www . canit . ca) Subject: Re: Back to the Future - 64-bit time_t on sparc64 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: Tue, 17 Feb 2004 20:05:21 -0000 At 10:06 PM -0600 2/16/04, Tillman Hodgson wrote: >On Mon, Feb 16, 2004, Garance A Drosihn wrote: > >> This is described in a little detail in the UPDATING.64BTT file. > >Speaking of which, in that document you mention the problem with >portupgrade and note that you have a prebuilt package available >for download. The issue is 'cvsup', not portupgrade. My point was that you should not run 'cvsup' before trying to recompile ports. That is partially because the cvsup you *have* (which would be a 32-bTT version of cvsup) will not work until you recompile it -- so of course you can't run it before recompiling your ports.... Perhaps I need to come up with better wording for that section. Also note that if you *do* recompile all of ezm3 and cvsup, then you will have a 64-bTT version, and that will work okay. >Is that necessary, or will a portupgrade of portupgrade itself >generally compile fine (allowing one to use the newly compiled >version of portupgrade to get the rest of the ports done)? As noted in the writeup, start out with portupgrade -Rr -f portupgrade ruby and everything should work out okay. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu