Due to having largefile support enabled by default, >=gpgme-1.2.0 tends to break existing applications and provides no good solution to fix the issue. As a software developer myself, I see no reason to enable largefile support in my program by default and I would really appreciate if I were able to determine whether, in particular case, the related CFLAG has to be added. To avoid breaking other programs, I suggest adding additional '--largefile-cflags' option to GPGME, printing the '-D_FILE_OFFSET_BITS=64' flag if gpgme was compiled with largefile support.
Please send your suggestions to GPGME upstream. gnupg-devel@gnupg.org