From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: fixing python-gpg package, need help Date: Mon, 9 Jan 2017 16:28:44 -0500 Message-ID: <20170109212844.GA26863@jasmine> References: <148390975770.27447.2744857101049384652@what> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:60715) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cQhUt-0005Rb-FY for guix-devel@gnu.org; Mon, 09 Jan 2017 16:28:56 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cQhUo-00072j-Bg for guix-devel@gnu.org; Mon, 09 Jan 2017 16:28:55 -0500 Received: from out1-smtp.messagingengine.com ([66.111.4.25]:48613) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cQhUo-00072X-4W for guix-devel@gnu.org; Mon, 09 Jan 2017 16:28:50 -0500 Content-Disposition: inline In-Reply-To: <148390975770.27447.2744857101049384652@what> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Troy Sankey Cc: guix-devel@gnu.org 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