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 1/1] libc-locale: split locale handling from libc recipe.
Date: Tue, 28 Jun 2011 15:00:41 +0100	[thread overview]
Message-ID: <1309269641.20015.296.camel@rex> (raw)
In-Reply-To: <15DA3F00-905F-4370-85D5-5038CD5D9ED2@dominion.thruhere.net>

On Tue, 2011-06-28 at 14:17 +0200, Koen Kooi wrote:
> Op 28 jun 2011, om 13:07 heeft Richard Purdie het volgende geschreven:
> > On Tue, 2011-06-28 at 10:07 +0100, Phil Blundell wrote:

> > 
> > Dongxiao: What Phil is referring to here is that libsotruss${PKGSUFFIX}
> > disappeared from PACKAGES and that also "${libdir}/audit/.debug"
> > disappeared from FILES_${PN}-dbg.
> > 
> > Specifically these changes came in as part of:
> > 
> > http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=77c2dd944db42e40cc8467e6bc5a175fed90c251
> > 
> > which I don't think your patch accounted for.
> > 
> > Since this patch has been around for a while and it otherwise looks
> > good, I've fixed up these couple of issues and merged it though.
> 
> This breaks when using eglibc 2.12 :(

Sorry, I've pushed some cleanup to resolve that.

Cheers,

Richard




  reply	other threads:[~2011-06-28 14:17 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-27  8:37 [PATCH 0/1 v3][PULL] libc locale split Dongxiao Xu
2011-06-27  8:37 ` [PATCH 1/1] libc-locale: split locale handling from libc recipe Dongxiao Xu
2011-06-27  8:58   ` Phil Blundell
2011-06-28  0:51     ` Xu, Dongxiao
2011-06-28  9:07       ` Phil Blundell
2011-06-28 11:07         ` Richard Purdie
2011-06-28 12:17           ` Koen Kooi
2011-06-28 14:00             ` Richard Purdie [this message]
2011-06-28 19:37               ` Koen Kooi
2011-06-28 20:15                 ` Koen Kooi
2011-06-28  4:12     ` Xu, Dongxiao
2011-07-08 14:55   ` Phil Blundell
  -- strict thread matches above, loose matches on Subject: below --
2011-06-22  9:01 [PATCH 0/1 v2][PULL] libc locale split Dongxiao Xu
2011-06-22  9:01 ` [PATCH 1/1] libc-locale: split locale handling from libc recipe Dongxiao Xu
2011-06-22 11:44   ` Phil Blundell
2011-06-23  4:08     ` Xu, Dongxiao
2011-06-23  9:40       ` Phil Blundell
2011-06-23 10:14         ` Richard Purdie
2011-06-23 23:42           ` Khem Raj
2011-06-27  5:49             ` Xu, Dongxiao
2011-06-22 14:44   ` Khem Raj
2011-06-22 14:47     ` Phil Blundell
2011-06-22 15:17       ` Mark Hatle
2011-06-22 15:43         ` Khem Raj
2011-06-08  9:08 [PATCH 0/1][RFC] libc locale split Dongxiao Xu
2011-06-08  9:08 ` [PATCH 1/1] libc-locale: split locale handling from libc recipe Dongxiao Xu
2011-06-08  9:36   ` Phil Blundell
2011-06-08 15:35     ` Richard Purdie
2011-06-09 11:14       ` Phil Blundell
2011-06-09 11:29         ` Richard Purdie
2011-06-09 11:43           ` Phil Blundell
2011-06-09 13:15             ` Richard Purdie
2011-06-09 13:51               ` Richard Purdie
2011-06-09 13:53               ` Koen Kooi
2011-06-09 13:55                 ` Phil Blundell

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=1309269641.20015.296.camel@rex \
    --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