Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [ISSUE] nvidia340 fails to build on linux4.19-4.19.59_1
Date: Mon, 15 Jul 2019 02:31:07 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-13128@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]

New issue by patoski on void-packages repository

https://github.com/void-linux/void-packages/issues/13128
Description: ### System

* xuname:  
Void 4.19.59_1 x86_64 GenuineIntel
* package:  
nvidia340-340.107_3

### Expected behavior
When updating system with xbps-install -Syu the nvidia DKMS should build.
 
### Actual behavior
While trying to build the nvidia module comes back with "... FAILED!" System will not reboot into X Windows unless using an old kernel.
### Steps to reproduce the behavior
Try to build nvidia340 module with linux4.19-4.19.59_1 and linux4.19-headers-4.19.59_1

### Notes to fix
Log in as root an run: `export IGNORE_CC_MISMATCH=1`
then run: `xbps-install -Sf linux4.19-*`
The nvidia dkms kernel module will compile successfully.

When trying to build the nvidia module manually in /var/lib/nvidia `make` complains that the current compiler version is different than that used to build the kernel or something like that. The error message advises to set IGNORE_CC_MISMATCH to 1

This issue has been happening for me for a few months or so.

             reply	other threads:[~2019-07-15  0:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-15  0:31 voidlinux-github [this message]
2019-07-15  8:13 ` [ISSUE] [CLOSED] " voidlinux-github
2019-07-15  8:13 ` 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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-13128@inbox.vuxu.org \
    --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).