Bug 25974
Summary: | kernel compile fails at "make modules" | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Dan Scholnik <scholnik> |
Component: | kernel | Assignee: | Michael K. Johnson <johnsonm> |
Status: | CLOSED NOTABUG | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | CC: | linux |
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: | 2001-02-06 10:20:48 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
Dan Scholnik
2001-02-04 14:15:08 UTC
Save your .config file elsewhere, do "make mrproper", then make xconfig and load the configuration file you saved and exit xconfig. It seems like without make mrproper some residues are left from previous compilation that cause this problem. I had the same problem. It can be avoided if you unset CONFIG_MODVERSIONS - it is normally set to CONFIG_MODVERSIONS=y. Then it will compile and install. Using make mrproper is important before building -- there are many potential kernel configs. If one copys one of the *.config files from /usr/src/linux-2.4.0/configs/ to /usr/src/linux-2.4.0/.config. Then I believe that the following sequence should work. Since it does not, of what use is /usr/src/linux-2.4.0/configs/* and why is this not a bug? make dep Make clean Make bxImage Make modules make mrproper cp configs/something .config make oldconfig ... Perhaps you should change your kernel building .SPEC file to include an mrproper before it bundles up the kernel-source RPM Save a lot of people some grief. The reason we don't do that (and it is also the reason why you need make mrproper) is that the sources as they are currently installed, allow you to compile external modules (think Alsa but also VMware, NVidia) for any kernel we provide. The problem arrises when you compile your own kernel, in that case you need your own symbolversioning data, not the one we provide. "make mrproper" removes these. Obviously, something is missing from the package if you HAVE to do a 'make mrproper'. The real problem here arises when there is a bug in one of the modules acompanying the installation (in this case pcnet32). Ideally I should be able to patch the driver and build the module. However, this is not possible for reasons explained in this thread. The problem is that if I DO a 'make mrproper', and only replaces that module I will get unresolved symbols. |