mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Waldemar Brodkorb <wbx@openadk.org>
To: musl@lists.openwall.com
Subject: Re: Re: bbox: musl versus uclibc
Date: Thu, 17 Aug 2017 06:29:16 +0200	[thread overview]
Message-ID: <20170817042916.GR28021@waldemar-brodkorb.de> (raw)
In-Reply-To: <CAKpSnpL+kPssr13SVEULepxoKerWkuVG0X=FM6XSYu758tzuHw@mail.gmail.com>

Hi,
Jorge Almeida wrote,

> On Wed, Aug 16, 2017 at 1:34 PM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
> 
> > On Mon, 14 Aug 2017 12:59:41 -0500, wdlkmpx wrote:
> >
> 
> >> The project has been badly managed.. thats the only reason i can think
> >
> > uClibc-ng is alive at https://uclibc-ng.org/. Regular releases
> > (actually more regular than musl in recent months!), updated web site,
> > responsive maintainer, lots of cleanup in the code base, and QA effort.
> >
> 
> I just visited the link you provided. I was curious to know whether to
> compile a program one still has to "make menuconfig", which IMO is
> fine for the linux kernel. So I clicked the "Documentation" link. It
> leads to an "Overview over different language related features".
> 
> What did I do wrong?

Nothing. I updated the page now.
A valid config is still required to build a uClibc-ng toolchain.
You can avoid this by just using Buildroot, Crosstool-ng or OpenADK,
which all have good uClibc-ng toolchain support.

best regards
 Waldemar


  reply	other threads:[~2017-08-17  4:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-14 17:43 Denys Vlasenko
2017-08-14 17:59 ` wdlkmpx
2017-08-16 12:34   ` Thomas Petazzoni
2017-08-16 12:57     ` Jorge Almeida
2017-08-17  4:29       ` Waldemar Brodkorb [this message]
2017-08-16 13:25     ` Denys Vlasenko
2017-08-16 13:36       ` Thomas Petazzoni
2017-08-17  4:35         ` [musl] " Waldemar Brodkorb
2017-08-14 18:18 ` Emmanuel Deloget
2017-08-14 18:48 ` Rich Felker
2017-08-14 22:13   ` Denys Vlasenko

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=20170817042916.GR28021@waldemar-brodkorb.de \
    --to=wbx@openadk.org \
    --cc=musl@lists.openwall.com \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).