Summary: | sys-fs/zfs-kmod: ebuild requires build kernel before building module into kernel source tree | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | lekto |
Component: | Current packages | Assignee: | Sam James <sam> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | ionen, neb.semqen.ramesses, sam |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | emerge --info |
Description
lekto
2023-06-26 17:15:50 UTC
You can set EXTRA_ECONF via /etc/portage/env, fwiw. For some backstory on the check... Without Module.symvers, it cannot verify if symbols used by the modules are available in the kernel and then it could fail at runtime (which I feel is especially unsafe with zfs). Furthermore, without that file the kernel will typically also abort the build unless the user sets KBUILD_MODPOST_WARN=1 to change errors into warnings making this a predictable failure that the eclass is trying to explain. Some packages also probe that file for their configuration and could be misconfigured without it (nvidia for one). zfs-kmod would *also* normally fail given it looks for Module.symvers *unless* --enable-linux-builtin In other words I see this as an unsupported configuration using EXTRA_ECONF, but that aside there's two possible solutions I see to this without removing the IMO justified check: 1. touch Module.symvers at the top of the linux tree (hack) 2. Unsure how many people need this, but I could consider adding a variable to cleanly bypass the check in the eclass and inform about it in the error message. (In reply to Ionen Wolkens from comment #2) > 1. touch Module.symvers at the top of the linux tree (hack) > > 2. Unsure how many people need this, but I could consider adding a variable > to cleanly bypass the check in the eclass and inform about it in the error > message. Guess you could also consider: 3. don't use the ebuild I'm not sure if using the ebuild to add builtin modules to the kernel make much sense. >Without Module.symvers, it cannot verify if symbols used by the modules are available in the kernel and then it could fail at runtime Wouldn't it fail at build time? >2. Unsure how many people need this, but I could consider adding a variable to cleanly bypass the check in the eclass and inform about it in the error message. Sounds okay, but would be possible to bypass check if sys-fs/zfs has kernel-builtin flag set? |