mailing list of musl libc
 help / color / mirror / code / Atom feed
* Patching kernel headers?
@ 2015-03-11 15:33 Peter Smith
  2015-03-11 16:14 ` Szabolcs Nagy
  0 siblings, 1 reply; 3+ messages in thread
From: Peter Smith @ 2015-03-11 15:33 UTC (permalink / raw)
  To: musl

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?



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Patching kernel headers?
  2015-03-11 15:33 Patching kernel headers? Peter Smith
@ 2015-03-11 16:14 ` Szabolcs Nagy
  2015-03-14  3:33   ` Peter Smith
  0 siblings, 1 reply; 3+ messages in thread
From: Szabolcs Nagy @ 2015-03-11 16:14 UTC (permalink / raw)
  To: musl

* 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)


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Patching kernel headers?
  2015-03-11 16:14 ` Szabolcs Nagy
@ 2015-03-14  3:33   ` Peter Smith
  0 siblings, 0 replies; 3+ messages in thread
From: Peter Smith @ 2015-03-14  3:33 UTC (permalink / raw)
  To: musl

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?



^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2015-03-14  3:33 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-03-11 15:33 Patching kernel headers? Peter Smith
2015-03-11 16:14 ` Szabolcs Nagy
2015-03-14  3:33   ` Peter Smith

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).