SCIENTIFIC-LINUX-USERS Archives

February 2008

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
markaoki <[log in to unmask]>
Reply To:
Date:
Tue, 26 Feb 2008 14:21:58 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (76 lines)
hi, its installed:

kernel-devel-2.6.18-8.1.3.el5.i686 "Development package for developing 
kernel modules to match the kernel".
kernel-headers-2.6.18-8.1.3.el5.i386 "Header files for the Linux kernel for 
use by glibc"

But, you know its the kernel itself that I am building, not a module, thus 
these are irrelevant.

I don't understand why the RPM build process would build everything 
perfectly, except for
the source output directory being named linux-2.6.18.i686 instead of the 
expected 2.6.18-8.1.3_test.el5-i686.

I decided to see if patches were applied beyond the 2.6.18 level and so 
unzipped "patch-2.6.18.4.bz" that was in SOURCES.

Then I picked at random a section patching Documentation/sysctl/vm.txt 
beginning on line 26 thus:

1    = Zone reclaim on
2    = Zone reclaim writes ...
4    = Zone reclaim swaps ...
-8  = Also do a global ...

I see in my BUILD/kernel-2.6.18/linux-2.6.18.i686 that the patch was applied 
(the last line was taken out), thus the directory name does not reflect the 
actual patch level of the source code.

It seems to be a bug :-\

-m

----- Original Message ----- 
From: "Akemi Yagi" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Tuesday, February 26, 2008 12:41 PM
Subject: Re: rpm kernel build question


> On Tue, Feb 26, 2008 at 12:35 PM, markaoki <[log in to unmask]> wrote:
>>
>>
>> hi,
>> I just dl'd & built a kernel source RPM ( 2.6.18-8.1.3.el5-i686 ) as I
>> needed to set some kernel
>> switches for a new driver.
>>
>> The rpm build process produced the exact RPMs that I expected, complete 
>> with
>> my little version
>> '_test' at the end.
>>
>> The system boots my new 2.6.18-8.1.3_test.el5 kernel just fine.
>>
>> The problem is that the rpm BUILD output dir only has linux-2.6.18.i686, 
>> and
>> my symlink
>> ( /lib/modules/2.6.18-8.1.3_test.el5/build ) is expecting a
>> 2.6.18-8.1.3_test.el5-i686
>> source directory. This symlink was set by the rpmbuild process.
>>
>> Any idea why the RPM build process produced a linux-2.6.18.i686 rather 
>> than
>> the expected 2.6.18-8.1.3_test.el5-i686
>> source code directory?
>>
>> Thanks, I appreciate any insight,
>> -m
>
> Need to install your version of kernel-devel ?
>
> Akemi
> 

ATOM RSS1 RSS2