mailing list of musl libc
 help / color / mirror / code / Atom feed
From: John Spencer <maillist-musl@barfooze.de>
To: musl@lists.openwall.com
Cc: Laurent Bercot <ska-dietlibc@skarnet.org>
Subject: Re: linux/netlink.h
Date: Mon, 07 Oct 2013 14:06:21 +0200	[thread overview]
Message-ID: <5252A3BD.2070409@barfooze.de> (raw)
In-Reply-To: <52529004.6000406@skarnet.org>

On 10/07/2013 12:42 PM, Laurent Bercot wrote:
>
> Hi Luca,
>
>> Your distribution doesn't provide the whole set of linux headers
>> stand-alone?
>
> I can compile my software on top of an existing distribution all
> right. But the point is I'm building my own systems by hand without
> a distribution, which is precisely why I'm interested in musl. And
> it looks like mini-lkh was made for that precise case.
>

the mini-lkh's are really mini... currently they're barely enough to 
compile a small subset of busybox.

until they become more sophisticated, you can use sabotage's multi-arch
kernel headers tarball:

http://ftp.barfooze.de/pub/sabotage/tarballs/kernel-headers-3.3.4-1.tar.gz

imo a good alternative to downloading the full kernel sources to compile 
the headers.
an additional advantage is that kernel headers are often broken,
the version used by sabotage is known good.


  reply	other threads:[~2013-10-07 12:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-07  0:16 linux/netlink.h Laurent Bercot
2013-10-07  1:13 ` linux/netlink.h Luca Barbato
2013-10-07 10:42   ` linux/netlink.h Laurent Bercot
2013-10-07 12:06     ` John Spencer [this message]
2013-10-07 14:26       ` linux/netlink.h Laurent Bercot
2013-10-07 15:07       ` linux/netlink.h Christian Wiese
2013-10-07 16:08         ` linux/netlink.h John Spencer
2013-10-12 17:44       ` linux/netlink.h Justin Cormack
2013-10-13  3:37         ` linux/netlink.h John Spencer

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=5252A3BD.2070409@barfooze.de \
    --to=maillist-musl@barfooze.de \
    --cc=musl@lists.openwall.com \
    --cc=ska-dietlibc@skarnet.org \
    /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).