From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [Tracking] linux 5.2 dkms status
Date: Tue, 10 Sep 2019 11:34:54 +0200 [thread overview]
Message-ID: <20190910093454.fXEpapBBW0pfUgwsOAV2kPVodOs6Lx7GM1LYHnH2HNU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12959@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 563 bytes --]
New comment by Hoshpak on void-packages repository
https://github.com/void-linux/void-packages/issues/12959#issuecomment-529855640
Comment:
This is most likely caused by the gcc update and not by the kernel version. The nvidia driver checks if the gcc version used to compile the kernel matches with the gcc version used to compile the module and refuses to build otherwise. You can override this by setting `IGNORE_CC_MISMATCH=1` in the environment.
I'm closing this issue since 5.2 is now the default kernel and the dkms status is thus no longer relevant.
next prev parent reply other threads:[~2019-09-10 9:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-10 7:02 [ISSUE] " voidlinux-github
2019-07-10 14:39 ` voidlinux-github
2019-07-11 16:55 ` voidlinux-github
2019-07-12 12:10 ` voidlinux-github
2019-07-12 21:03 ` voidlinux-github
2019-07-27 15:27 ` voidlinux-github
2019-07-28 8:34 ` voidlinux-github
2019-07-28 8:44 ` voidlinux-github
2019-07-28 9:59 ` voidlinux-github
2019-07-28 12:20 ` voidlinux-github
2019-07-29 20:13 ` voidlinux-github
2019-09-10 9:26 ` voidlinux-github
2019-09-10 9:34 ` [ISSUE] [CLOSED] " voidlinux-github
2019-09-10 9:34 ` voidlinux-github [this message]
2019-09-10 9:38 ` voidlinux-github
2019-09-10 9:38 ` voidlinux-github
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=20190910093454.fXEpapBBW0pfUgwsOAV2kPVodOs6Lx7GM1LYHnH2HNU@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).