Re: recommending AC_SYS_YEAR2038_REQUIRED ?

Bruno Haible writes: > Paul Eggert wrote: >> > How about a middle ground between the two macros? A macro, say >> > AC_SYS_YEAR2038_UNLESS_OPT_OUT (*), that >> >- like AC_SYS_YEAR2038, has the option --disable-year2038, >> >- like AC_SYS_YEAR2038_REQUIRED, fails if a large 'time_t' is >>

Re: recommending AC_SYS_YEAR2038_REQUIRED ?

On Mon, Apr 10, 2023, at 7:00 PM, Paul Eggert wrote: > On 2023-04-10 15:36, Bruno Haible wrote: >> I like this. Thanks. > > OK, then let's hear Zack's opinion and hopefully move forward. I'm also happy with this resolution. I do not have time to do the Autoconf work until the weekend. zw

Re: doc: Clarify list of platforms for year2038 support

On 4/11/23 06:45, Adhemerval Zanella Netto wrote: It makes difference on all ABIs with has originally 32 bit time_t support: i686, microblaze, arm, m68k, sh, csky, nios2, and hppa, powerpc32, sparc32, s390, and mips o32. Thanks, I installed the attached. It also mentions Android, which still

some syntax-check fixes

I tried some sc_* rules from the main Makefile. Patch 0001 fixes an alert by 'kate' for Makefile command lines that don't start with a tab. Patch 0002 fixes some of the "make sc_prohibit_leading_TABs" output. The affected files are not shared with glibc, therefore the change won't cause trouble i

Re: doc: Clarify list of platforms for year2038 support

On 11/04/23 02:33, Paul Eggert wrote: > Oh, I forgot to send comments that partly explain my recent changes in this > area. Here they are, belatedly: > > > On 2023-04-10 05:56, Bruno Haible wrote: > >> +@item >> +Linux/riscv32, > > says this platform used 6