Am Donnerstag, 5. September 2024, 20:20:32 CEST schrieb Paul Eggert:
> On 2024-09-05 10:03, Andreas K. Huettel wrote:
> > at least time64 implies largefile, so that will get sorted as side
> > effect.
>
> Right, but this means the "t" in "t64" is somewhat misleading, as it's
> not just about time
On 2024-09-05 10:03, Andreas K. Huettel wrote:
at least time64 implies largefile, so that will get sorted as side
effect.
Right, but this means the "t" in "t64" is somewhat misleading, as it's
not just about time: it also affects off_t, ino_t, etc., effects that
are in some cases more importa
> One possible improvement would be to append "t32" if you want 32-bit
> time_t, instead of appending "t64" for 64-bit time_t.
Versioned symbols in glibc should mean that old binaries will still run (even
if they misbehave when they look at the system time), just like with most
previous ABI chan
> One possible improvement would be to append "t32" if you want 32-bit
> time_t, instead of appending "t64" for 64-bit time_t.
I hope you aren't earnestly proposing this worst of both worlds idea
(let's change CHOST for any system with no ABI change).
> I felt the same way about the 64-bit off
Hi Todd,
> Versioned symbols in glibc should mean that old binaries will still run (even
> if they
> misbehave when they look at the system time), just like with most previous
> ABI changes
> to libc over the years.
That is irrelevant here. glibc takes care of its own interface and is not a
On Thu, Sep 5, 2024 at 6:51 AM Andreas K. Huettel wrote:
>
> >
> > FWIW, yocto/openembedded have also done the same and offered a distro
> > setting to the users
> > to select 32bit time_t if they wished to but defaulted to 64bit time_t.
>
> In case of Openembedded, which (as far as I understand)
One possible improvement would be to append "t32" if you want 32-bit
time_t, instead of appending "t64" for 64-bit time_t. That way, people
wouldn't be stuck with appending that confusing "t64" for the
foreseeable future, and only specialists concerned with 32-bit time_t
would need to know abou
Hi Wookey,
> > in Gentoo Linux we want to change our CHOST triplets for 32-bit glibc
> > systems that use
> > 64-bit time_t, since this is technically an ABI change which breaks binary
> > compatibility [1].
>
> > * In an ideal world this change would be synchronized across distributions.
> >
>
> FWIW, yocto/openembedded have also done the same and offered a distro
> setting to the users
> to select 32bit time_t if they wished to but defaulted to 64bit time_t.
In case of Openembedded, which (as far as I understand) mostly offers
complete system images for download or build, I might ha
