From: ILadis <ILadis@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Raspberry Pi: unable to make kernel 5.x scripts
Date: Mon, 09 Nov 2020 21:02:12 +0100 [thread overview]
Message-ID: <20201109200212._H_-plclqSR47f4MxwQXunx6binR9P3nQO0OHy3AtKg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26257@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]
New comment by ILadis on void-packages repository
https://github.com/void-linux/void-packages/issues/26257#issuecomment-724240467
Comment:
I dont' want to compile a package but rather build another/external kernel module/driver for the current available kernel. I'd compare that with having to install a `devel` package in order to include its header files an compile it against the available system library.
I'd also like to mention that I could compile the kernel scripts with the `rpi-kernel-headers-4.19.127` just fine.
The kernel module/driver I'm talking about can be found here: [github.com/lwfinger/rtl8188eu](https://github.com/lwfinger/rtl8188eu/tree/v4.1.8_9499#compiling--building). I had no issue compiling its source against the previouse `rpi-kernel-4.19.127` and `rpi-kernel-headers-4.19.127`.
That is why I assume something is missing from the current `rpi-kernel-headers-5.*` that was present before.
I am by no means an expert on this field. So any help and hints are appreciated.
next prev parent reply other threads:[~2020-11-09 20:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-09 19:17 [ISSUE] " ILadis
2020-11-09 19:36 ` Anachron
2020-11-09 19:51 ` ILadis
2020-11-09 20:02 ` ILadis [this message]
2020-11-09 20:02 ` ILadis
2020-11-09 20:19 ` ILadis
2020-11-09 23:41 ` fosslinux
2020-11-10 0:12 ` pbui
2020-11-10 0:14 ` pbui
2020-11-11 10:43 ` Piraty
2020-11-11 10:43 ` [ISSUE] [CLOSED] " Piraty
2020-11-11 10:47 ` Piraty
2020-11-15 21:17 ` ILadis
2020-11-15 21:17 ` ILadis
2020-11-15 21:17 ` ILadis
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=20201109200212._H_-plclqSR47f4MxwQXunx6binR9P3nQO0OHy3AtKg@z \
--to=iladis@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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).