Gary E. Miller <g...@rellim.com>: > The 32-bit problem is that you have to deal with timespec(32) > for system time. That breaks in 2038. When we read system time > in timespec(32) we do not know if the currennt year is 1971 or 2039.
The integral part of timespec is time_t which has been 64-bit *even
on 32-bit Linuxes* for, what is it, close to 20 years now?
I am prepared to assume that by 2038 we will be able to put in a
config test that barfs on 32-bit time_t without causing a ripple.
--
<a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>
Please consider contributing to my Patreon page at https://www.patreon.com/esr
so I can keep the invisible wheels of the Internet turning. Give generously -
the civilization you save might be your own.
signature.asc
Description: PGP signature
_______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
