[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAA2zVHp+HM+DXU-KEqODy=1GVBJrAJXskPm029Sr2UY9+uYa1g@mail.gmail.com>
Date: Wed, 19 Mar 2025 11:57:10 -0400
From: James Y Knight <jyknight@...gle.com>
To: musl@...ts.openwall.com
Subject: Re: Making user libraries Y2038 compatible?
On Tue, Mar 18, 2025 at 10:18 PM Khem Raj <raj.khem@...il.com> wrote:
>
> Musl always had 64bit time_t and off_t regardless of 32bit or 64bit systems
> so I guess we are good here.
"Always"? 2019 wasn't _that_ long ago that everyone's forgotten it
existed already, is it?
https://musl.libc.org/time64.html
https://git.musl-libc.org/cgit/musl/commit/?id=38143339646a4ccce8afe298c34467767c899f51
For musl's time64 transition, the impacted non-libc libraries which
used time_t in their ABIs just took the ABI break. Distros rebuilt
everything that needed to be rebuilt.
Taking an ABI break is also what 99% of libraries are doing with the
glibc transition -- I suppose with libselinux being the exceptional
case.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
