Description of problem: I want to build a kernel with modules deactivated and transfer it in rpm form. After the 'make bzImage' step, the make rpm process crashes. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.rpm -i kernel-source-2.4.18-18.8.0 2.choose any way to create /usr/src/linux-2.4/.config, but deselect use of modules 3.replace rpm with rpmbuild in Makefile, under the rpm: label 4.make rpm Actual Results: Boot sector 512 bytes. Setup is 4797 bytes. System is 812 kB make[2]: Leaving directory `/usr/src/redhat/BUILD/kernel-2.4.1818.8.0custom/arch/i386/boot' The present kernel configuration has modules disabled. Type 'make config' and enable loadable module support. Then build a kernel with module support enabled. make[1]: *** [modules] Error 1 make[1]: Leaving directory `/usr/src/redhat/BUILD/kernel-2.4.1818.8.0custom' error: Bad exit status from /var/tmp/rpm-tmp.68538 (%build) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.68538 (%build) make: *** [rpm] Error 1 Expected Results: kernel build + binary rpm of kernel Additional info:
Actually I should add a footnote to this To rebuild RH kernels it is handled by the spec file - and rpmbuild --install kernel-blah.src.rpm rpmbuild -ba SPEC/kernel.spec
just a sidenote: #rpm -qa|grep kern kernel-2.4.18-18.7.x glibc-kernheaders-2.4-7.16 kernel-source-2.4.18-18.7.x # cp configs/kernel-2.4.18-athlon.config .config # make spec . scripts/mkspec >kernel.spec # mv kernel.spec /usr/src/redhat/SPECS/ # rpmbuild -bb /usr/src/redhat/SPECS/kernel.spec error: File /usr/src/redhat/SOURCES/kernel-2.4.1818.7.xcustom.tar.gz: No such file or directory as a matter of fact, I do not think rpmbuild would work as proposed in the previous comment if more patches are to be applied by external scripts (as in adding freeswan for instance)
Thanks for the bug report. However, Red Hat no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem in the bug tracker at: http://bugzilla.fedora.us/