Date: Sun, 14 Mar 2004 16:09:44 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Stephen McKay <smckay@internode.on.net> Cc: current@freebsd.org Subject: Re: HEADS UP! MAJOR change to FreeBSD/sparc64 Message-ID: <20040315000944.GA93356@xor.obsecurity.org> In-Reply-To: <200403140716.i2E7GDKa007204@dungeon.home> References: <p060204f5bc750679b827@[128.113.24.47]> <200403140716.i2E7GDKa007204@dungeon.home>
next in thread | previous in thread | raw e-mail | index | archive | help
--DocE+STaALJfprDB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Mar 14, 2004 at 05:16:13PM +1000, Stephen McKay wrote: > On Wednesday, 10th March 2004, Garance A Drosihn wrote: >=20 > >The long-threatened change for FreeBSD/sparc64 has now been > >committed. This changes time_t to be a 64-bit quantity, the > >same as it is for the AMD64 and IA64 architectures. People > >running FreeBSD/sparc64 *will* have to read the UPDATING.64BTT > >file for instructions on how to safely build and install this > >change. >=20 > The change to 64-bit time is essential, of course, but I don't understand > why it has to break backward compatibility. Surely you just allocate a > bunch of new system call numbers (for the 64-bit variants) while keeping > the old ones (so 32-bit time calls still work) and bump the version > number of every library. What else is going on? (I don't have a Sparc > or I'd join your experiment.) No-one donated their time to do it that way. Kris --DocE+STaALJfprDB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAVPRIWry0BWjoQKURAoJIAJ9Kk50F/eNsLx9m9cIDP/U3FZigRwCfVUps Lr4SN2NP4uNfWBFWRUuq6PY= =r4yt -----END PGP SIGNATURE----- --DocE+STaALJfprDB--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040315000944.GA93356>