From: Martin Jansa <martin.jansa@gmail.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/2] glib-2.0: Don't check function "qsort_r" in configure.ac
Date: Mon, 6 Feb 2012 08:05:14 +0100 [thread overview]
Message-ID: <20120206070513.GC3872@jama.jama.net> (raw)
In-Reply-To: <cover.1328509284.git.xiaofeng.yan@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 2141 bytes --]
On Mon, Feb 06, 2012 at 02:41:09PM +0800, Xiaofeng Yan wrote:
> From: Xiaofeng Yan <xiaofeng.yan@windriver.com>
>
> The function "g_qsort_with_data" has two kinds of realization. One calls qsort_r
> from libglib, the other realize itself. the realization method is controlled by macro "HAVE_QSORT_R".
> qsort_r from libglib cause sort error. Add no-check-qsort_r.patch for fixing this problem.
> This patch is to fix bug 1959. After this patch is merged into OE-core I will open a new bug to
> track the reason why qsort_r report normally. For finishing lsb test in YOCTO 1.2 M3 this patch
> is applied temporarily.
>
> Pull URL: git://git.pokylinux.org/poky-contrib.git
> Branch: xiaofeng/1959
> Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=xiaofeng/1959
>
> Thanks,
> Xiaofeng Yan <xiaofeng.yan@windriver.com>
> ---
no-check-qsort_r.patch is the same as remove.test.for.qsort_r.patch from
http://git.openembedded.org/openembedded-core/commit/?id=74f43e3b269c01dba7cd5215a8e825229bd5ecff
which was later removed from glib-2.0-native in
http://git.openembedded.org/openembedded-core/commit/?id=37579d7d74d127c90c1e078d05c5bf4ba0b3f755
and later removed completely in
http://git.openembedded.org/openembedded-core/commit/?id=812342e44e9e361a0fa93cfcfe65cf4dd6f2fb57
Are you sure this patch is right fix? And no need to split adding patch
itself and adding it to SRC_URI to 2 patches.
Cheers,
>
>
> Xiaofeng Yan (2):
> glib-2.0: Don't check function qsort_r
> glib-2.0: Add patch "no-check-qsort_r.patch"
>
> .../glib-2.0/glib-2.0/no-check-qsort_r.patch | 61 ++++++++++++++++++++
> meta/recipes-core/glib-2.0/glib-2.0_2.30.2.bb | 3 +-
> 2 files changed, 63 insertions(+), 1 deletions(-)
> create mode 100644 meta/recipes-core/glib-2.0/glib-2.0/no-check-qsort_r.patch
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2012-02-06 7:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 6:41 [PATCH 0/2] glib-2.0: Don't check function "qsort_r" in configure.ac Xiaofeng Yan
2012-02-06 6:41 ` [PATCH 1/2] glib-2.0: Don't check function qsort_r Xiaofeng Yan
2012-02-06 9:13 ` Phil Blundell
2012-02-06 15:34 ` Khem Raj
2012-02-06 19:13 ` Peter Tworek
2012-02-06 22:54 ` Khem Raj
2012-02-06 6:41 ` [PATCH 2/2] glib-2.0: Add patch "no-check-qsort_r.patch" Xiaofeng Yan
2012-02-06 15:33 ` Khem Raj
2012-02-07 5:40 ` Xiaofeng Yan
2012-02-06 7:05 ` Martin Jansa [this message]
2012-02-06 7:37 ` [PATCH 0/2] glib-2.0: Don't check function "qsort_r" in configure.ac Xiaofeng Yan
2012-02-06 9:16 ` Xiaofeng Yan
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=20120206070513.GC3872@jama.jama.net \
--to=martin.jansa@gmail.com \
--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 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.