summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPaul Eggert <eggert@cs.ucla.edu>2023-05-13 09:56:33 -0700
committerPaul Eggert <eggert@cs.ucla.edu>2023-05-13 09:57:44 -0700
commitccc0d640c4d829504568330f9674408af5092ffc (patch)
tree1d57921c08ffb9c5d24c80862b13126b9557c2cd
parent33c26d2700f927432c756ccf7a4fc89403d35b95 (diff)
downloadautoconf-ccc0d640c4d829504568330f9674408af5092ffc.tar.gz
Improve AC_SYS_YEAR2038_RECOMMENDED diagnostic
* lib/autoconf/specific.m4 (AC_SYS_YEAR2038_RECOMMENDED): Do not recommend gcc -m64, as that likely will not work. Problem reported by Bruno Haible in: https://lists.gnu.org/r/bug-gnulib/2023-05/msg00060.html Instead, mention that 32-bit time_t is not recommended for this package, before telling the builder how to configure with 32-bit time_t anyway.
-rw-r--r--lib/autoconf/specific.m45
1 files changed, 3 insertions, 2 deletions
diff --git a/lib/autoconf/specific.m4 b/lib/autoconf/specific.m4
index 88e0479e..91f20bf0 100644
--- a/lib/autoconf/specific.m4
+++ b/lib/autoconf/specific.m4
@@ -228,8 +228,9 @@ AC_DEFUN([AC_SYS_YEAR2038_RECOMMENDED],
AS_IF([test "$enable_year2038,$ac_have_year2038" = yes,no],
[AC_MSG_FAILURE(m4_text_wrap(
[could not enable timestamps after mid-January 2038.
- Did you mean to build a 64-bit binary? (E.g., 'CC="${CC} -m64"'.)
- To proceed with 32-bit time_t, configure with '--disable-year2038'.],
+ This package recommends support for these later timestamps.
+ However, to proceed with signed 32-bit time_t even though it
+ will fail then, configure with '--disable-year2038'.],
[], [], [55]))])])
# _AC_SYS_LARGEFILE_TEST_CODE