Re: Y2038 - best way forward in Debian?
* Ben Hutchings:
> On Sun, 2020-02-09 at 11:57 +0100, Florian Weimer wrote:
>> * Ben Hutchings:
>>
>> > If I recall correctly, glibc *will* provide both entry points, so there
>> > is no ABI break. But the size of time_t (etc.) exposed through libc-
>> > dev is fixed at glibc build time.
>>
>> Is this a Debian-specific decision?
>
> I though that was the *upstream* decision, but perhaps that's still not
> decided after all?
There's going to be a _TIME_BITS selector, similar to
_FILE_OFFSET_BITS.
There was a proposal to have only one API before, but I think the
agreement was that it wouldn't save much complexity.
Reply to: