From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] meta: glib-2.0: don't apply qsort_r test removable patch for native version
Date: Wed, 02 Nov 2011 09:08:48 +0000 [thread overview]
Message-ID: <1320224928.20107.18.camel@ted> (raw)
In-Reply-To: <1320185290-18117-1-git-send-email-morphis@gravedo.de>
On Tue, 2011-11-01 at 23:08 +0100, Simon Busch wrote:
> On some buildhosts with an older version of native glib-2.0 installed (in this case
> 2.16.6) the qsort_r test removable patch leads to a compilation error:
>
> | ./.libs/libglib-2.0.so: undefined reference to `qsort_r'
> | collect2: ld returned 1 exit status
>
> This patch fixes this so the patch gets only applied for the native version of this
> recipe.
>
> Signed-off-by: Simon Busch <morphis@gravedo.de>
> ---
> meta/recipes-core/glib-2.0/glib-2.0_2.30.0.bb | 7 +++++--
> 1 files changed, 5 insertions(+), 2 deletions(-)
Merged to master, thanks.
Richard
prev parent reply other threads:[~2011-11-02 9:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 22:08 [PATCH] meta: glib-2.0: don't apply qsort_r test removable patch for native version Simon Busch
2011-11-02 8:26 ` Martin Jansa
2011-11-02 9:08 ` Richard Purdie [this message]
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=1320224928.20107.18.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