building from kernel source rpm

[Rick Stevens]

On 11/27/2012 06:06 PM, Brian West issued this missive:
> On 11/27/2012 07:44 PM, JD wrote:
>> Hi Bruno, Alan,
>>
>> The rpmbuild interface does not provide the user a way
>> to go through the entire config options before proceeding
>> to build the kernel. If it does, I would really like to know
>> how it's done.
>>
>> The current rpmbuild of the kernel builds bazillions of
>> drivers, most of which are very likely not needed by
>> the user's platform. This leads to an extremely time
>> consuming default build, and in my case, I have only
>> one machine which is a unicore.
>>
>> Other problems are features that a user might neither
>> want nor need.
>>
>> Is there a way to propagate this issue to development leads?
>>
>> Thanx.
> i second that this would be nice so that we can tailor our kernels to
> our config and not have unrequired drivers.

rpmbuild's "-ba" option is there to create full binary and source
kernel RPMs. By definition, most modules will be built because that's
how the kernel is distributed. If you want to limit what gets built,
you have to change the build's config file. There's nothing mysterious
about it and the process hasn't changed in at least four years.

Start using the "-bp" option to rpmbuild. After that, go into your
~/rpmbuild/BUILD/kernel-xxx/linux-xxx directory, run "make nconfig",
bugger the config there, save it and do the normal kernel make/make
install operations. Check the README file in that directory for options
on how to configure and how to compile.

Really, it's been like this for a LONG time.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital    ricks at alldigital.com -
- AIM/Skype: therps2        ICQ: 22643734            Yahoo: origrps2 -
-                                                                    -
-    If your broker is so damned smart...why is he still working?    -
----------------------------------------------------------------------