Summary: | linux-mod.eclass: build for specific kernel version | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Andreas Steinmetz <ast> |
Component: | Enhancement/Feature Requests | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
Status: | RESOLVED CANTFIX | ||
Severity: | enhancement | CC: | dev-portage |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Andreas Steinmetz
2017-07-28 17:28:57 UTC
We'd need some kind of support in linux-mod.eclass for this. linux-info/linux-mod look at the KERNEL_DIR environment var to find a linux source tree to build against. If you have set KERNEL_DIR to the new kernel source dir, or set the /usr/src/linux symlink, I would expect @module-rebuild to re-compile modules against the new kernel version, not the currently running kernel version. Hmm, ok, the soft link version seems to work (tried with running 4.9.39 to build for 4.9.36) though I'm quite sure it didn't work the last time I tried this (well, quite some time ago). Anyway, it would be nice if this behaviour would be documented somewhere, preferably the emerge man page. Thanks for your patience. It's documented here. https://devmanual.gentoo.org/eclass-reference/linux-info.eclass/index.html It would be nice to have some user docs on this, but that probably belongs on the wiki rather than in any portage documentation. Don't think there's anything for kernel team to do here. |