From: Denys Dmytriyenko <denis@denix.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
openembedded-architecture
<openembedded-architecture@lists.openembedded.org>,
openembeded-devel <Openembedded-devel@lists.openembedded.org>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [Openembedded-architecture] Glibc 2.24 _might_ require minimum kernel version 3.2
Date: Sun, 31 Jan 2016 13:18:23 -0500 [thread overview]
Message-ID: <20160131181823.GI1652@denix.org> (raw)
In-Reply-To: <CAMKF1sriCy0VxkkJHKsHaLy0K1N4Ns2E7o-rE_Lq8wSGXoy8hw@mail.gmail.com>
On Sun, Jan 31, 2016 at 09:41:17AM -0800, Khem Raj wrote:
> Hi
>
> This is FYI, as I have sent a RFT for glibc 2.24, there might be another change
> coming which is under discussion on glibc mailing lists which is on
> supported minimum
> kernel version bump to 3.2 since 2.6.32 will be EOLed this summer [1]
>
> If anyone is planning on using upcoming yocto/OE release and sticking
> to kernels older than 3.2 then please plan for upgrading your kernel.
>
> Thanks
> -Khem
>
> [1] - https://sourceware.org/ml/libc-alpha/2016-01/msg00885.html
What about our timeline - is glibc 2.24 planned for the next 2.1 release?
--
Denys
next prev parent reply other threads:[~2016-01-31 19:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-31 17:41 Glibc 2.24 _might_ require minimum kernel version 3.2 Khem Raj
2016-01-31 18:03 ` Phil Blundell
2016-01-31 18:18 ` Denys Dmytriyenko [this message]
2016-02-01 1:01 ` [Openembedded-architecture] " Khem Raj
2016-02-01 1:01 ` Khem Raj
2016-02-01 18:10 ` akuster
2016-02-01 18:24 ` [yocto] " Khem Raj
2016-02-01 18:24 ` 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=20160131181823.GI1652@denix.org \
--to=denis@denix.org \
--cc=Openembedded-devel@lists.openembedded.org \
--cc=openembedded-architecture@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.