From: Colin Walters <walters@verbum.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: "Purdie, Richard" <richard.purdie@intel.com>,
"yocto-builds@yoctoproject.org" <yocto-builds@yoctoproject.org>,
Eggleton <paul.eggleton@linux.intel.com>,
oe-core layer' <openembedded-core@lists.openembedded.org>,
Paul, 'Patches
Subject: Re: Glib-2.0 cross-compile issue Was: Master Failures
Date: Tue, 17 Jul 2012 21:01:40 -0400 [thread overview]
Message-ID: <1342573300.2860.16.camel@lenny> (raw)
In-Reply-To: <20120718005221.GG22569@jama.jama.net>
On Wed, 2012-07-18 at 02:52 +0200, Martin Jansa wrote:
> It's probably caused by this
> http://permalink.gmane.org/gmane.comp.gnome.svn/604029
>
> which isn't very cross-compile friendly.. maybe we can just add patch
> reverting this change in 2.32.4?
I don't think it's a good idea to look at this module by module. A
*lot* of code out there uses AM_PATH_PYTHON, and then does something
with the resulting value of @PYTHON@. We should figure out the correct
thing to do that fixes all of:
0) "Normal" self-hosting build where /usr/bin/python = python2, and
we can use both /usr/bin/env python or /usr/bin/python
1) OE-core cross compilation
2) Ubuntu's situation of /usr/bin/python = python 3, and we want
to use /usr/bin/python2
Reverting the patch is going to break 2).
next prev parent reply other threads:[~2012-07-18 1:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 21:58 Master Failures Saul Wold
2012-07-18 0:26 ` Saul Wold
2012-07-18 0:38 ` Martin Jansa
2012-07-18 0:52 ` Glib-2.0 cross-compile issue Was: " Martin Jansa
2012-07-18 0:57 ` Saul Wold
2012-07-18 1:01 ` Colin Walters [this message]
2012-07-18 1:05 ` Martin Jansa
2012-07-18 9:17 ` [PATCH] glib-2.0: revert one commit in target recipe Martin Jansa
2012-07-18 21:25 ` Richard Purdie
2012-07-18 9:25 ` Master Failures Paul Eggleton
2012-07-18 9:36 ` Burton, Ross
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=1342573300.2860.16.camel@lenny \
--to=walters@verbum.org \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
--cc=richard.purdie@intel.com \
--cc=yocto-builds@yoctoproject.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox