From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] nvidia340-dkms fails to build
Date: Sun, 08 Sep 2019 11:57:18 +0200 [thread overview]
Message-ID: <20190908095718.n8P4qSwvfrsKHgqtIBMu0teq6zGFzQEVTF_p7hO8VO0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14273@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 957 bytes --]
Closed issue by VoidDuck on void-packages repository
https://github.com/void-linux/void-packages/issues/14273
Description:
### System
* xuname:
Void 4.19.69_1 x86_64 GenuineIntel uptodate rF
* package:
nvidia340-dkms-340.107_3
### Expected behavior
The kernel module should be built and installed
### Actual behavior
The build fails with following error message:
`ERROR: Kernel configuration is invalid
include/generated/autoconf.h or include/config/auto.conf are missing.
Run 'make oldconfig && make prepare' on kernel src to fix it.`
Running `make oldconfig && make prepare` gives an error as well:
`scripts/kconfig/conf --syncconfig Kconfig
scripts/Makefile.build:45: arch/x86/entry/syscalls/Makefile: No such file or directory
make[1]: *** No rule to make target 'arch/x86/entry/syscalls/Makefile'. Stop.
make: *** [arch/x86/Makefile:245: archheaders] Error 2`
### Steps to reproduce the behavior
Install nvidia340
next prev parent reply other threads:[~2019-09-08 9:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 21:37 [ISSUE] nvidia340-dkms installation fails voidlinux-github
2019-09-06 22:41 ` nvidia340-dkms fails to build voidlinux-github
2019-09-07 11:29 ` voidlinux-github
2019-09-07 17:43 ` voidlinux-github
2019-09-08 9:56 ` voidlinux-github
2019-09-08 9:57 ` voidlinux-github [this message]
2019-09-10 12:38 ` voidlinux-github
2019-09-10 13:32 ` voidlinux-github
2019-09-10 14:37 ` [ISSUE] [CLOSED] " 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=20190908095718.n8P4qSwvfrsKHgqtIBMu0teq6zGFzQEVTF_p7hO8VO0@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).