From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Re: linux/vt.h
Date: Sat, 3 Oct 2015 14:00:15 -0400 [thread overview]
Message-ID: <20151003180015.GA8645@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAKpSnp+jJvxm0yHCQKndk8nDDSg=xdRyxhT_y01JpZtH2JrTOQ@mail.gmail.com>
On Sat, Oct 03, 2015 at 06:01:30AM -0700, Jorge Almeida wrote:
> On Sat, Oct 3, 2015 at 5:27 AM, vlse <vlse@veera.biz> wrote:
> >>In order to use these, you need to have kernel headers installed.
> >>There are several ways to get them, but the easiest is the way
> >>provided by the kernel:
> >
> >>https://www.kernel.org/doc/Documentation/kbuild/headers_install.txt
> >
> > But the vanilla kernel headers/source are not properly adapted for
> > musl; is'nt it. Or has it changed with musl and we can use the
> > vanilla kernel sources from www.kernel.org.
> >
> > But then why do sabotage uses modified/adapted kernel headers.
>
> Good question. Conventional wisdom states that one must keep the
> headers glibc was compiled against, not the headers of the current
> kernel, but the why is never explained. Does it apply here (with
> s/glibc/musl)?
This does not apply whatsoever to musl since musl does not use kernel
headers at all -- unless you want to count the few wrappers in sys/*.h
which this thread is about, but musl is not actually "using" the
kernel headers here, just helping applications that use the official
<sys/*.h> includes find the kernel headers for their own use.
Rich
next prev parent reply other threads:[~2015-10-03 18:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-03 12:27 linux/vt.h vlse
2015-10-03 13:01 ` linux/vt.h Jorge Almeida
2015-10-03 16:42 ` Laurent Bercot
2015-10-03 16:51 ` Jorge Almeida
2015-10-03 18:00 ` Rich Felker [this message]
2015-10-03 18:37 ` Jorge Almeida
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=20151003180015.GA8645@brightrain.aerifal.cx \
--to=dalias@libc.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).