git.ipfire.org Git - thirdparty/openembedded/openembedded-core-contrib.git/blob

   1 From ccc0d640c4d829504568330f9674408af5092ffc Mon Sep 17 00:00:00 2001
   2 From: Paul Eggert <eggert@cs.ucla.edu>
   3 Date: Sat, 13 May 2023 09:56:33 -0700
   4 Subject: [PATCH 23/29] Improve AC_SYS_YEAR2038_RECOMMENDED diagnostic
   5
   6 * lib/autoconf/specific.m4 (AC_SYS_YEAR2038_RECOMMENDED):
   7 Do not recommend gcc -m64, as that likely will not work.
   8 Problem reported by Bruno Haible in:
   9 https://lists.gnu.org/r/bug-gnulib/2023-05/msg00060.html
  10 Instead, mention that 32-bit time_t is not recommended
  11 for this package, before telling the builder how
  12 to configure with 32-bit time_t anyway.
  13
  14 Upstream-Status: Backport
  15 Signed-off-by: Khem Raj <raj.khem@gmail.com>
  16 ---
  17  lib/autoconf/specific.m4 | 5 +++--
  18  1 file changed, 3 insertions(+), 2 deletions(-)
  19
  20 diff --git a/lib/autoconf/specific.m4 b/lib/autoconf/specific.m4
  21 index 88e0479e8..91f20bf0d 100644
  22 --- a/lib/autoconf/specific.m4
  23 +++ b/lib/autoconf/specific.m4
  24 @@ -228,8 +228,9 @@ AC_DEFUN([AC_SYS_YEAR2038_RECOMMENDED],
  25  AS_IF([test "$enable_year2038,$ac_have_year2038" = yes,no],
  26     [AC_MSG_FAILURE(m4_text_wrap(
  27        [could not enable timestamps after mid-January 2038.
  28 -       Did you mean to build a 64-bit binary? (E.g., 'CC="${CC} -m64"'.)
  29 -       To proceed with 32-bit time_t, configure with '--disable-year2038'.],
  30 +       This package recommends support for these later timestamps.
  31 +       However, to proceed with signed 32-bit time_t even though it
  32 +       will fail then, configure with '--disable-year2038'.],
  33        [], [], [55]))])])
  34
  35  # _AC_SYS_LARGEFILE_TEST_CODE
  36 --
  37 2.41.0
  38