Date: Sat, 2 Jun 2001 17:22:55 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: obrien@FreeBSD.ORG Cc: arch@FreeBSD.ORG, freebsd-standards@bostonradio.org Subject: Re: time_t definition is wrong Message-ID: <15129.22831.64860.325847@grasshopper.cs.duke.edu> In-Reply-To: <20010602131404.M31257@dragon.nuxi.com> References: <200106012318.f51NI8w38590@bunrab.catwhisker.org> <200106020823.f528N5O98998@earth.backplane.com> <20010602085237.A73968@dragon.nuxi.com> <200106021739.f52Hd9V03943@earth.backplane.com> <p05100e0fb73ee9d458f7@[128.113.24.47]> <20010602124907.G31257@dragon.nuxi.com> <200106022005.f52K5FR04823@earth.backplane.com> <20010602131404.M31257@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
David O'Brien writes: > > NetBSD, OpenBSD, and HP-UX uses 32bit types for time_t. You can add Tru64 (aka OSF/1), where a time_t is an int. As far as I'm concerned, Tru64 is the gold standard for 64-bit platforms. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15129.22831.64860.325847>