[OE-core] What is the strategy to update eglibc?

[Ni Qingliang]

Thanks for the explanation:)

On Thu, 2011-11-17 at 14:41 +0800, Khem Raj wrote:
> On Wed, Nov 16, 2011 at 6:35 PM, Ni Qingliang
> <niqingliang at insigma.com.cn> wrote:
> > it looks like there is 2.14 bb file already, why the default eglibc stay
> > on 2.13?
> 
> 2.14 removed some functionality rpc which is used extensively
> alternative to use libtirpc is not sufficient atm. Therefore we
> readded the functionality into 2.14 recipes and they need testing.
> Some distros e.g. angstrom-bleeding use 2.14 but its not default in
> oe-core yet for same reasons that it needs to be
> tested
> 
> >
> > On Thu, 2011-11-17 at 10:32 +0800, Kang Kai wrote:
> >> On 2011年11月17日 05:38, Khem Raj wrote:
> >> > On Sun, Oct 30, 2011 at 7:12 PM, Kang Kai<Kai.Kang at windriver.com>  wrote:
> >> >> Hi Saul,
> >> >>
> >> >> I just want to update eglibc but eglibc is using its 2.14 branch and use svn
> >> >> commit revision "15225" as current version. Of course it is behind the
> >> >> latest svn revision, but I don't quit sure about which is the right revision
> >> >> to update eglibc.
> >>
> >> Hi Khem,
> >> > since release branches of eglibc only get bug fixes in ideal case it
> >> > should be good at any revision. However if we have bug
> >> > fixes that dont affect us immediately we do not tend to update
> >> > the revision. If you find that some bug fix thats applied upstream is
> >> > needed it certainly can be a reason to bump up srcrev given we do some
> >> > level of build and runtime testing
> >> > with new revision.
> >>
> >> Thanks very much for your detailed explanation.
> >> I check the changelog of eglibc 2.13 branch(latest is 15508), and they
> >> are some tiny updates except the revision 15226 that is same with
> >> current patch
> >>
> >> glibc_bug_fix_12454.patch
> >>
> >> And I made the rough tests of image-sato of qemu-x86 and qemu-arm and
> >> results are fine.
> >>
> >> Regards,
> >> Kai
> >> >
> >> >> Could you give me some guide? Thank you!
> >> >>
> >> >> Regards,
> >> >> Kai
> >> >>
> >> >> _______________________________________________
> >> >> Openembedded-core mailing list
> >> >> Openembedded-core at lists.openembedded.org
> >> >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
> >> >>
> >> > _______________________________________________
> >> > Openembedded-core mailing list
> >> > Openembedded-core at lists.openembedded.org
> >> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
> >>
> >>
> >> _______________________________________________
> >> Openembedded-core mailing list
> >> Openembedded-core at lists.openembedded.org
> >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
> >
> > --
> > Yi Qingliang
> > niqingliang at insigma.com.cn
> > https://niqingliang2003.wordpress.com
> >
> >
> > _______________________________________________
> > Openembedded-core mailing list
> > Openembedded-core at lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
> >

-- 
Yi Qingliang
niqingliang at insigma.com.cn
https://niqingliang2003.wordpress.com