You are not logged in.
Hi,
sorry for the stupid question, I bet it's obvious, because it's difficult for me to find any specific answer on this ![]()
What I always wondered is whether I need to reboot after a kernel upgrade before the makepkg/PKGBUILD system makes use of the new kernel headers.
Is there a *good* way to force it to use the new kernel stuff like changing an environment variable?
It would be nice if it was possible to delay the reboot -after a kernel upgrade- until after remaining packages that might depend on the kernel headers have been upgraded or rebuilt.
Thank you!
Max
Offline
There shouldn't be any need for reboot. As long as you have latest linux-headers installed, everything should be built against them.
If you want to make things easy for yourself, you can enable dkms systemd service, which builds any dkms modules automatically after reboot to a new kernel.
Offline
There shouldn't be any need for reboot. As long as you have latest linux-headers installed, everything should be built against them.
"Should" is a key word there. In reality, this might take some patching of makefiles, or at least setting of environment variables as many makefiles use the output of `uname -r` in constructing the path.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
"Should" is a key word there. In reality, this might take some patching of makefiles, or at least setting of environment variables as many makefiles use the output of `uname -r` in constructing the path.
I think I missed the question a bit, since it was about buiding packages with makepkg, and not building of kernel modules where I don't see any issues at least if you use dkms. Thanks for the correction.
With makepkg it completely depends on what you're building. Looks like many PKGBUILDs check the kernel version from /usr/lib/modules/extramodules-KERNEL/version, which should be updated alongside with the kernel (and not kernel headers).
Offline
There shouldn't be any need for reboot. As long as you have latest linux-headers installed, everything should be built against them.
If you want to make things easy for yourself, you can enable dkms systemd service, which builds any dkms modules automatically after reboot to a new kernel.
Trilby wrote:"Should" is a key word there. In reality, this might take some patching of makefiles, or at least setting of environment variables as many makefiles use the output of `uname -r` in constructing the path.
I think I missed the question a bit, since it was about buiding packages with makepkg, and not building of kernel modules where I don't see any issues at least if you use dkms. Thanks for the correction.
With makepkg it completely depends on what you're building. Looks like many PKGBUILDs check the kernel version from /usr/lib/modules/extramodules-KERNEL/version, which should be updated alongside with the kernel (and not kernel headers).
Thank you very much ooo and Trilby! I have been wondering about this since ages ![]()
I wish you a nice weekend!
Offline