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: [yocto] [RFT] upcoming glibc 2.21 and gcc 4.9 upgrade
Date: Sat, 21 Feb 2015 09:22:30 +0000 [thread overview]
Message-ID: <1424510550.11836.66.camel@linuxfoundation.org> (raw)
In-Reply-To: <1424455387.11836.57.camel@linuxfoundation.org>
On Fri, 2015-02-20 at 18:03 +0000, Richard Purdie wrote:
> On Mon, 2015-02-02 at 02:02 -0800, Khem Raj wrote:
> > I have put together upgrade to gcc 4.9.2 as well as glibc 2.21 (
> > upcoming ) on a contrib branch ( top 2 patches) its has not got much
> > testing besides x86 qemu thus far.
> >
> > http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/gcc-glibc-upgrade
> >
> > I would like to request some help in testing these out in your
> > respective environments and please report any issues you see so we can
> > start sorting them out at earlier and making its way into OE-Core.
> >
> > Thanks for your help
>
> For info, I've now merged the glibc part of this change now too.
>
> Khem: Thanks for the work on this!
New issue that caught my eye:
https://autobuilder.yoctoproject.org/main/builders/nightly-qa-logrotate/builds/204/steps/Running%20Sanity%20Tests/logs/stdio
segfault in init within libc :/.
Cheers,
Richard
next prev parent reply other threads:[~2015-02-21 9:22 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 10:02 [RFT] upcoming glibc 2.21 and gcc 4.9 upgrade Khem Raj
2015-02-02 10:40 ` [yocto] " Burton, Ross
2015-02-02 10:53 ` Khem Raj
2015-02-02 10:54 ` Khem Raj
2015-02-02 17:25 ` Burton, Ross
2015-02-02 17:40 ` Khem Raj
2015-02-02 17:50 ` Burton, Ross
2015-02-02 18:33 ` Khem Raj
2015-02-02 21:45 ` Burton, Ross
2015-02-03 5:03 ` Khem Raj
2015-02-03 11:55 ` Burton, Ross
2015-02-03 14:43 ` Dan McGregor
2015-02-12 7:35 ` Khem Raj
2015-02-14 7:53 ` Burton, Ross
2015-02-14 10:06 ` Richard Purdie
2015-02-14 13:08 ` Burton, Ross
2015-02-14 15:15 ` Dan McGregor
2015-02-15 21:59 ` Richard Purdie
2015-02-17 17:50 ` Martin Jansa
2015-02-17 19:02 ` [PATCH 1/2] valgrind: add glibc-2.21 to glibc.patch Martin Jansa
2015-02-17 19:02 ` [PATCH 2/2] license.bbclass: fix unexpected operator for LICENSE values with space Martin Jansa
2015-02-18 7:15 ` [yocto] [RFT] upcoming glibc 2.21 and gcc 4.9 upgrade Khem Raj
2015-02-18 7:46 ` Richard Purdie
2015-02-18 9:01 ` Khem Raj
2015-02-18 11:51 ` Richard Purdie
2015-02-18 13:06 ` Richard Purdie
2015-02-18 18:38 ` Khem Raj
2015-02-18 21:41 ` Richard Purdie
2015-02-19 0:23 ` Khem Raj
2015-02-19 0:28 ` Khem Raj
2015-02-19 0:31 ` Khem Raj
2015-02-19 3:36 ` Khem Raj
[not found] ` <54CFA8A5.7090504@mvista.com>
2015-02-02 17:26 ` Burton, Ross
2015-02-02 17:43 ` Khem Raj
2015-02-20 18:03 ` Richard Purdie
2015-02-21 0:27 ` Peter Urbanec
2015-02-24 6:34 ` Khem Raj
2015-02-21 9:22 ` Richard Purdie [this message]
2015-02-24 6:59 ` Khem Raj
2015-02-24 21:58 ` Khem Raj
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=1424510550.11836.66.camel@linuxfoundation.org \
--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