From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: eglib is dead?
Date: Thu, 19 Jun 2014 20:33:25 -0500 [thread overview]
Message-ID: <53A38F65.4060005@windriver.com> (raw)
In-Reply-To: <12874293.qmlQjDjeXe@yiqingliang-pc>
On 6/19/14, 7:35 PM, Yi Qingliang wrote:
> Hello,
>
> this morning I have seen that:
> http://www.phoronix.com/scan.php?page=news_item&px=MTcyNDY
>
> it said that the "eglibc" is a "dead project", and most feature had
> been merged into "glibc" at version 2.19.
>
> so maybe we should drop "eglibc", and switch back to "glibc"?
eglibc and glibc have been in sync since the beginning. The only remaining
difference between glibc and eglibc is the configurable libc interface.
(Ability to change the configuration.) Last time we discussed this, we were
still trying to determine if we (OE) were going to try to keep that
configuration active, or if were were going to go to a different libc for 'tiny'
systems.
I don't believe a final decision has been made, but one way or another we will
be moving to 'glibc' in the future.
My understanding is that eglibc 2.19 is still 'alive' and maintained, but will
be the last version.
--Mark
> Yi Qingliang
> 20140620
>
prev parent reply other threads:[~2014-06-20 1:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 0:35 eglib is dead? Yi Qingliang
2014-06-20 1:33 ` Mark Hatle [this message]
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=53A38F65.4060005@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.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