From: drichline <drichline@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] ZFS DKMS build fails on freshly installed system
Date: Fri, 30 Sep 2022 11:36:05 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39539@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1370 bytes --]
New issue by drichline on void-packages repository
https://github.com/void-linux/void-packages/issues/39539
Description:
### Is this a new report?
Yes
### System Info
Void 5.19.10_1 x86_64 GenuineIntel/VM uptodate rFF
### Package(s) Affected
zfs-2.1.5_3
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
I installed a fresh Void system, updated with xbps-install -Su, rebooted into kernel 5.19 (also tested with linux-lts, same result), and attempted to install ZFS.
### Actual behaviour
On installing (and reinstalling) ZFS, this is the end of the xbps output:
```zfs-2.1.5_3: configuring ...
Added DKMS module 'zfs-2.1.5'.
Skipping kernel-5.13.19_1. kernel-headers package not installed...
Building DKMS module 'zfs-2.1.5' for kernel-5.19.10_1... Killed
```
Manually building with the DKMS module (sudo dkms build zfs/2.1.5) ended with a segmentation fault in gcc and the attached [make.log](https://github.com/void-linux/void-packages/files/9682842/make.log) file.
### Steps to reproduce
(Please note, this is my first time using void. I reinstalled and tried again to make sure it wasn't a fluke)
1. Install a fresh void system (tried with both local and netinstall)
2. Sync/update system and reboot
3. xbps-install zfs
4. DKMS fails, even on kernels <5.18
next reply other threads:[~2022-09-30 9:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 9:36 drichline [this message]
2022-09-30 13:14 ` Duncaen
2022-09-30 13:14 ` Duncaen
2022-09-30 13:31 ` ahesford
2022-09-30 14:02 ` drichline
2022-09-30 14:02 ` drichline
2022-09-30 14:10 ` ahesford
2022-09-30 15:33 ` drichline
2022-09-30 15:33 ` [ISSUE] [CLOSED] " drichline
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-39539@inbox.vuxu.org \
--to=drichline@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).