You are not logged in.
I am using zfs-dkms which depends on spl-dkms. Sometimes dkms will try to build/install zfs before spl resulting in error
: Running post-transaction hooks...
(1/6) Install DKMS modules
==> dkms install zfs/0.6.5.8 -k 4.4.39-1-lts
configure: error:
*** Please make sure the kmod spl devel <kernel> package for your
*** distribution is installed then try again. If that fails you
*** can specify the location of the spl objects with the
*** '--with-spl-obj=PATH' option.
Error! Bad return status for module build on kernel: 4.4.39-1-lts (x86_64)
Consult /var/lib/dkms/zfs/0.6.5.8/build/make.log for more information.
==> dkms install nvidia/375.26 -k 4.4.39-1-lts
==> dkms install vboxhost/5.1.10_OSE -k 4.4.39-1-lts
==> dkms install spl/0.6.5.8 -k 4.4.39-1-lts
(2/6) Updating linux-lts initcpios
...
For now I just run dkms manually to install zfs after pacman has finished
$ sudo dkms install zfs/0.6.5.8 -k 4.4.39-1-lts
Is there a way to control how these modules are built/installed by dkms? I would like to ensure that spl is always installed before zfs. Any guidance in the correct direction would be greatly appreciated.
Edit:
More specifically I am confused about how this is being handled. Im not exactly sure where I should be searching for my answer. It seems this could possibly be handled by editing the zfs-dkms PKGBUILD. Or more likely I could manage this with custom hook? I have not got my head wrapped around this completely yet.
I am thinking I should be looking toward a custom hook for dkms that would install spl followed by zfs then followed by any remaining dkms modules. Is this on correct path or am I totally misunderstanding what I am reading?
Last edited by tprelog (2016-12-17 19:55:09)
Offline
I am thinking I should be looking toward a custom hook for dkms that would install spl followed by zfs then followed by any remaining dkms modules. Is this on correct path or am I totally misunderstanding what I am reading?
I think you're on the right path.
A quick peek in some dkms packages suggests they all use the same hooks, provided by the dkms package itself.
usr/share/libalpm/hooks/70-dkms-install.hook
usr/share/libalpm/hooks/70-dkms-remove.hook
Custom hooks that use a number below 70 should be executed before the default dkms hooks .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
@OP did you ever find a way to fix this?
Polar bears are left handed
Offline