We should extend:
./meta/recipes-devtools/valgrind/valgrind/glibc-2.20.patch

to allow building valgrind with glibc-2.21, currently it fails with:

| checking the GLIBC_VERSION version... unsupported version 2.21
| configure: error: Valgrind requires glibc version 2.2 - 2.19
| Configure failed. The contents of all config.log files follows to aid
debugging
| ERROR: oe_runconf failed


On Sun, Feb 15, 2015 at 10:59 PM, Richard Purdie <
richard.purdie@linuxfoundation.org> wrote:

> On Sat, 2015-02-14 at 10:06 +0000, Richard Purdie wrote:
> > Hi Khem,
> >
> > On Thu, 2015-02-12 at 15:35 +0800, Khem Raj wrote:
> > > I have refreshed the branch to include the patch which moves the src
> > > uri to use the newly released glibc 2.21 branch
> > > and please run it via autobuilder ( top 5 commits )
> >
> > Its running on the autobuilder at the moment. Errors will be reported to
> > the error reporting system and can be seen at:
> >
> >
> http://errors.yoctoproject.org/Errors/Search/?items=10&query=be29d13a847d458efaf542ed302e48050f67a655
> >
> > Right now, poky-tiny failed due to warning are errors and unused
> > symbols. Minnow failed due to SSE instruction issues. Full build logs
> > are also available on the autobuilder:
> >
> > https://autobuilder.yoctoproject.org/main/tgrid
> >
> > as ross/mut-next. We do have other changes in the branch but the above
> > are pretty clearly glibc.
> >
> > Other errors will go to the places above as the builds complete/fail.
>
> FWIW I tested the gcc upgrade without glibc and that seems ok so I've
> merged that whilst we work out the issues with glibc.
>
> Cheers,
>
> Richard
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>