Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] glib-2.0: revert one commit in target recipe
Date: Wed, 18 Jul 2012 22:25:59 +0100	[thread overview]
Message-ID: <1342646759.513.54.camel@ted> (raw)
In-Reply-To: <1342603039-6608-1-git-send-email-Martin.Jansa@gmail.com>

On Wed, 2012-07-18 at 11:17 +0200, Martin Jansa wrote:
> * it was causing staged python to be used as shebang
> 
> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> ---
>  ...-the-same-Python-as-we-found-in-configure.patch |   39 ++++++++++++++++++++
>  meta/recipes-core/glib-2.0/glib-2.0_2.32.4.bb      |    5 ++-
>  2 files changed, 42 insertions(+), 2 deletions(-)
>  create mode 100644 meta/recipes-core/glib-2.0/glib-2.0/0001-Revert-Use-the-same-Python-as-we-found-in-configure.patch

I've applied a different patch using sed to address the problem. I've
consolidated all the other code doing this and also fixed the nativesdk
case which this version potentially doesn't.

Cheers,

Richard




  reply	other threads:[~2012-07-18 21:37 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
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 [this message]
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=1342646759.513.54.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.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