From: egrain <egrain@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: zfs on musl: Building DKMS module 'zfs-2.1.9' for kernel-6.1.19_1... FAILED!
Date: Mon, 20 Mar 2023 17:40:16 +0100 [thread overview]
Message-ID: <20230320164016.IYVNaV06WLSNGecJPg8MMxlWQ-zA9IpGE1EMM7MEt-w@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42871@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2692 bytes --]
New comment by egrain on void-packages repository
https://github.com/void-linux/void-packages/issues/42871#issuecomment-1476578175
Comment:
$ xbps-query -l | grep -v '^ii'
nothing
$ doas xbps-reconfigure -f linux6.1
linux6.1: configuring ...
Executing post-install kernel hook: 10-dkms ...
Available DKMS module: zfs-2.1.9.
Building DKMS module: zfs-2.1.9... FAILED!
Generating kernel module dependency lists... done.
Executing post-install kernel hook: 20-initramfs ...
dracut-install: Failed to find module 'zfs'
dracut: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.inSxCU/initramfs --kerneldir /lib/modules/6.1.19_1/ -m zfs
dracut: installkernel failed in module zfs
Executing post-install kernel hook: 50-grub ...
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.1.19_1
Found initrd image: /boot/initramfs-6.1.19_1.img
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
done
linux6.1: configured successfully.
You sure about that last one? Gave me this:
$ doas dkms build --force -m zfs -v 2.1.9 -k 6.1.9_1
Sign command: /lib/modules/6.1.9_1/build/scripts/sign-file
Binary /lib/modules/6.1.9_1/build/scripts/sign-file not found, modules won't be signed
Error! Your kernel headers for kernel 6.1.9_1 cannot be found at /lib/modules/6.1.9_1/build or /lib/modules/6.1.9_1/source.
Please install the linux-headers-6.1.9_1 package or use the --kernelsourcedir option to tell DKMS where it's located.
I added a 1 to 6.1.9:
$ doas dkms build --force -m zfs -v 2.1.9 -k 6.1.19_1
Sign command: /lib/modules/6.1.19_1/build/scripts/sign-file
Binary /lib/modules/6.1.19_1/build/scripts/sign-file not found, modules won't be signed
Warning: The pre_build script is not executable.
Building module:
Cleaning build area...(bad exit status: 2)
make -j12 KERNELRELEASE=6.1.19_1 -C module/...(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.1.19_1 (x86_64)
Consult /var/lib/dkms/zfs/2.1.9/build/make.log for more information.
$ find /lib/modules/6.1.19_1/build/scripts/ -iname *sign*
/lib/modules/6.1.19_1/build/scripts/sign-file.c
/lib/modules/6.1.19_1/build/scripts/coccinelle/tests/unsigned_lesser_than_zero.cocci
$ cat /var/lib/dkms/zfs/2.1.9/build/make.log
DKMS make.log for zfs-2.1.9 for kernel 6.1.19_1 (x86_64)
Mon Mar 20 16:37:30 UTC 2023
make: Entering directory '/var/lib/dkms/zfs/2.1.9/build/module'
make: *** No targets specified and no makefile found. Stop.
make: Leaving directory '/var/lib/dkms/zfs/2.1.9/build/module'
next prev parent reply other threads:[~2023-03-20 16:40 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-19 21:00 [ISSUE] " egrain
2023-03-20 2:32 ` sgn
2023-03-20 8:02 ` egrain
2023-03-20 10:02 ` egrain
2023-03-20 14:43 ` sgn
2023-03-20 14:47 ` sgn
2023-03-20 15:11 ` egrain
2023-03-20 15:12 ` egrain
2023-03-20 15:16 ` egrain
2023-03-20 15:18 ` egrain
2023-03-20 16:01 ` sgn
2023-03-20 16:11 ` egrain
2023-03-20 16:21 ` sgn
2023-03-20 16:26 ` sgn
2023-03-20 16:40 ` egrain [this message]
2023-03-20 16:46 ` sgn
2023-03-20 16:47 ` sgn
2023-03-20 16:47 ` egrain
2023-03-20 16:50 ` sgn
2023-03-20 16:52 ` egrain
2023-03-20 17:05 ` sgn
2023-03-20 17:10 ` sgn
2023-03-20 17:10 ` sgn
2023-03-20 17:10 ` sgn
2023-03-20 17:14 ` egrain
2023-03-20 17:16 ` paper42
2023-03-20 17:17 ` paper42
2023-03-20 17:27 ` egrain
2023-03-21 0:44 ` sgn
2023-03-21 9:13 ` egrain
2023-03-21 10:39 ` [ISSUE] [CLOSED] " paper42
2023-03-23 1:59 ` sgn
2023-03-23 7:45 ` egrain
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=20230320164016.IYVNaV06WLSNGecJPg8MMxlWQ-zA9IpGE1EMM7MEt-w@z \
--to=egrain@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).