From: Mark H Weaver <mhw@netris.org>
To: Eleven <qiaochu321@126.com>
Cc: help-guix@gnu.org
Subject: Re: Missing platform_device.h in linux-libre-headers
Date: Sun, 08 Apr 2018 16:52:40 -0400 [thread overview]
Message-ID: <87d0z9qv3b.fsf@netris.org> (raw)
In-Reply-To: <3C5A836C-851A-417A-AA49-363F371D5FBD@126.com> (Eleven's message of "Sun, 8 Apr 2018 23:18:01 +0800")
Hi,
Eleven <qiaochu321@126.com> writes:
> I’m trying to compile some extra kernel module for my guixsd, however
> the headers files needed, `modules.h` and `platform_device.h` was not
> found. After redefining the linux-libra-headers package, update the
> version to 4.15.13 which is the version of the kernel I’m currently
> running, I get `modules.h` but `platform_device.h` still
> missing. What’s the problem and how can I fix it?
platform_device.h is not part of the user API, so it's not installed by
the "headers_install" make target in linux-libre.
I would recommend against changing the 'linux-libre-headers' package
itself. The contents of 'linux-libre-headers' is included in our
default C headers used to build the entire system. Updating it entails
a full system rebuild from the toolchain up. Even if not for this
practical problem, I would argue that private kernel driver interfaces
do not belong in our default C headers.
The headers needed to build kernel modules should be a separate package,
maybe called 'linux-libre-kernel-headers' or
'linux-libre-internal-headers'. It could be almost the same as
'linux-libre-headers', except that it should use the current kernel
version (using the %linux-libre-version and %linux-libre-hash variables)
and it should use different make targets in the 'build' and 'install'
phases, namely "headers_check_all" and "headers_install_all".
Mark
prev parent reply other threads:[~2018-04-08 20:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-08 15:18 Missing platform_device.h in linux-libre-headers Eleven
2018-04-08 20:52 ` Mark H Weaver [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d0z9qv3b.fsf@netris.org \
--to=mhw@netris.org \
--cc=help-guix@gnu.org \
--cc=qiaochu321@126.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).