Dear Maintainer,

See buildbot output:
https://builder.sourceware.org/buildbot/#/builders/270/builds/8114/steps/3/logs/stdio

Whether or not generated configure file is correct, it's inconsistent with
output generated by vanilla autoconf version 2.69 and it triggers buildbot
failures.

Regards,
Dave

debian/patches/avoid-undefined-behavior-for-32bit-off_t.patch:

the patch is also in Debian's autoconf (2.72) package, apparently never
forwarded.


Description: Fix undefined behavior for 32-bit off_t.
  autoconf (2.69-6) unstable; urgency=low
  .
    * lib/autoconf/specific.m4: Use ((off_t) 1 << 31) << 31 in place of
      (off_t) 1 << 62 to avoid undefined behavior when off_t is 32-bit.
      Closes: #742780.  Thanks to Mathieu Malaterre <malat@debian.org> for
      reporting this bug.
Author: Ben Pfaff <pfaffben@debian.org>
Bug-Debian: http://bugs.debian.org/742780
Forwarded: yes

--- autoconf-2.69.orig/lib/autoconf/specific.m4
+++ autoconf-2.69/lib/autoconf/specific.m4
@@ -92,7 +92,7 @@ m4_define([_AC_SYS_LARGEFILE_TEST_INCLUD
      We can't simply define LARGE_OFF_T to be 9223372036854775807,
      since some C++ compilers masquerading as C compilers
      incorrectly reject 9223372036854775807.  */
-@%:@define LARGE_OFF_T (((off_t) 1 << 62) - 1 + ((off_t) 1 << 62))
+@%:@define LARGE_OFF_T ((((off_t) 1 << 31) << 31) - 1 + (((off_t) 1 <<
31) << 31))
    int off_t_is_large[[(LARGE_OFF_T % 2147483629 == 721
                        && LARGE_OFF_T % 2147483647 == 1)
                       ? 1 : -1]];[]dnl

Don't all Debian architectures now use 64-bit offsets (_FILE_OFFSET_BITS == 64).  In features.h,
we have:

#if defined _FILE_OFFSET_BITS && _FILE_OFFSET_BITS == 64
# define __USE_FILE_OFFSET64    1
#endif

So, maybe the above patch can now be dropped.

Some patch also adds two free() statements.

Dave

that should be fixed in the autoconf package as well.