year2038: be more insistent about 64-bit time_t
commitce0eeab0095ee700ab1917343d6259e7f8b70c62
authorPaul Eggert <eggert@cs.ucla.edu>
Tue, 7 Nov 2017 07:20:23 +0000 (6 23:20 -0800)
committerPaul Eggert <eggert@cs.ucla.edu>
Sat, 11 Nov 2017 07:14:40 +0000 (10 23:14 -0800)
treea8dabaccde40f8f9ecd69b78d448447c7bc763ea
parent866352f5e5ca93f59a328be97902090314e0fbff
year2038: be more insistent about 64-bit time_t

Applications requiring access to arbitrary files should not be
built with 32-bit time_t on hosts that have 64-bit timestamps,
as this can lead to real trouble at runtime.
* m4/year2038.m4 (gl_YEAR2038): Do not require AC_CANONICAL_HOST.
Check on all systems, not just MinGW.  Use a heuristic involving
TIME_T_32_BIT_OK, cross_compiling, and the touch command to
output a failure or just a warning, to make it more likely that
builders will select 64-bit time_t.
ChangeLog
m4/year2038.m4