On 2023-04-20 09:02, Bruno Haible wrote:
I see two issues:
1) For AC_SYS_YEAR2038 and AC_SYS_YEAR2038_RECOMMENDED, when run on a 32-bit
platform (x86) with glibc < 2.34, there is no
checking for <$CC> option for timestamps after 2038...
line in the output. It _looks_like_ the macro was not invoked or did no
checks. This is quite confusing for a developer who wants to understand what
happened.
Suggestion: Print
checking for gcc option for timestamps after 2038... support not detected
That's odd, since I just tried it and it worked for me. That is, I ran
./gnulib-tool --create-testdir --dir foo -h year2038-recommended
and saw this output from configure when run on gcc45.fsffrance.org:
...
checking for gcc -std=gnu11 option to enable large file support...
-D_FILE_OFFSET_BITS=64
checking for gcc -std=gnu11 option for timestamps after 2038... support
not detected
configure: error: in `/home/eggert/foo':
configure: error: could not enable timestamps after mid-January 2038.
Did you mean to build a 64-bit binary? (E.g.,
'CC="gcc -std=gnu11 -m64"'.) To proceed with 32-bit time_t,
configure with '--disable-year2038'.
See `config.log' for more details
with exit status 1, and I ran
./gnulib-tool --create-testdir --dir bar -h year2038
and saw this output from configure:
...
checking for gcc -std=gnu11 option to enable large file support...
-D_FILE_OFFSET_BITS=64
checking for gcc -std=gnu11 option for timestamps after 2038... support
not detected
...
with an otherwise-successful run.
