mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: Query about current practice of installing linux kernel header files
Date: Fri, 6 Jan 2017 14:25:46 +0100	[thread overview]
Message-ID: <20170106132545.GC17692@port70.net> (raw)
In-Reply-To: <20170106123839.GA2527@localhost>

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


  reply	other threads:[~2017-01-06 13:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-06 12:38 vlse
2017-01-06 13:25 ` Szabolcs Nagy [this message]
2017-01-06 14:41 vlse

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=20170106132545.GC17692@port70.net \
    --to=nsz@port70.net \
    --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).