From owner-freebsd-sparc64@FreeBSD.ORG Tue Feb 24 16:45:31 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 CD06016A4CE for ; Tue, 24 Feb 2004 16:45:31 -0800 (PST) Received: from blake.polstra.com (blake.polstra.com [64.81.189.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D7A943D1D for ; Tue, 24 Feb 2004 16:45:31 -0800 (PST) (envelope-from jdp@polstra.com) Received: from strings.polstra.com (dsl081-189-067.sea1.dsl.speakeasy.net [64.81.189.67]) by blake.polstra.com (8.12.9p2/8.12.9) with ESMTP id i1P0jRtC032687; Tue, 24 Feb 2004 16:45:28 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20040220173231.GA1344@electra.cse.Buffalo.EDU> Date: Tue, 24 Feb 2004 16:45:27 -0800 (PST) From: John Polstra To: Ken Smith X-Bogosity: No, tests=bogofilter, spamicity=0.484330, version=0.14.5 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 00:45:31 -0000 On 20-Feb-2004 Ken Smith wrote: > Has anyone tried using cvsup on a 64btt system yet? I'm getting odd > results on a system being set up as a cvsup mirror - it seems to think > it needs to touch (timestamp correction) every file in the repo but > there is no visible change to the timestamp on the files themselves. Well, Modula-3 still thinks time_t is 32 bits, of course. I haven't looked at the patches for a 64-bit time_t, so I'm not sure what provisions have been made for backward compatibility. I assume you (the collective "you") kept compatibility versions of time(2), stat(2), lstat(2), etc., with 32-bit time_t fields so that existing executables would continue to work. If that's the case, then existing CVSup binaries ought to work OK. 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. 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'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. [Somebody in a big truck smashed into my mailbox and then drove away. Now the postal service has told me they won't deliver my mail after this weekend unless I fix it *sigh*. Just another damned hardware problem. :-] Let's see, where was I ... Oh, yeah ... 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. If other data structures got shuffled, try to find them, or ask me where they are. Figure out the ports-Makefile-fu to make the new patches get applied only if the system has a recent enough __FreeBSD_version. That ought to do it. A new M3 bootstrap file might be needed, but I don't think so. Let me know if you run into questions or problems. John