On 2024-10-01, Lawrence D'Oliveiro wrote:
On Tue, 1 Oct 2024 00:56 +0100 (BST), John Dallman wrote:
In article <vdfdcj$2dsh2$[email protected]>, [email protected]d (Lawrence
D'Oliveiro) wrote:
On Tue, 1 Oct 2024 00:25 +0100 (BST), John Dallman wrote:
In article <vdf71h$2cn51$[email protected]>, [email protected]d (Lawrence
D'Oliveiro) wrote:
It's not being ignored. The Linux kernel added the option to build a >>>>> 32-bit kernel with time_t having 64 bits
The same has happened for Windows and Apple's operating systems.
A lot of the work for 2038 is already done.
They're not supporting 32-bit code any more. Linux is.
Apple only run 64-bit code on recent OSes, yes, but Windows 11 still
runs 32-bit applications, even though the OS is only available in 64-bit
form.
But those 32-bit Windows apps are not being rebuilt for 64-bit time_t. The option isn’t there.
Is Windows really affected in the same way?
According to the last bullet item in [1], WINAPI does not rely on time_t
*and* the parts that do have it have built with 64-bit time_t by default
for a while now?
(What does this mean for people using third-party compilers? Just needs
to be enabled there too?)
[1]
https://en.wikipedia.org/w/index.php?oldid=1244809614#Implemented_solutions
(Either way, trusting this, it seems the rebuild option has been there
for almost two decades now?)
--
Nuno Silva
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)