Re: [PATCH 0/4] uclibc and related fixes

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Wed, 2011-06-22 at 08:57 -0700, Khem Raj wrote:
> On 06/22/2011 08:42 AM, Richard Purdie wrote:
> > On Tue, 2011-06-21 at 18:44 -0700, Khem Raj wrote:
> >> Fix uclibc build for x86_64
> >> gettext compile failed on uclibc so fix it and additionally
> >> remove unused patches
> >> Add required support for systemd to function with uclibc
> >> Quash a parse warning where uclibc-initial and uclibc
> >> both provided libsegfault
> >>
> >> The following changes since commit 78de64f58b98101f5be5778e9ecbdaae5ba32997:
> >>
> >>    binutils_2.21.bb: Fix ld segfault exposed by eglibc 2.14 on x86_64 (2011-06-21 17:58:06 -0700)
> >>
> >> are available in the git repository at:
> >>    git://git.openembedded.org/openembedded-core-contrib kraj/uclibc
> >>    http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=kraj/uclibc
> >>
> >> Khem Raj (4):
> >>    uclibc.inc: libsegfault is only RPROVIDED by uclibc
> >>    gettext-0.18.1.1: Remove unused patches
> >>    uclibc/x86_64/uClibc.machine: Enable ARCH_USE_MMU
> >>    uclibc: Add support for $ORIGIN
> >
> > Merged to master, thanks.
> >
> > I had reservations about the first one as hardcoding PN can have issues
> > with BBCLASSEXTEND but looking at the recipe, there are bigger issues if
> > we were ever to do that :/
> >
> 
> in attached patch I moved it to uclibc recipe is that better ?

Its better, yes and its what I was going to suggest until I realised
there were other issues that BBCLASSEXTEND would have with the recipe.
Its certainly something to keep in mind in the future...

Cheers,

Richard