On Wed, 2012-07-11 at 19:00 +0100, Paul Eggleton wrote: > On Wednesday 11 July 2012 17:55:18 McClintock Matthew-B29882 wrote: > > On Wed, Jul 11, 2012 at 6:00 AM, Richard Purdie > > <[email protected]> wrote: > > > On Wed, 2012-07-11 at 09:57 +0100, Jack Mitchell wrote: > > >> Are Khems eglibc patches going to make it in for this - 2.16 is playing > > >> havoc with my builds at the moment and surely will with everyone else > > >> when the major distros catch up. > > > > > > Its too late to get those pieces into 1.2.1, they're not even in master > > > yet, let alone in a stable release branch. > > > > > > I'm proposing we get 1.2.1 out, get the 2.16 pieces tested in master, > > > then port them to the denzil branch quickly post release so they'd make > > > any 1.2.2 release and are available on the git branch for people using > > > the stable branch. > > > > Can you fill me in? Why would a point release include such a dramatic > > upgrade? > > I think what we would be looking at would be just adding the fixes to allow > the > native packages to build against eglibc 2.16 so it can work on host distros > that use it, not bringing eglibc 2.16 itself in for the target.
Right, this would just be to allow edison to work on systems that have a native eglibc 2.16. I'm not convinced we have the patches worked out yet though. Target eglibc would remain with whatever is in edison (2.13?). Cheers, Richard _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
