You are not logged in.
Pages: 1
When I update my pf kernel, after it has been compiled, it always installs the kernel first, and only after the headers.
This seems to me quite daft, because I have several HOOKS to recompile modules like fxgl or vbox that run upon installation of kernel. However, they require updated headers to be present.
The result is, that automatic compilation of those modules fail because headers are installed afterwards.
Is there some way to inverse it?
Offline
Install them one at a time? Am I missing something?
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
This is not recommended, but I guess you could use the -dd option to force the installation of the headers before (-d twice to completely disable dependency checks). It should allow you to install it anyway even if the kernel is missing.
Another option would be to remove the check from the PKGBUILD before building linux-pf. Just get rid of "depends=('linux-pf')" from the package_linux-pf-headers() function so pacman doesn't complain at all.
Offline
my solution is remake kernel after update
"mkinitcpio -p linux"
Offline
Note that the headers for the standard kernel do not depend on the kernel's being installed. Is this different for the pf kernel?
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
@atmouse
I think your workaround is best.
However, the necessity for a workaround kind of defeats the purpose of HOOKS.
@cfr
Yes, it is different.
Offline
Pages: 1