mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Peter Smith <aic0azee@openmailbox.org>
To: musl@lists.openwall.com
Subject: Re: Patching kernel headers?
Date: Sat, 14 Mar 2015 04:33:12 +0100	[thread overview]
Message-ID: <4ec529702be11fefd204b3056086af86@openmailbox.org> (raw)
In-Reply-To: <20150311161434.GP16260@port70.net>

On 2015-03-11 17:14, Szabolcs Nagy wrote:
> * Peter Smith <aic0azee@openmailbox.org> [2015-03-11 16:33:54 +0100]:
>> I have built a toolchain with GCC 4.7.3, musl 1.1.6 and Linux 3.12 
>> kernel
>> headers. I then tried to compile Busybox 1.23.1 without patching the
>> toolchain kernel headers, as described here:
>> http://wiki.musl-libc.org/wiki/Building_Busybox and the build was 
>> still
>> successful.
>> 
>> Does this mean that patching the kernel headers is no longer 
>> necessary?
> 
> did you use an allyes busybox config?
> 
> only some of the tools use conflicting headers
> 
> (some kernel headers are incompatible with libc headers
> busybox might got fixed not to include those but other
> code may still need the patched kernel headers)

I have now investigated further, and both the current and previous 
version of Busybox will build without patching the kernel headers, when 
using my custom Busybox config. If I try to build Busybox with an allyes 
config it will fail. Nothing has changed, I have just found out that my 
specific Busybox config will work without patching the kernel headers.

Are there any reasons for me to patch the kernel headers now that I 
found out Busybox will build anyway? Could other applications require 
the headers to be patched?



      reply	other threads:[~2015-03-14  3:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-11 15:33 Peter Smith
2015-03-11 16:14 ` Szabolcs Nagy
2015-03-14  3:33   ` Peter Smith [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=4ec529702be11fefd204b3056086af86@openmailbox.org \
    --to=aic0azee@openmailbox.org \
    --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).