From: FirstZero <FirstZero@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] virtualbox-ose-dkms: fails to build DKMS module on the latest kernel
Date: Sun, 30 Aug 2020 17:25:08 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24551@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1015 bytes --]
New issue by FirstZero on void-packages repository
https://github.com/void-linux/void-packages/issues/24551
Description:
* xuname:
Void 5.8.5_1 x86_64 AuthenticAMD uptodate rrrrmmnFFFFFFF
* package:
virtualbox-ose-6.1.10_2
virtualbox-ose-dkms-6.1.10_2
### Expected behavior
The DKMS module for virtualbox-ose-6.1.10 is getting built.
### Actual behavior
The DKMS module for virtualbox-ose-6.1.10 is not getting built.
> [*] Configuring unpacked packages
virtualbox-ose-dkms-6.1.10_2: configuring ...
DKMS module 'virtualbox-ose-6.1.10' already added, skipping.
Skipping kernel-5.3.18_1. kernel-headers package not installed...
Building DKMS module 'virtualbox-ose-6.1.10' for kernel-5.8.5_1... FAILED!
DKMS module 'virtualbox-ose-6.1.10' failed to build, please check /var/lib/dkms
for errors in the log file.
virtualbox-ose-dkms-6.1.10_2: installed successfully.
### Steps to reproduce the behavior
Install or rebuild virtualbox-ose-dkms on the latest kernel linux5.8
next reply other threads:[~2020-08-30 15:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-30 15:25 FirstZero [this message]
2020-09-01 2:18 ` sgn
2020-09-01 4:08 ` ericonr
2020-09-01 8:47 ` FirstZero
2020-09-01 8:47 ` [ISSUE] [CLOSED] " FirstZero
2020-09-01 16:23 ` FirstZero
2020-09-01 16:23 ` FirstZero
2020-09-01 16:38 ` FirstZero
2020-09-01 18:30 ` pullmoll
2020-09-01 21:32 ` FirstZero
2020-09-04 23:27 ` steinex
2020-09-08 19:16 ` pullmoll
2020-09-08 19:16 ` [ISSUE] [CLOSED] " pullmoll
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-24551@inbox.vuxu.org \
--to=firstzero@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).