From owner-freebsd-arch@FreeBSD.ORG Sat Nov 15 07:06:42 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1341616A4CE; Sat, 15 Nov 2003 07:06:42 -0800 (PST) Received: from mailhub.fokus.fraunhofer.de (mailhub.fokus.fraunhofer.de [193.174.154.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 407B043FBD; Sat, 15 Nov 2003 07:06:40 -0800 (PST) (envelope-from brandt@fokus.fraunhofer.de) Received: from beagle (beagle [193.175.132.100])hAFF6au20115; Sat, 15 Nov 2003 16:06:36 +0100 (MET) Date: Sat, 15 Nov 2003 16:06:36 +0100 (CET) From: Harti Brandt To: Garance A Drosihn In-Reply-To: Message-ID: <20031115155943.W87142@beagle.fokus.fraunhofer.de> References: <3FB5C942.1010907@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: arch@freebsd.org Subject: Re: 64-bit time_t on sparc64, epilogue(?) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Nov 2003 15:06:42 -0000 On Sat, 15 Nov 2003, Garance A Drosihn wrote: GAD>At 11:35 PM -0700 11/14/03, Scott Long wrote: GAD>>Garance A Drosihn wrote: GAD>>>Recently on the freebsd-sparc64 list, it was mentioned GAD>>>that it would be nice to upgrade time_t on that port to GAD>>>be 64-bit. GAD> [...mumble mumble...] GAD> GAD>>>So, I thought I'd explicitly say that I don't think we GAD>>>should make the change this late in the game.. GAD>> GAD>>Switching to 64-bit time_t this late in the 5.2 cycle will GAD>>likely cause more excitement than we can handle. ... GAD>>...Why don't we put this on the TODO list for 5.3, and GAD>>plan to do it in early January, assuming that Jake and GAD>>Thomas are ok with it. GAD> GAD>Personally I am inclined to think that we have to stop GAD>making ABI/API changes to 5.x or we will never ever get GAD>to "5.x-stable". It would be nice if 5.2 were the last GAD>set of API/ABI changes, so that people who install it can GAD>at least have a painless upgrade to 5.3-release (which GAD>will hopefully be 5.x-stable). GAD> GAD>However, I really would like to see the 64-bit time_t GAD>happen, and I'm certainly willing to help out (as time GAD>permits) if we were to make this change on sparc64 in GAD>early January. I'll even start testing such changes on GAD>my own sparc64 system during the code-freeze for 5.2. GAD> GAD>[however, it takes about 11 hours for build/installworld GAD>on my system, so there's a limit to how much I can test!] GAD> GAD>Certainly it's more important to get make-release and GAD>kse-for-sparc64 working for 5.2-release than it is to GAD>make this time_t change. I'm running one of my two sparcs since then without any problem with 64-bit time_t (I don't have many ports on it - perl, bash, a dozen or so). I was waiting for thomas and jake to say something on this. Also someone wanted to test it, but I did not here from him. I think that Scott is right, it's too late for 5.2 but we should definitely try to do it for 5.3. The biggest problem is getting the upgrade process right, but this should be manageable. harti -- harti brandt, http://www.fokus.fraunhofer.de/research/cc/cats/employees/hartmut.brandt/private brandt@fokus.fraunhofer.de, harti@freebsd.org