From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] eglibc: ensure that NSS libs go into the right package when ${base_libdir} and ${libdir} are the same
Date: Wed, 13 Jul 2011 12:26:26 +0100 [thread overview]
Message-ID: <1310556386.2378.6.camel@phil-desktop> (raw)
In-Reply-To: <6FD8E09E-1FDA-4CB6-84B0-085F878F0214@dominion.thruhere.net>
On Wed, 2011-07-13 at 13:13 +0200, Koen Kooi wrote:
> Op 13 jul 2011, om 13:08 heeft Richard Purdie het volgende geschreven:
>
> > On Wed, 2011-07-13 at 10:03 +0100, Phil Blundell wrote:
> >> Previously, libnss_hesiod et al. could get swallowed by the wildcarded glob in ${PN}-dev.
> >> Fix it by moving eglibc-extra-nss earlier in the PACKAGES and adjusting its FILES to ensure
> >> that the devel symlinks don't get caught.
> >>
> >> Signed-off-by: Phil Blundell <philb@gnu.org>
> >> ---
> >> meta/recipes-core/eglibc/eglibc-package.inc | 4 ++--
> >> meta/recipes-core/eglibc/eglibc_2.13.bb | 2 +-
> >> 2 files changed, 3 insertions(+), 3 deletions(-)
> >
> > Merged to master, thanks.
>
> That is missing a PR bump for eglibc 2.12
Oh yeah. Do we really need to keep 2.12 around still?
I also wonder if glibc 2.10 could/should be deleted now. That recipe
probably has a lot of the same issues that we've been fixing in eglibc
recently and it seems a bit of a waste of time to keep beating away at a
package that's four major versions out of date.
p.
next prev parent reply other threads:[~2011-07-13 11:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 9:03 [PATCH] eglibc: ensure that NSS libs go into the right package when ${base_libdir} and ${libdir} are the same Phil Blundell
2011-07-13 11:08 ` Richard Purdie
2011-07-13 11:13 ` Koen Kooi
2011-07-13 11:26 ` Phil Blundell [this message]
2011-07-13 13:14 ` Koen Kooi
2011-07-14 14:16 ` Richard Purdie
2011-07-14 14:25 ` Phil Blundell
2011-07-14 19:47 ` Khem Raj
2011-07-14 15:32 ` Koen Kooi
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=1310556386.2378.6.camel@phil-desktop \
--to=philb@gnu.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