Date: Sat, 21 Feb 2004 13:59:06 -0500 From: Garance A Drosihn <drosih@rpi.edu> To: Harti Brandt <brandt@fokus.fraunhofer.de> Cc: ru@freebsd.org Subject: Re: Back to the Future - 64-bit time_t on sparc64 Message-ID: <p0602045fbc5d5375b7d9@[128.113.24.47]> In-Reply-To: <20040221140438.M87450@beagle.fokus.fraunhofer.de> References: <40306CE7.6080104@mindspring.com> <20040216193108.GE12181@seekingfire.com> <p0602041ebc56dd660908@[128.113.24.47]> <20040217040616.GL12181@seekingfire.com> <20040219143838.GL68388@seekingfire.com> <p0602044bbc5ac1a48967@[128.113.24.47]> <20040219204008.GB3545@electra.cse.Buffalo.EDU> <p0602044cbc5ad23c6d38@[128.113.24.47]> <20040219205750.GC3545@electra.cse.Buffalo.EDU> <p06020453bc5b2ce4acc3@[128.113.24.47]> <20040220035635.GA69900@dhcp01.pn.xcllnt.net> <p0602045abc5c248db8bd@[128.113.24.47]> <20040221140438.M87450@beagle.fokus.fraunhofer.de>
next in thread | previous in thread | raw e-mail | index | archive | help
At 2:07 PM +0100 2/21/04, Harti Brandt wrote:
>GAD>I *think* what would work is something like:
>GAD>In /etc/make.conf, users would define:
>GAD>
>GAD>SPARCWORLD_TIMET=32bit or SPARCWORLD_TIMET=64bit
>GAD>
>GAD>If neither is defined, than 32-bit is assumed.
>
>That would look like an option to build either way and I think
>we shouldn't have such an option that allows 32bit time_t's.
>This will require to ship to sets of packages and will give as
>a lot of bug reports because of mismatched packages and kernels.
Well, I was just giving a basic idea of something we could do,
I did not mean to imply this is all we would ever do. This
would just be a transition aid, and like all transition aids
it would eventually disappear.
Initially, I think we DO want to allow 32-bit builds. But then,
after a week or two, we would simply change the script to say:
"I'm sorry dave,
but I can't let you do 32-bit builds anymore".
</reference-to-2001>
Why do we want to allow 32-bit builds?
Because the instructions say:
First do a 32-bit build. Install it.
Once you know that that installation is working,
Change _types.h, do a 64-bit build, and install that.
>GAD> I am certain that there are some details I have overlooked, but
>GAD> I really don't have the time to think it through right now.
I probably should have *started* my message by emphasizing this part
more strongly. I think the low-level details are workable, but some
developer would have to sit down and think them out. That is what I
do not have the time to do.
Also keep in mind that whatever we do for 5.x-current, we will
also have users who are sticking on 5.2.1-security until 5.2-
release comes out. It would be nice if they also had a way to
make a smooth transition, without the risk of shooting their
foot off...
--
Garance Alistair Drosehn = gad@gilead.netel.rpi.edu
Senior Systems Programmer or gad@freebsd.org
Rensselaer Polytechnic Institute or drosih@rpi.edu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p0602045fbc5d5375b7d9>