Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 14 Aug 2017 12:59:41 -0500
From: wdlkmpx <>
To: Denys Vlasenko <>
Cc: busybox <>, musl <>
Subject: Re: bbox: musl versus uclibc

I'm sure there was plenty of people willing to contribute  to uclibc,
there is even an updated fork.

The project has been badly managed.. thats the only reason i can think
of for this situation  to happen

On 8/14/17, Denys Vlasenko <> wrote:
> As uclibc is increasingly aging, I am finally forced
> to switch to musl: I'm bitten by a nasty bug in
> getopt() - hush is using it in a slightly unusual way,
> which uclibc does not expect.
> I built a toolchain using
> (Rich, is this the thing I should be using?)
> and it worked with no issues at all.
> (I can probably only wish for the README
> to also mention how to make this a _static_
> toolchain... I have a box with 32-bit userspace,
> would be awesome to be able to copy this fresh
> 64-bit toolchain to it and have it working).
> Then I built busybox. Impressions:
> Only a few options did not build:
> failed because they need GNU regexp extensions.
> because they need rpc/rpc.h.
> Not complaining, since them being in libc was a mistake
> in the first place.
> Now, the good news - musl has smaller data!
> 6695 bytes versus 7129 bytes for uclibc:
>    text  data   bss     dec    hex filename
>  894902   465  6664  902031  dc38f busybox.uclibc
>  912538   563  6132  919233  e06c1 busybox.musl
> Whee!
> _______________________________________________
> busybox mailing list

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.