From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/2040 Path: news.gmane.org!not-for-mail From: John Spencer Newsgroups: gmane.linux.lib.musl.general Subject: Re: musl for ARM Date: Tue, 02 Oct 2012 12:55:27 +0200 Message-ID: <506AC81F.7090709@barfooze.de> References: Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1349174840 8821 80.91.229.3 (2 Oct 2012 10:47:20 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 2 Oct 2012 10:47:20 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-2041-gllmg-musl=m.gmane.org@lists.openwall.com Tue Oct 02 12:47:25 2012 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1TJ00E-0006QU-Rp for gllmg-musl@plane.gmane.org; Tue, 02 Oct 2012 12:47:02 +0200 Original-Received: (qmail 20012 invoked by uid 550); 2 Oct 2012 10:46:56 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 20003 invoked from network); 2 Oct 2012 10:46:56 -0000 User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.14) Gecko/20110221 SUSE/3.1.8 Mail/1.0 In-Reply-To: Xref: news.gmane.org gmane.linux.lib.musl.general:2040 Archived-At: 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.