From: Eric Le Bihan <eric.le.bihan.dev@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] python Gobject
Date: Thu, 23 Jan 2014 18:02:56 +0100 [thread overview]
Message-ID: <20140123170253.GB10856@pc-eric> (raw)
In-Reply-To: <CAGzWX_Jgdzctc_=-9XBg4Bw__KtdNwF3MChWvG4mi6XVNFUEhQ@mail.gmail.com>
On Thu, Jan 23, 2014 at 03:27:32PM +0100, Samuel Buffet wrote:
I poked my nose in your build/python-pygobject-2.28.6/config.log. The
configure script of pygobject complains about not having found Python headers
because it fails to compile a test program:
> configure:14934: checking for headers required to compile python extensions
> configure:14954: /home/toto/Documents/homeproject/buildroot/output/host/usr/bin/arm-buildroot-linux-uclibcgnueabi-cpp -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -I/home/toto/Documents/homeproject/buildroot/output/host/usr/include/python2.7 -I/home/toto/Documents/homeproject/buildroot/output/host/usr/include/python2.7 conftest.c
> In file included from /home/toto/Documents/homeproject/buildroot/output/host/usr/include/python2.7/Python.h:58:0,
> from conftest.c:26:
> /home/toto/Documents/homeproject/buildroot/output/host/usr/include/python2.7/pyport.h:849:2: error: #error "LONG_BIT definition appears wrong for platform (bad gcc/glibc config?)."
> [...]
> configure:14959: result: not found
> configure:14961: error: could not find Python headers
Are you building a 32-bit ARM guest on a 64-bit host machine?
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.
Best regards,
ELB
next prev parent reply other threads:[~2014-01-23 17:02 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 [this message]
2014-01-24 18:27 ` Eric Le Bihan
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=20140123170253.GB10856@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.