From: Richard Purdie <richard.purdie@linuxfoundation.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: Thu, 14 Jul 2011 15:16:54 +0100 [thread overview]
Message-ID: <1310653014.20015.1162.camel@rex> (raw)
In-Reply-To: <DA356529-F7C2-4402-B058-6537D1272BCD@dominion.thruhere.net>
On Wed, 2011-07-13 at 15:14 +0200, Koen Kooi wrote:
> Op 13 jul 2011, om 13:26 heeft Phil Blundell het volgende geschreven:
>
> > 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?
>
> It's the default for angstrom, dunno if that's a good enough reason :)
Does Angstrom have any plans to switch to 2.13?
Certainly we're not aware of issues with 2.13 and as such we should
really consider phasing out 2.12 from OE-Core at least...
Cheers,
Richard
next prev parent reply other threads:[~2011-07-14 14:21 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
2011-07-13 13:14 ` Koen Kooi
2011-07-14 14:16 ` Richard Purdie [this message]
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=1310653014.20015.1162.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