[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] year2038: support glibc 2.34 _TIME_BITS=64

From: Paul Eggert
Subject: Re: [PATCH] year2038: support glibc 2.34 _TIME_BITS=64
Date: Wed, 7 Jul 2021 14:58:17 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0

On 7/7/21 1:45 AM, Florian Weimer wrote:

Y2038 support requires recompilation.  If you are able to do that, why
not recompile for a 64-bit architecture?

Doesn't this argue against _TIME_BITS=64 in general? It seems to be saying that one should just recompile for 64-bit, and never use _TIME_BITS=64.

This probably needs per-package/component work to enable dual ABI,
similar to what glibc did for its time_t interfaces....
I don't expect many upstreams to support this effort.

Two separate i386 ports seem to require the least human
resources to maintain.

That's a reasonable approach and if people want to do that they can, even with the latest Gnulib and the next version of Glibc.

However, people who want to run old binaries will surely stick to the 32-bit-time_t i386 port, which means they won't use the 64-bit-time_t i386 port. So it's not clear to me that they will cotton to this approach.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]