Bug 422711
Summary: | Wrong kernel version (2.6.23.9-rc1) in kernel source for 2.6.23.8-63.f8 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Need Real Name <bugzilla> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 8 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-01-16 21:42:47 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Need Real Name
2007-12-13 00:55:07 UTC
Changing that version probably isn't going to help; it would have been called 2.6.23.9-63.rc1.fc8 Well, at least for my purposes, *manually* setting EXTRAVERSION=.8-63.fc8 seems to have solved my problem. The point remains thought that there doesn't seem to be a valid source in udpates-sources corresponding to the latest kernel which I would think is a "bad thing" Any reason not to fix the rpm now or do we just have to wait for the next kernel release to (hopefully) fix this You should be using the kernel-devel package to build external modules. I wasn't building an external module. I was building a patched version of the bttv module since it doesn't work properly for the Winfast 2000XP board. Now that the new kernels have broken gpio, it is critical to make this simple patch to bttv-input.c in order to user lirc with the board. The sources for that module (obviously) are only found in the full kernel source RPM. I have in fact submitted the patch to the kernel bugzilla but have not heard back... (https://bugzilla.redhat.com/show_bug.cgi?id=369921) Clearly the bug mentioned will affect anybody who needs to use portions of the kernel source to recompile individual modules against the stock F8 kernel. So, I repeat my question... "Any reason not to fix the rpm now or do we just have to wait for the next kernel release to (hopefully) fix this" Similar problem with kernel 2.6.23.9-85.fc8 The source kernel after running rpmbuild on it still has: MODVERSION=.9 However, to get things to build compatible modules for this kernel you should have MODVERSION=.9-85.fc8. Am I missing something here? Because I would have thought that the whole point of running rpmbuild and thereby installing all the patches that convert this from vanilla 2.6.23.9 to 2.6.23.9-85.fc8 should also change the MODVERSION so this thing will compile correctly. What am I missing here? Is this a bug or not? If not, please explain why not and let's close it. If yes, it is ever so simple to fix... EXTRAVERSION gets fixed up in the BuildKernel() script in kernel.spec. If you build an entire kernel instead of just one module everything should work fine. And building just one module with possibly a different C compiler than was used to build the original kernel could cause problems, so we don't support that. http://fedoraproject.org/wiki/Docs/CustomKernel |