unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Troy Sankey <sankeytms@gmail.com>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel@gnu.org
Subject: Re: fixing python-gpg package, need help
Date: Mon, 09 Jan 2017 09:04:17 -0500	[thread overview]
Message-ID: <148397065764.27447.14504713860418611638@what> (raw)
In-Reply-To: <20170109101429.GB24479@macbook42.flashner.co.il>

[-- Attachment #1: Type: text/plain, Size: 1520 bytes --]

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
> > = 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 ----
> > 
> > Attached is a patch which forces _FILE_OFFSET_BITS = 64 and
> > _LARGEFILE_SOURCE = 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

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

-----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-----

  reply	other threads:[~2017-01-09 14:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-08 21:09 fixing python-gpg package, need help Troy Sankey
2017-01-09 10:14 ` Efraim Flashner
2017-01-09 14:04   ` Troy Sankey [this message]
2017-01-09 14:32     ` Troy Sankey
2017-01-09 21:28 ` Leo Famulari

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=148397065764.27447.14504713860418611638@what \
    --to=sankeytms@gmail.com \
    --cc=efraim@flashner.co.il \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).