From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: yocto@yoctoproject.org,
openembedded-devel@lists.openembedded.org,
openembedded-core@lists.openembedded.org
Subject: Re: [RFT] Moving on from eglibc to glibc 2.20
Date: Thu, 28 Aug 2014 22:35:27 +0100 [thread overview]
Message-ID: <1409261727.29296.144.camel@ted> (raw)
In-Reply-To: <20140828064051.GA13139@haswell>
On Wed, 2014-08-27 at 23:41 -0700, Khem Raj wrote:
> As we all know eglibc has been merged back into glibc and 2.19 was the
> last release, here I have put together the recipes for upcoming glibc
> 2.20 release and removed eglibc 2.19 in favor of move.
>
> I also thought about leaving eglibc in there but then eglibc and glibc
> were pretty much same as they always have been that it would be an
> incremental change with lot more patches this time.
>
> The tree is here
>
> http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/eglibc-to-glibc-2.20
>
> This has not recieved much testing yet and I am looking out for helping
> hands here, so try it out in your buid environments and machines of
> interest and report back on issues.
The one I've seen so far looks like a patch wasn't updated:
http://errors.yoctoproject.org/Errors/Search/Details/3783/3/10/1fc811ecd57be21ae6ab78e15204ffa76494c6b8
Cheers,
Richard
next prev parent reply other threads:[~2014-08-28 21:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 6:41 [RFT] Moving on from eglibc to glibc 2.20 Khem Raj
2014-08-28 7:18 ` Richard Purdie
2014-08-28 7:52 ` Khem Raj
2014-08-28 21:35 ` Richard Purdie [this message]
2014-08-29 0:40 ` Khem Raj
2014-08-28 22:51 ` Richard Purdie
2014-08-29 0:41 ` Khem Raj
2014-08-29 1:46 ` Khem Raj
2014-08-29 10:39 ` Richard Purdie
2014-08-30 0:01 ` Khem Raj
2014-08-30 2:56 ` Khem Raj
2014-08-29 12:18 ` Richard Purdie
2014-08-29 23:59 ` Khem Raj
2014-08-30 3:01 ` Khem Raj
2014-09-02 22:50 ` Dan McGregor
2014-08-29 12:20 ` Richard Purdie
2014-08-30 0:00 ` 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=1409261727.29296.144.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@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