would it be possible to make a dkms that works for both gcc and Clang compiled kernels?
Search Criteria
Package Details: zfs-dkms 2.2.6-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/zfs-dkms.git (read-only, click to copy) |
---|---|
Package Base: | zfs-dkms |
Description: | Kernel modules for the Zettabyte File System. |
Upstream URL: | https://zfsonlinux.org/ |
Licenses: | CDDL |
Provides: | SPL-MODULE, zfs, ZFS-MODULE |
Submitter: | isiachi |
Maintainer: | kstolp |
Last Packager: | kstolp |
Votes: | 179 |
Popularity: | 6.41 |
First Submitted: | 2015-08-31 12:01 (UTC) |
Last Updated: | 2024-09-05 04:42 (UTC) |
Dependencies (2)
- dkms (dkms-gitAUR, dkms-fast-zstdAUR)
- zfs-utilsAUR (zfs-utils-gitAUR, zfs-linux-gitAUR, zfs-utils-staging-gitAUR)
Required by (20)
- cockpit-zfs-manager (requires zfs)
- prepare-lastboot (requires zfs)
- python-pyzfscmds (requires zfs)
- targetd (optional)
- targetd-git (optional)
- zbectl-git (requires zfs)
- zectl (requires zfs)
- zectl-git (requires zfs)
- zedenv (requires zfs)
- zedenv-git (requires zfs)
- zedenv-grub (requires zfs)
- zfs-auto-snapshot (requires zfs)
- zfs-auto-snapshot-git (requires zfs)
- zfs-openrc
- zfsbootmenu (requires zfs)
- zfsbootmenu-efi-bin (requires zfs)
- znapzend (requires zfs)
- znapzupport (requires zfs)
- zsnapd (requires zfs)
- zxfer (requires zfs)
Sources (4)
Latest Comments
« First ‹ Previous 1 .. 13 14 15 16 17 18 19 20 21 22 23 .. 63 Next › Last »
j1simon commented on 2023-04-07 11:39 (UTC)
Vrakfall commented on 2023-03-31 02:43 (UTC) (edited on 2023-03-31 03:26 (UTC) by Vrakfall)
In the meantime, the merged patch could be included in this package in order for it to work with kernel 6.2.8 and potentially above until zfs 2.1.10 comes out.
Someone on the github issue even wrote a PKGBUILD patch for it (for the git version)!
I already wrote a correct PKGBUILD for zfs-dkms
that I tested, if you want I could push it here.
mabod commented on 2023-03-30 05:21 (UTC)
@karns: It is NOT illegal. You can do with the source code whatever you want. This is the right you are granted by either of the open source licenses, specifically the GPL.
karns commented on 2023-03-29 20:34 (UTC)
@thedanbob: Not that I would ever use this method, because it is illegal, but if you want to try it - make sure you run it twice. The first time you may get an odd issue.
ipaqmaster commented on 2023-03-26 00:54 (UTC)
Had to downgrade from Linux 6.2.8 to Linux 6.2.7 to avoid GPL-incompatible module
during DKMS build. What a pain.
kstolp commented on 2023-03-24 22:05 (UTC)
They plan to have a proper fix for this in the 2.1.10 release. (https://github.com/openzfs/zfs/issues/14658#issuecomment-1483462181)
RAMChYLD commented on 2023-03-24 17:40 (UTC) (edited on 2023-03-24 17:41 (UTC) by RAMChYLD)
@thedanbob: a (legally) safer way would be to integrate patches 3ace9de and 2e9c9b7 from github. Using the sed command only makes the kernel module lie about it's license which is legally wrong.
https://github.com/openzfs/zfs/issues/14658
The patches rewrites the the offending parts of the code to not use the two offending GPL-only symbols. You need to rerun autogen.sh once the patches are applied. I've tested this on both 2.1.9 and git and they work, so I can vouch for it.
thedanbob commented on 2023-03-24 01:17 (UTC)
It just broke on x86_64 too with kernel 6.2.8. A workaround is to edit the PKGBUILD to change the license to GPL:
prepare() {
cd "${srcdir}"/${pkgname%-dkms}-${pkgver}
sed -i 's/CDDL/GPL/' META # <-- add this line
mabod commented on 2023-03-18 07:44 (UTC)
@Taurolyon: This is a known issue. Reported 2 weeks ago for kernel 6.2.1 on github: https://github.com/openzfs/zfs/issues/14555
Taurolyon commented on 2023-03-18 06:21 (UTC) (edited on 2023-03-18 06:23 (UTC) by Taurolyon)
Getting the following when building.
==> dkms install --no-depmod zfs/2.1.9 -k 6.2.5-1-MANJARO-ARM
Error! Bad return status for module build on kernel: 6.2.5-1-MANJARO-ARM (aarch64)
Consult /var/lib/dkms/zfs/2.1.9/build/make.log for more information.
==> WARNING: `dkms install --no-depmod zfs/2.1.9 -k 6.2.5-1-MANJARO-ARM' exited 10
Checked the log and got these GPL errors:
MODPOST /var/lib/dkms/zfs/2.1.9/build/module/Module.symvers
ERROR: modpost: GPL-incompatible module zcommon.ko uses GPL-only symbol 'kernel_neon_begin'
ERROR: modpost: GPL-incompatible module zcommon.ko uses GPL-only symbol 'kernel_neon_end'
ERROR: modpost: GPL-incompatible module zfs.ko uses GPL-only symbol 'kernel_neon_end'
ERROR: modpost: GPL-incompatible module zfs.ko uses GPL-only symbol 'kernel_neon_begin'
make[2]: *** [scripts/Makefile.modpost:138: /var/lib/dkms/zfs/2.1.9/build/module/Module.symvers] Error 1
make[1]: *** [Makefile:1973: modpost] Error 2
make: *** [Makefile:55: modules-Linux] Error 2
make: Leaving directory '/var/lib/dkms/zfs/2.1.9/build/module'
Pinned Comments
kstolp commented on 2023-09-29 00:34 (UTC)
When requesting changes, please include detailed reasoning for the change.
kstolp commented on 2023-01-07 09:31 (UTC)
If you receive this error when trying to build, it is because you have not imported the GPG keys used for verification.
You have two options:
1) Import the two keys into your keyring. ArchWiki article. You can find the key IDs in the PKGBUILD file, in the
validpgpkeys
array. (recommended)2) Alternatively, you can skip this verification by passing the
--skippgpcheck
argument tomakepkg
when building. (not recommended)