From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] nvidia340: broken with linux5.4
Date: Fri, 03 Jan 2020 10:30:21 +0100 [thread overview]
Message-ID: <20200103093021.ndQl_WDXFl2Gfa9bcTvmdzhkC8QbmnqjKcCzxpC1hcs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-16923@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 990 bytes --]
Closed issue by Hoshpak on void-packages repository
https://github.com/void-linux/void-packages/issues/16923
Description:
nvidia340 fails to compile the kernel module via dkms and complains about missing Makefiles. I suspect that the use of `SUBDIRS` is the culprit since the 5.3 Makefile already warns against using that when compiling the module:
```
Makefile:213: ================= WARNING ================
Makefile:214: 'SUBDIRS' will be removed after Linux 5.3
Makefile:215:
Makefile:216: If you are building an individual subdirectory
Makefile:217: in the kernel tree, you can do like this:
Makefile:218: $ make path/to/dir/you/want/to/build/
Makefile:219: (Do not forget the trailing slash)
Makefile:220:
Makefile:221: If you are building an external module,
Makefile:222: Please use 'M=' or 'KBUILD_EXTMOD' instead
Makefile:223: ==========================================
```
The package needs to be patched or updated if nvidia releases a compatible version.
next parent reply other threads:[~2020-01-03 9:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-16923@inbox.vuxu.org>
2020-01-03 9:30 ` voidlinux-github [this message]
2020-01-04 14:36 ` voidlinux-github
2020-02-16 8:45 [ISSUE] " Hoshpak
2020-02-16 21:39 ` [ISSUE] [CLOSED] " Hoshpak
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=20200103093021.ndQl_WDXFl2Gfa9bcTvmdzhkC8QbmnqjKcCzxpC1hcs@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).