mailing list of musl libc
 help / color / mirror / code / Atom feed
From: u-igbb@aetey.se
To: musl@lists.openwall.com
Subject: Re: Compiling latest busybox with latest musl
Date: Sat, 9 Aug 2014 08:45:14 +0200	[thread overview]
Message-ID: <20140809064513.GQ10958@example.net> (raw)
In-Reply-To: <53E53368.3070107@decentral.ch>

Thanks for the hint Tim,

On Fri, Aug 08, 2014 at 10:30:32PM +0200, Tim Tassonis wrote:
> http://wiki.musl-libc.org/wiki/Building_Busybox
> 
> This put me off a bit, as I did not want to modify my kernel headers

The information there led me to delay moving busybox to musl.
Good that the unpatched kernel headers seem to play nicely along.

Rune



      parent reply	other threads:[~2014-08-09  6:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-08 20:30 Tim Tassonis
2014-08-08 20:51 ` Rich Felker
2014-08-08 21:12   ` Tim Tassonis
2014-08-08 21:15     ` Rich Felker
2014-08-09  6:45 ` u-igbb [this message]

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=20140809064513.GQ10958@example.net \
    --to=u-igbb@aetey.se \
    --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).