Re: time64 / Large File Support: 2) default time64 breaks legacy 32bit binaries

[Paul Eggert <eggert@cs.ucla.edu>]

On 1/26/23 05:21, Adhemerval Zanella Netto via Libc-alpha wrote:
> So although I am not quite against --enable-hard-sys-types64, I personally
> think we should do something more drastically (which not all other glibc
> developers agree) and flip the switch to enable 64-bit time_t *as default*
> and document 32-bit is opt-in.

Just to clarify, there are two issues here:

A. Should _FILE_OFFSET_BITS and _TIME_BITS default to 64 instead of to 32?

B. Should _FILE_OFFSET_BITS=64 and _TIME_BITS=64 be the *only* values 
supported? That is, should the old API (with 32-bit time_t, off_t, etc.) 
be available only to old 32-bit executables, and not to newly-built 
32-bit executables?

As I understood it, the proposal was that (A) and (B) both default to 
"no", but '.../configure --enable-hard-sys-types64' would change both 
(A) and (B) to "yes".

It sounds like you're proposing a more drastic approach, in which (A) 
and (B) both default to "yes", but '.../configure 
--disable-hard-sys-types64' changes them both to "no". Is that right?

Another possibility is to adopt the milder approach for glibc version N, 
and switch to the more drastic approach in glibc version N+1.This would 
give distros time to test this new configure-time option before it's the 
default.