From: Rich Felker <dalias@libc.org>
To: j-core@j-core.org, musl@lists.openwall.com
Subject: musl-cross-make can now install kernel headers
Date: Sat, 14 May 2016 01:40:28 -0400 [thread overview]
Message-ID: <20160514054028.GA21804@brightrain.aerifal.cx> (raw)
I've updated the musl-cross-make toolchain build system to support
fetching kernel sources and installing the kernel headers for the
target. This should make it easier to use the resulting toolchains
for building things like toybox, busybox, strace, etc. that need
kernel headers, and for using them with buildroot. As usual the repo
is here:
https://github.com/richfelker/musl-cross-make
The kernel header functionality can be suppressed by clearing the
LINUX_VER make variable, if desired.
The new version also installs a $(TARGET)-cc symlink for gcc, for
compatibility with software that only tries cc and not gcc.
Rich
next reply other threads:[~2016-05-14 5:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-14 5:40 Rich Felker [this message]
2016-05-17 0:25 ` Patrick Oppenlander
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=20160514054028.GA21804@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=j-core@j-core.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).