From: sambuff <samuel.buffet@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] python Gobject
Date: Mon, 20 Jan 2014 23:41:17 -0800 (PST) [thread overview]
Message-ID: <1390290077263-60414.post@n4.nabble.com> (raw)
In-Reply-To: <20140117154452.GC10730@pc-eric>
Hi Eric,
> Adding a new package for python-gobject 2.28 is pretty straightforward. I
>did it in my repo:
https://github.com/elebihan/buildroot/commit/4107b0e4549aa4a234496c840361528381f57edf.
Thanks for the link but I've failed to build it though.
I've tried your new package with br-2013.11but the build fails because of
"missing python headers"
see the last lines :
"checking for python version... 2.7
checking for python platform... linux2
checking for python script directory...
${prefix}/lib/python2.7/site-packages
checking for python extension module directory...
${exec_prefix}/lib/python2.7/site-packages
checking for python version... (cached) 2.7
checking for python platform... (cached) linux2
checking for python script directory... (cached)
${prefix}/lib/python2.7/site-packages
checking for python extension module directory... (cached)
${exec_prefix}/lib/python2.7/site-packages
checking for headers required to compile python extensions... not found
configure: error: could not find Python headers
make: ***
[/home/xxxxx/buildroot-2013.11/output/build/python-gobject-2.28.6/.stamp_configured]
Error 1"
I consider myself as "learning" how to use buildroot at the moment so I'm
may doing a mistake (but don't know where). If you had any advise that would
make my day.
Thanks for the good job.
Sam
--
View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/python-Gobject-tp60199p60414.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.
next prev parent reply other threads:[~2014-01-21 7:41 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 [this message]
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
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=1390290077263-60414.post@n4.nabble.com \
--to=samuel.buffet@gmail.com \
--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