From owner-freebsd-sparc64@FreeBSD.ORG Wed Jan 7 09:45:32 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 DD39C16A4D0; Wed, 7 Jan 2004 09:45:32 -0800 (PST) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id DCA2943D78; Wed, 7 Jan 2004 09:44:00 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.10/8.12.9) with ESMTP id i07HhkvT055300; Wed, 7 Jan 2004 09:43:46 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.10/8.12.10/Submit) id i07HhkCJ055299; Wed, 7 Jan 2004 09:43:46 -0800 (PST) (envelope-from obrien) Date: Wed, 7 Jan 2004 09:43:46 -0800 From: "David O'Brien" To: Garance A Drosihn Message-ID: <20040107174346.GA50142@dragon.nuxi.com> References: <200312212239.38557.craig@xfoil.gank.org> <20040106095942.O66232@beagle.fokus.fraunhofer.de> <20040106182824.GA42422@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 5.2-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: harti@freebsd.org cc: freebsd-sparc64@freebsd.org Subject: Re: Gearing up for 64-bit time_t on sparc64 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-sparc64@freebsd.org List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jan 2004 17:45:33 -0000 On Wed, Jan 07, 2004 at 12:08:13AM -0500, Garance A Drosihn wrote: > How flexible should we be? My first thought is to tell people: > > 1) upgrade to RELENG_5_2 > 2) *after* you know that upgrade worked, then run a patch > file (which will already be in /usr/src?), which will > modify the appropriate files needed for this change. > 3) rebuild after making just that one change. No cvsup. I think it has to all be doable given a CVS archive, no external patches. If need be: cvs up -Pd -r RELENG_5_2 make buildworld make kernel reboot make installworld cvs up -Pd -D '' make ... ---\ reboot | what ever is the debugged order to do things... make ... ---/ cvs up -PdA make buildworld make kernel reboot make installworld > Or we could do a more flexible version, combining a -Define in > CFLAGS (set in /etc/make.conf), along with some extra magic > when installing the include files during 'make installworld'. > Some flag such as -DSPARC_TIME_T=BIT32 vs =BIT64. I think we should only do this if we can't achieve this as above. > The remaining steps would be the same, but users could flip > the switch at whatever time they wanted, instead of being > forced to upgrade to RELENG_5_2. I think that will be a nightmare of too much potential for people doing it wrong.