From 82bde58b7ac1ba09a7de71d3f9f7cdbf280e8538 Mon Sep 17 00:00:00 2001 From: Arjen de Korte Date: Mon, 22 Feb 2021 09:00:22 +0100 Subject: [PATCH] config.m4: Add largefile support MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The GPGME uses AC_SYS_LARGEFILE in its `configure.ac`, which makes it expects largefile support to be enabled when the system supports it. See the following from https://gnupg.org/documentation/manuals/gpgme/Largefile-Support-_0028LFS_0029.html: "On POSIX platforms you can enable largefile support, if it is different from the default on the system the application is compiled on, by using the Autoconf macro AC_SYS_LARGEFILE. If you do this, then you don’t need to worry about anything else: It will just work. In this case you might also want to use AC_FUNC_FSEEKO to take advantage of some new interfaces, and AC_TYPE_OFF_T (just in case)." Adding this is required on 32-bits and optional on 64-bits platforms. --- config.m4 | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/config.m4 b/config.m4 index 4a5ca35..0883305 100644 --- a/config.m4 +++ b/config.m4 @@ -40,6 +40,10 @@ if test "$PHP_GNUPG" != "no"; then PHP_ADD_INCLUDE($GNUPG_DIR/include) + dnl enable largefile support on 32-bits platform + AC_SYS_LARGEFILE + AC_TYPE_OFF_T + dnl gpgme_op_passwd is not used but was added in 1.3.0 LIBNAME=gpgme LIBSYMBOL=gpgme_op_passwd