From: wdlkmpx <wdlkmpx@gmail.com>
To: Denys Vlasenko <vda.linux@googlemail.com>
Cc: busybox <busybox@busybox.net>, musl <musl@lists.openwall.com>
Subject: Re: bbox: musl versus uclibc
Date: Mon, 14 Aug 2017 12:59:41 -0500 [thread overview]
Message-ID: <CADm8ZdUcR3qGjHBNnWP6uXONmCDbfzw7fQDTog5QHUsdxsSZUQ@mail.gmail.com> (raw)
In-Reply-To: <CAK1hOcOiWhBQYrH1VRs6coeQ+9aKtTnbwme9wiNkMboRv6dEgA@mail.gmail.com>
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 <vda.linux@googlemail.com> 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
> https://github.com/richfelker/musl-cross-make
> (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:
> EXTRA_COMPAT and FEATURE_VI_REGEX_SEARCH
> failed because they need GNU regexp extensions.
> FEATURE_MOUNT_NFS and FEATURE_INETD_RPC do not build
> 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
> busybox@busybox.net
> http://lists.busybox.net/mailman/listinfo/busybox
>
next prev parent reply other threads:[~2017-08-14 17:59 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 [this message]
2017-08-16 12:34 ` Thomas Petazzoni
2017-08-16 12:57 ` Jorge Almeida
2017-08-17 4:29 ` Waldemar Brodkorb
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=CADm8ZdUcR3qGjHBNnWP6uXONmCDbfzw7fQDTog5QHUsdxsSZUQ@mail.gmail.com \
--to=wdlkmpx@gmail.com \
--cc=busybox@busybox.net \
--cc=musl@lists.openwall.com \
--cc=vda.linux@googlemail.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).