How to compile a soft same as the version realeased by fedora?

JD jd1008 at gmail.com
Sun Mar 20 01:57:30 UTC 2011


On 03/19/2011 03:36 PM, stan wrote:
> On Sat, 19 Mar 2011 14:42:20 -0700
> JD<jd1008 at gmail.com>  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.
OK! I have not tried to create patches using this method,
but will try it.
>    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.
Very interesting.
I have been building all my kernels with SMP disabled.
To wit, Here are the relevant config options in my
.config file for 2.6.38 (Mainline kernel), which I am
now running:
#
# Automatically generated make config: don't edit
# Linux/i386 2.6.38.0-1 Kernel Configuration
# Wed Mar 16 23:19:36 2011
#
# CONFIG_64BIT is not set
CONFIG_X86_32=y
# CONFIG_X86_64 is not set
CONFIG_X86=y
.
.
.
#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_BROKEN_ON_SMP=y
.
.
.
# CONFIG_SMP is not set

Cheers,

JD


More information about the users mailing list