mailing list of musl libc
 help / color / mirror / code / Atom feed
* Query about current practice of installing linux kernel header files
@ 2017-01-06 12:38 vlse
  2017-01-06 13:25 ` Szabolcs Nagy
  0 siblings, 1 reply; 3+ messages in thread
From: vlse @ 2017-01-06 12:38 UTC (permalink / raw)
  To: musl

I have a query regarding installation of Linux kernel header files for use with musl while compiling programs requiring it. I studied musl-cross-make source files. From it I found that it applies the linux kernel patch "0001-archscripts.diff" to linux source. And basically it does the following:

1) $(MAKE) ARCH=$(LINUX_ARCH) O=somedir INSTALL_HDR_PATH=somedir/staged headers_install
2) find somedir/staged/include '(' -name .install -o -name ..install.cmd ')' -exec rm {} +
3) cp -R somedir/staged/include/* $(DESTDIR)$(OUTPUT)$(SYSROOT)/include

Is this correct?
Does it means we can use plain vanilla kernel source and install headers from it?
That is musl specific adaptation of Linux kernel sources & headers has been upstreamed.
No more any need of sabotage adapted linux kernel headers.
Please correct me.

vlse,

Veera


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

* Re: Query about current practice of installing linux kernel header files
  2017-01-06 12:38 Query about current practice of installing linux kernel header files vlse
@ 2017-01-06 13:25 ` Szabolcs Nagy
  0 siblings, 0 replies; 3+ messages in thread
From: Szabolcs Nagy @ 2017-01-06 13:25 UTC (permalink / raw)
  To: musl

* vlse <vlse@veera.biz> [2017-01-06 18:08:39 +0530]:
> I have a query regarding installation of Linux kernel header files for use with musl while compiling programs requiring it. I studied musl-cross-make source files. From it I found that it applies the linux kernel patch "0001-archscripts.diff" to linux source. And basically it does the following:
> 
> 1) $(MAKE) ARCH=$(LINUX_ARCH) O=somedir INSTALL_HDR_PATH=somedir/staged headers_install
> 2) find somedir/staged/include '(' -name .install -o -name ..install.cmd ')' -exec rm {} +
> 3) cp -R somedir/staged/include/* $(DESTDIR)$(OUTPUT)$(SYSROOT)/include
> 
> Is this correct?

i think this is not musl specific, but the linux kernel way
to install uapi (there are collisions with libc headers
so you need staging and copy to the destination in the right
order with respect to libc header install)

> Does it means we can use plain vanilla kernel source and install headers from it?

yes.

> That is musl specific adaptation of Linux kernel sources & headers has been upstreamed.
> No more any need of sabotage adapted linux kernel headers.
> Please correct me.

no, musl specific fixes are not upstreamed yet
but this only affects code that includes certain
linux headers as well as libc headers in the same
source files.


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

* Re: Query about current practice of installing linux kernel header files
@ 2017-01-06 14:41 vlse
  0 siblings, 0 replies; 3+ messages in thread
From: vlse @ 2017-01-06 14:41 UTC (permalink / raw)
  To: musl

Sorry, I didn't received mail from Szabolcs Nagy to my inbox.

I am unable to understand the Makefile fully.

May you please correct me on this:

1) First musl include headers files are installed.
2) Then linux kernel header files are copied over.

Is this correct?

What about building busybox with musl-libc?
It needed few adapted headers of linux kernel as well as musl libc ones?

Veera
vlse
http://www.veera.biz


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

end of thread, other threads:[~2017-01-06 14:41 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-01-06 12:38 Query about current practice of installing linux kernel header files vlse
2017-01-06 13:25 ` Szabolcs Nagy
2017-01-06 14:41 vlse

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