From mboxrd@z Thu Jan 1 00:00:00 1970 From: Troy Sankey Subject: Re: fixing python-gpg package, need help Date: Mon, 09 Jan 2017 09:04:17 -0500 Message-ID: <148397065764.27447.14504713860418611638@what> References: <148390975770.27447.2744857101049384652@what> <20170109101429.GB24479@macbook42.flashner.co.il> Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha256"; boundary="===============0708400614==" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:37978) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cQaYl-0007Gr-5p for guix-devel@gnu.org; Mon, 09 Jan 2017 09:04:28 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cQaYk-0001ZC-3C for guix-devel@gnu.org; Mon, 09 Jan 2017 09:04:27 -0500 Received: from mail-qk0-x22a.google.com ([2607:f8b0:400d:c09::22a]:33950) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cQaYj-0001Z3-W2 for guix-devel@gnu.org; Mon, 09 Jan 2017 09:04:26 -0500 Received: by mail-qk0-x22a.google.com with SMTP id a20so141701013qkc.1 for ; Mon, 09 Jan 2017 06:04:25 -0800 (PST) Content-Disposition: inline In-Reply-To: <20170109101429.GB24479@macbook42.flashner.co.il> 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: Efraim Flashner Cc: guix-devel@gnu.org --===============0708400614== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Quoting Efraim Flashner (2017-01-09 05:14:29) > 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 > > =3D 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_BI= TS =3D 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 ---- > > = > > Attached is a patch which forces _FILE_OFFSET_BITS =3D 64 and > > _LARGEFILE_SOURCE =3D 1, as per the gpgme documentation [1]. This fixes > > the build on my laptop (i686), but I'm quite sure this is a bad hack. > > = > = > Since your laptop is actually 32-bit, does python-gpg build without the > patch? If it does build without the patch, then it means that the > 64-bit-ness of the build-machine on hydra is leaking into the build > environment, and it should be set to the 32/64-bit-ness of the > %target-system. No, without the patch my 32-bit system produces the same error as hydra's 32-bit build. Troy --===============0708400614== MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Description: signature Content-Type: application/pgp-signature; name="signature.asc"; charset="us-ascii" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEE0zLJ6STd4Cp+CgbIgs677ofYV8IFAlhzmFsACgkQgs677ofY V8JbpQ/+PqlhLg202J5jzfYCsXpK8/T/S5uv/zNwJE4LQLmQpDO5dau7+dmH2bcY aCYhdIO16TaIyu89eyoAFMLxvuf2xmakfH5ZPgBHghuLIom0AP1uY+v8kZkQdxQa LZ7L9McFE+tDsJyuXECm9j+cr0aQbQJfnh7FV5rPwXqYuQ7oVoTz1SrlyZznaTHD zPqeh8hJLYFPalLWbasumKYqRumDk3i3bN99vJaztaS3CrlUbMU9/ZV4pRKXpJRW Lz2C53ZNLlbx9ho7M3igplLfYB3MPOgl6qQAJvpklrajo3HF1UIclUCbw5K7W0b8 rnONIyrCPJepHPa9hBQVSdq4WlQLT1Q5Cz//Jw8idGtwuCZENllks3u3pO8Zcpp/ 89aO7INfdaKOlpaMiKbnrHAeEphk8qseoYAUEXniJnKo/mKqX6gdk05rfSumMUSu UVyvymzINplnRy32y+L8NKdy0jH4UbrsXPNEB3FZd9jeQrBeyQ3BIUWqZmaYQEmV gSux96GvIW/K7Ze6unxiD+0dLz/B+9XbvMZpCNxh0h74wiUOe40DmYZ1+mdRSlIl 05IW/ZgJwvAihCpHPeQKM9IWVp8c+MdI7eInswjXvYBVLf28NSTkz+iZRBwhVMA2 vK4Qk8NnwYP0L5PRBnX9257SIgpD04PG2cSH5zYELhKUXJIPJ9I= =rosd -----END PGP SIGNATURE----- --===============0708400614==--