Quite simply, the package compiles just fine without kernel sources. Simply removing the linux-info_pkg_setup line from pkg_setup is enough to make this package work properly for release building. What this does is causes the package to spit out a warning if it cannot determine the kernel information, but it doesn't make it fatal, since it is possible to be building this package in many ways, such as building a LiveCD or GRP set. Thanks
I just hit this bug again during a test-catalyst-run. Would be great if this will be officially resolved instead of in the release-snapshot only.
commited. Sorry about the delay.
*** Bug 157467 has been marked as a duplicate of this bug. ***
Hi, I got this bug when trying to build an ivman (bug 157467). Then I re-compiled the kernel with a an asking support, and I still got this message pops-up. I think it should not be reported, if the kernel configuration is correct. Thank you.
No, your "bug" is just the opposite. It is the *intended* behavior for it to continue compiling, even if the support is not in the current kernel. This is necessary for building releases. Anyway, it's not changing.
(In reply to comment #5) > No, your "bug" is just the opposite. It is the *intended* behavior for it to > continue compiling, even if the support is not in the current kernel. This is > necessary for building releases. Anyway, it's not changing. Yes, it is the opposite. But when I turn on this option, re-compiled the kernel, re-booted and tried again, I get the same message. Does this mean that the package does not actually check for that option, and the message is just a warning?
