Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Le Bihan <eric.le.bihan.dev@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] python Gobject
Date: Fri, 24 Jan 2014 19:27:01 +0100	[thread overview]
Message-ID: <20140124182659.GB30974@pc-eric> (raw)
In-Reply-To: <20140123170253.GB10856@pc-eric>

On Thu, Jan 23, 2014 at 06:02:56PM +0100, Eric Le Bihan wrote:
> I dug into the mailing list and found this discussion, which seems to be
> related to this problem:
> http://lists.busybox.net/pipermail/buildroot/2011-August/045038.html.
I've also found this interesting presentation about Python and
cross-compilation: http://whatschrisdoing.com/blog/talks/PyConTalk2012.pdf.

The author points out that cross-compiling Python extensions like
python-gobject, that do not rely on distutils, is likely to fail, because they
rely on the _host_ python-config to get the path to Python headers. In our
case, we end up with headers for a 64-bit machine
(host/usr/bin/include/python2.7) instead of the ones for the 32-bit target
(target/usr/include/python2.7).

I'll patch the autotools files in the modules of the PyGtk stack to handle
this properly.

Best regards,
ELB

  reply	other threads:[~2014-01-24 18:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-17 10:39 [Buildroot] python Gobject Freedreamer
2014-01-17 11:31 ` Eric Le Bihan
2014-01-17 12:39   ` Freedreamer
2014-01-17 15:44     ` Eric Le Bihan
2014-01-21  7:41       ` sambuff
2014-01-21 17:36         ` Eric Le Bihan
2014-01-22 19:57           ` sambuff
     [not found]             ` <20140123134942.GA10856@pc-eric>
     [not found]               ` <CAGzWX_Jgdzctc_=-9XBg4Bw__KtdNwF3MChWvG4mi6XVNFUEhQ@mail.gmail.com>
2014-01-23 17:02                 ` Eric Le Bihan
2014-01-24 18:27                   ` Eric Le Bihan [this message]
2014-01-26 14:19                     ` sambuff
2014-01-28  8:42                       ` Eric Le Bihan

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

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

  git send-email \
    --in-reply-to=20140124182659.GB30974@pc-eric \
    --to=eric.le.bihan.dev@free.fr \
    --cc=buildroot@busybox.net \
    /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. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox