On 03/19/2011 04:02 PM, Konstantin Svist wrote: > On 03/19/2011 03:36 PM, stan wrote: >> On Sat, 19 Mar 2011 14:42:20 -0700 >> JD<jd1008@xxxxxxxxx> wrote: >> >>>> The -bp flag just unpacks the source so it can be examined or >>>> patches can be created. >>> Well, actually, -bp is for "prep"ing the source tree for compilation. >>> -bp will APPLY the patches (if they exist and are called for in the >>> spec file), rather than create them. >>> >> What you say is true, but it also can be used to *create* new patches >> if that is your inclination. The fedora wiki page for compiling a >> custom kernel has instructions on how to do this for the kernel. >> Obviously, the same general procedure can be used for any src.rpm. It >> requires modification of the spec file as well, and the patches have to >> be moved into the SOURCE directory. >> >> I know this works because I patch the kernel using that procedure, and >> it then creates RPMs with those patches in place. The 2.6.35 kernel >> source no longer compiles with SMP turned off unless it is patched and >> I experience lockups on my single core CPU unless I turn SMP off. > I've used the kernel compilation procedure from the wiki page [1] but > the sizes of the binaries are larger than the distro sizes > > > [1] http://fedoraproject.org/wiki/Docs/CustomKernel > > Ditto here!! I have NEVER been able to replicate the same kernel size. I have the latest F13 compiler...build tools...etc. And when building from SRPM's, I do not even create my own config file. I simply do: yum install kernel-2.6.xxxxx.source.rpm cd ...SPECS rpmbuild -vvv -bb kernel.spec and the resulting kernel size is larger than the same kernel binary from the repo. Why is that? Perhaps someone from the Fedora build team could shed some light on this. -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
