From mboxrd@z Thu Jan 1 00:00:00 1970 From: Efraim Flashner Subject: Re: fixing python-gpg package, need help Date: Mon, 9 Jan 2017 12:14:29 +0200 Message-ID: <20170109101429.GB24479@macbook42.flashner.co.il> References: <148390975770.27447.2744857101049384652@what> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="XF85m9dhOBO43t/C" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43148) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cQWyK-0005ow-4R for guix-devel@gnu.org; Mon, 09 Jan 2017 05:14:37 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cQWyF-0004M8-8W for guix-devel@gnu.org; Mon, 09 Jan 2017 05:14:36 -0500 Received: from flashner.co.il ([178.62.234.194]:42138) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cQWyF-0004Lx-0B for guix-devel@gnu.org; Mon, 09 Jan 2017 05:14:31 -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 --XF85m9dhOBO43t/C Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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). >=20 > Relevant build log snippet: >=20 > ---- 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= =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 ---- >=20 > 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. >=20 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. > Seeking help! >=20 > Troy >=20 > [0] http://hydra.gnu.org/build/1749143 > [1] https://www.gnupg.org/documentation/manuals/gpgme/Largefile-Support-_= 0028LFS_0029.html --=20 Efraim Flashner =D7=90=D7=A4=D7=A8=D7=99=D7=9D = =D7=A4=D7=9C=D7=A9=D7=A0=D7=A8 GPG key =3D A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 Confidentiality cannot be guaranteed on emails sent or received unencrypted --XF85m9dhOBO43t/C Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEkVdB/rIvpOM7bo+N9MHTkX6s7pMFAlhzYoQACgkQ9MHTkX6s 7pNS8w//VCbYDs9mVL7x3P19S1j/pDDc5z7s9WcPagpMWNz/sbjsLbhTgR2gsgyv aHjTlxabHeYaqb3zU7W6S7fMeXXGFmjySVaRUrCg7N1uRjqwZsWQRoX3Xugk3C4v 1mZGE6g7BJdDrZdi7JRbIDjsPL+rUMweyjt+7vljr+UaTv1dIXosMGKHhKruZ3D/ 5C1eO4Du4gB5tD/C4dEn7tODbokzKz946hOIbxYsZfZbkU2BEK5mZhjLYYFJtqsx BGcTr0yCVoiDV2kqyuzuE1qxVDkNxrqITAdISwHjhkl+i7Ztkv0AYzem2ZZkDmQV Az2tZCbyUjqLycP9FGjIbgMOlV4ing1fJYB3d4draxzm7qSuW47pLhZkj1avLoyV CaZebbn6mJZQRy37QpSBCUyQuUXsj59exYdFKlnLFl7K47C60Ou6m0GnULC0QA7h T0c/Sn/LzQsj9vWQ3j2swu+7t9HnjIKseX9aZQ8Gp8KZbBQPiJu1P81+WxIimH60 bz6Wicks0k/OI5MFDxb78k4Y2ca2+v8kfd7Z9B7/SANSuLQVnCGwEFc0gtN9IGfr G0LPtNYKcWhhB5zkL49Wd8RAlZlAKpDu7/MWht8+6PTaX55PKKIvz/S5cCvspfEs TcMJuJWJDJbRUvg/tJf+PlIalQF1u3zJjHJhf9MtAecnP5H3z0o= =Dzut -----END PGP SIGNATURE----- --XF85m9dhOBO43t/C--