[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: fixing python-gpg package, need help
|
From: |
Leo Famulari |
|
Subject: |
Re: fixing python-gpg package, need help |
|
Date: |
Mon, 9 Jan 2017 16:28:44 -0500 |
|
User-agent: |
Mutt/1.7.2 (2016-11-26) |
On Sun, Jan 08, 2017 at 04:09:17PM -0500, Troy Sankey wrote:
> I'm trying to fix the python-gpg package. Latest build [0] was a
> failure because gpgme.h claims gpgme was compiled with _FILE_OFFSET_BITS
> = 64, implying the current build (python-gpg) doesn't define any
> _FILE_OFFSET_BITS (it should also be set to 64, I think).
>
> Relevant build log snippet:
>
> ---- cut here / start ----
> swigging gpgme.i to gpgme_wrap.c
> swig -python -py3 -builtin -threads -outdir gpg -o gpgme_wrap.c gpgme.i
> gpgme.h:104: Error: CPP #error "GPGME was compiled with _FILE_OFFSET_BITS =
> 64, please see the section "Largefile support (LFS)" in the GPGME
> manual.". Use the -cpperraswarn option to continue swig processing.
> error: command 'swig' failed with exit status 1
> ---- cut here / end ----
It seems related to this upstream discussion:
https://lists.gnupg.org/pipermail/gnupg-devel/2016-September/031660.html