The process you describe is the process I am using. There has been a couple of problems along the way. Only 1 problem has not been resolved.
If signmodules is set to 1 in the SPEC file for the arch that I have, then there is a segfault during the process when using 'rpmbuild -ba'. From the emails I have read, this is a known problem that has not been resolved.
I am currently running the process with all the fixes for the problems I have been having. This includes signmodules set to 0. Signmodules is defined in several places in the SPEC file.
I am concerned about the signmodules setting since I do not know what it does. It would seem to be important but I do not know. Are you knowledgeable about this or do you know where I can get information about it?
Thanks for your input,
David On Friday 25 May 2007 1:01 pm, Mark Hull-Richter wrote:
On 5/24/07, dcw dwoody1@charter.net wrote:
I did some more investigation. After a cd to the BUILD directory, I ran 'make xconfig' and set the 3 items that I need. isa, isapnp and ne2000 support.
From the SPEC directory I ran 'rpmbuild -bc --short-circuit kernel-2.6.spec'. After about 4 minutes I looked at the contents of the .config file in the BUILD directory.
ALL 3 ITEMS I had selected had been DELETED.
I also noticed that rpmbuild -bc runs 'make mrproper'. From my 2.4.x days, I seem to remember that mrproper restores everything to original content. Is my memory correct?
I normally use make menuconfig, but I'm wondering if the basic process is the same:
cd <rpm-build-base/BUILD/kernel*/linux*/ cp <rpm-base-dir>/SOURCES/<your-choice-of-config-file> .config make xconfig cp .config <rpm-base-dir>/SOURCES/<your-choice-of-config-file> cd <rpm-build-base>/SPECS rpmbuild ...
Whatever you create in the BUILD/kernel*/linux*/ directory is reconstructed from scratch UNLESS you are doing an rpmbuild -bc or -bi with --short-circuit, and that won't get you an rpm of the kernel, just the kernel itself.