From: John Spencer <maillist-musl@barfooze.de>
To: musl@lists.openwall.com
Subject: Re: musl for ARM
Date: Tue, 02 Oct 2012 12:55:27 +0200 [thread overview]
Message-ID: <506AC81F.7090709@barfooze.de> (raw)
In-Reply-To: <CAPW=hRTK-vP9Nmk938PQvZzOUcFF0GFvOLqevMBwYxR4a=-+eA@mail.gmail.com>
On 10/02/2012 09:27 AM, Brian Wang wrote:
> Hello all,
>
> I am currently thinking of switching to musl from glibc for my target
> after some readings on musl.
> I would like some advice from musl experts:
> * Does it support gettext stuff?
musl has no libintl built-in, but i put together a replacement that is
capable of building all packages relying on the gettext tools:
https://github.com/rofl0r/gettext-tiny
at this point, all it does is echo the passed translation string back;
i.e. everything's english.
however you can compile gnu gettext just fine, if you want to spend 40+
min on its compilation.
> * Does it _boost_ the performance on a 400MHz arm926 device? Or it
> is just smaller?
> By _boost_, I mean if the user can actually feel the improvement
> in performance.
it will definitely boost shell performance, in that it has a far lower
syscall overhead on startup. configure scripts run up to 4x as fast.
also, memory usage will be much smaller. a booted up x86_64 sabotage
system takes ~2MB RAM, including kernel.
> I did try the musl cross project and successfully built a musl-based
> arm linux toolchain.
> My kernel (2.6.24) was built successfully (not tried it on my device yet).
> However, when building busybox, there are some header files clashes,
> resulting in conflicting types.
> An example of it:
> ---------------------
> In file included from
> /opt/cross/arm-linux-musleabi/lib/gcc/arm-linux-musleabi/4.7.1/../../../../arm-linux-musleabi/include/linux/kd.h:3:0,
> from console-tools/kbd_mode.c:23:
> /opt/cross/arm-linux-musleabi/lib/gcc/arm-linux-musleabi/4.7.1/../../../../arm-linux-musleabi/include/linux/types.h:12:26:
> error: conflicting types for ‘fd_set’
> In file included from
> /opt/cross/arm-linux-musleabi/lib/gcc/arm-linux-musleabi/4.7.1/../../../../arm-linux-musleabi/include/sys/time.h:9:0,
> from include/libbb.h:45,
> from console-tools/kbd_mode.c:22:
> /opt/cross/arm-linux-musleabi/lib/gcc/arm-linux-musleabi/4.7.1/../../../../arm-linux-musleabi/include/sys/select.h:25:3:
> note: previous declaration of ‘fd_set’ was here
> ---------------------
>
the problem here seems to be the inclusion of
linux/types.h, not GCC-related headers.
here's a busybox build recipe that's known to work with ARM (at least with kernel 3.0+ headers):
https://github.com/rofl0r/sabotage/blob/master/pkg/busybox
there's also a prebuilt armv7l rootfs available on that site, check README on the repo for info.
next prev parent reply other threads:[~2012-10-02 10:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 7:27 Brian Wang
2012-10-02 10:55 ` John Spencer [this message]
2012-10-02 16:05 ` Brian Wang
2012-10-02 13:48 ` Rich Felker
2012-10-02 16:18 ` Brian Wang
2012-10-02 17:45 ` Rich Felker
2012-10-02 16:39 ` Szabolcs Nagy
2012-10-02 17:46 ` Rich Felker
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=506AC81F.7090709@barfooze.de \
--to=maillist-musl@barfooze.de \
--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).