From owner-freebsd-sparc64@FreeBSD.ORG Wed Feb 25 13:55:22 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 9566B16A4CE for ; Wed, 25 Feb 2004 13:55:22 -0800 (PST) Received: from smtp2.server.rpi.edu (smtp2.server.rpi.edu [128.113.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 37D5443D2F for ; Wed, 25 Feb 2004 13:55:22 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp2.server.rpi.edu (8.12.8/8.12.8) with ESMTP id i1PLtFnI031772; Wed, 25 Feb 2004 16:55:16 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: Date: Wed, 25 Feb 2004 16:55:14 -0500 To: John Polstra , Ken Smith From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: CanIt (www . canit . ca) cc: freebsd-sparc64@freebsd.org Subject: RE: 64btt cvsup? 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, 25 Feb 2004 21:55:22 -0000 At 4:45 PM -0800 2/24/04, John Polstra wrote: >However, if you rebuild CVSup from source, it will most likely >have problems. This will be the case until I or somebody else >adds a few patches to the port to deal with the change. [to pick up from where I left off in my previous reply...] I have done force-rebuilds (portupgrade -Rr -f) of ezm3 and cvsup-without-gui after upgrading my systems to 64-bTT. These seem to be working okay, although it is true that I haven't looked too closely. cvsup on the sparc "looks like" it is finding the right set of files to update. However, I have not run it often and I have not done any serious checking to see how accurately it works. >If __FreeBSD_version wasn't already bumped to mark the change >to a 64-bit time_t, somebody please bump it ASAP. We're going >to need that in order to know whether to apply the new patches >or not. I'll add this to the list of things to do on March 10th. That is the date that I plan to commit the change that actually switches sparc64 to the 64-bit time_t. >I've already got a fire drill scheduled for this weekend, so >I'd appreciate it if somebody else could make at stab a the >patches for the ezm3 port. ... The place to start on the patch >is with the file > > libs/m3core/src/unix/freebsd-4.sparc64/Utypes.i3 > >in the ezm3-1.1 source distribution. (Do a "make patch" in the >lang/ezm3 port and then find the file.) Find "time_t" and change >its type to int64_t or whatever it ought to be. In the same >directory, edit "Ustat.i3" if necessary, to change the layout of >the stat structure appropriately. I'll try to take a quick look at this. I'm puzzled why it would be needed though. Didn't this come up on amd64 and ia64 ports? (or is cvsup not-available on those architectures?) -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu