Bug 35637
Summary: | Upgrade 2.2.14-22 to 2.2.17-14 fails - can't compile sources either | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <bernard> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED WONTFIX | QA Contact: | Brock Organ <borgan> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-06-06 00:17:28 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
2001-04-11 14:42:27 UTC
I tried a 'make mrproper' before, same result. I installed kgcc-1.1.2-40 (got from RH7.0) and the compilation process was okay! So the problem is 100% linked to the compilation tools. Maybe the kernel-source rpm should require kgcc... However, I've found something strange in net/ipv4/ip_masq.c : I had to comment line 578 & 579 to be able to compile this file: /*EXPORT_SYMBOL(ip_masq_hash);*/ /*EXPORT_SYMBOL(ip_masq_unhash);*/ Thanks 1) Re the lilo.conf: You don't want the kernel rpm to edit your lilo.conf, do you? 2) Re "make mrproper" yes it is annoying, but there is nothing we can do about it given the state the kernel buildsystem is in 3) Re the EXPORT_SYMBOL(ip_masq_hash);, that should be fixed in the 2.2.19 we recently released. 1) About lilo.conf: I'd like the rpm to tell me something like "warning: files have been changed in /boot. Check lilo.conf consistency!" and have files removed from /boot put in a backup place. Or better, have the new files installed in "/tmp/boot/", with a message saying "new kernel installed in /tmp/boot, you have to move it to /boot and edit lilo.conf". In the actual situation, if someone just applies the patch and then reboot, the system can be in a inconsistent state. This must be avoided. 2) For 'mrproper': the problem is the same: a comment from rpm(1) would remind people of what is the first thing to do when installing the kernel sources. (In this particular case it changed nothing but that's not the point) I dunno if the rpm building system allows one to insert such comments in a way that will display the comments when the package is installed. Obviously, you would have less support to perform on these matters if such a feature is used. (and have these comments copied in a file displayed at reboot when one performed a full release upgrade) My 2cts comment... It's hard to display those. And NO files will be removed if you do rpm -i kernel-FOO.rpm only if you use rpm -iU which you really shouldn't use. |