[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140808205143.GR1674@brightrain.aerifal.cx>
Date: Fri, 8 Aug 2014 16:51:43 -0400
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Re: Compiling latest busybox with latest musl
On Fri, Aug 08, 2014 at 10:30:32PM +0200, Tim Tassonis wrote:
> Hi
>
> Firstly, thanks for musl. I chose it to create fully-working statically
> linked binaries for a system without any glibc stuff on it and did not
> want to create a whole toolchain first, as required with uClibc.
>
> When I wanted to create s statically linked busybox (1.22.1), I looked
> in the wiki and found the page:
>
> http://wiki.musl-libc.org/wiki/Building_Busybox
>
>
> This put me off a bit, as I did not want to modify my kernel headers
> just to compile a static busybox.
In order to compile Busybox (at least the applets that need kernel
headers), you have to have a copy of the kernel headers in your musl
include path anyway; if the host system is glibc-based, /usr/include
will not be used. So this isn't as big a burden as it sounds like.
You're not modifying "your kernel headers" but just the copy installed
with musl. This does not need root.
Rich
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.
