From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] Is uClibc dead?
Date: Thu, 12 May 2016 17:00:10 +0100 [thread overview]
Message-ID: <5734A88A.9090309@imgtec.com> (raw)
In-Reply-To: <nh26a3$g4l$1@ger.gmane.org>
+CC Waldemar
On 12/05/16 16:08, Grant Edwards wrote:
> I recently decided to check to see what changes had been made to
> uClibc since the 4 year old version we're using in our product. So I
> went to https://uclibc.org.
>
> After jumping through hoops because all the SSL certificates are
> invalid/expired I see under latest news:
>
> 15 May 2012, uClibc 0.9.33.2 Released
>
> uClibc-0.9.33.2 was released today.
>
> Odd... no releases for four years?
>
> Is uClibc abandoned?
>
> I see that buildroot now uses uclibc-ng which, according Wikipedia, is
>
> "a spin-off of uClibc that regularly provides a stable and tested
> release, which is more suitable for different software development
> processes."
>
> So... processes different than what?
>
next prev parent reply other threads:[~2016-05-12 16:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 15:08 [Buildroot] Is uClibc dead? Grant Edwards
2016-05-12 16:00 ` Vicente Olivert Riera [this message]
2016-05-12 17:03 ` Waldemar Brodkorb
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=5734A88A.9090309@imgtec.com \
--to=vincent.riera@imgtec.com \
--cc=buildroot@busybox.net \
/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