From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
openembeded-devel <Openembedded-devel@lists.openembedded.org>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [RFT] eglibc 2.19
Date: Wed, 12 Feb 2014 16:53:50 +0000 [thread overview]
Message-ID: <1392224030.14081.3.camel@ted> (raw)
In-Reply-To: <1392219682.14081.1.camel@ted>
On Wed, 2014-02-12 at 15:41 +0000, Richard Purdie wrote:
> On Sat, 2014-02-08 at 08:08 -0800, Khem Raj wrote:
> > Hi all
> >
> > I have staged a branch with eglibc 2.19 upgraded recipes here
> >
> > http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/eglibc-2.19
> >
> > These are not final recipes there may be tweaks needed like adjusting SRC_URI
> > later on.
> >
> > please help testing it out in your environments and machines
> > I would be happy to help out with issues we find
>
> The autobuilder is still going but it found:
>
> http://autobuilder.yoctoproject.org/main/builders/nightly-fsl-ppc/builds/25/steps/BuildImages/logs/stdio
the valgrind configure check breaks too:
http://autobuilder.yoctoproject.org/main/builders/minnow/builds/25/steps/BuildImages/logs/stdio
Cheers,
Richard
next prev parent reply other threads:[~2014-02-12 16:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-08 16:08 [RFT] eglibc 2.19 Khem Raj
2014-02-10 5:32 ` Nathan Rossi
2014-02-10 7:31 ` Khem Raj
2014-02-12 15:41 ` Richard Purdie
2014-02-12 16:53 ` Richard Purdie [this message]
2014-02-12 17:14 ` Khem Raj
2014-02-12 18:20 ` Khem Raj
2014-02-13 5:45 ` Khem Raj
2014-02-17 15:25 ` Richard Purdie
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=1392224030.14081.3.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=Openembedded-devel@lists.openembedded.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=yocto@yoctoproject.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