From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: linux/vt.h
Date: Thu, 1 Oct 2015 16:15:12 -0400 [thread overview]
Message-ID: <20151001201512.GK8645@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAKpSnp+SwzLH-w+tbhqEEcExtX-aHe8tHEB_nXNYO7ZSkFXtXg@mail.gmail.com>
On Thu, Oct 01, 2015 at 01:02:51PM -0700, Jorge Almeida wrote:
> Greetings
>
> <sys/vt.h> includes <linux/vt.h>, but there is no such thing
There are a couple of headers like this that are questionable to have
in musl at all, but it seemed like the most sensible place to have
them. I think sys/soundcard.h and sys/kd.h are also like this. These
are headers that really have nothing to do with libc or userspace
stuff; they just define ioctl interfaces to the Linux kernel. But
for various historical reasons they were in sys/ rather than linux/
where the kernel headers would go.
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
You should point INSTALL_HDR_PATH to the location of the musl include
dir if you use this method.
Alternatively if you don't want to download and extract the whole
kernel source, Sabotage Linux has a working kernels headers package;
you can simply download from their mirrors listed in the package file:
https://github.com/sabotage-linux/sabotage/blob/master/pkg/kernel-headers
Hope this helps.
BTW once the wiki is back up we should put this on the FAQ if it's not
already there..
Rich
next prev parent reply other threads:[~2015-10-01 20:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 20:02 linux/vt.h Jorge Almeida
2015-10-01 20:15 ` Rich Felker [this message]
2015-10-01 20:51 ` linux/vt.h Jorge Almeida
2015-10-03 12:27 linux/vt.h 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=20151001201512.GK8645@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).