I?m trying to build a 2.6.18-128.1.6.el5 kernel without kabichk. I have
downloaded the sources, installed the compiler, etc and ran the following
command
rpmbuild -bb --target=`uname -m` --without kabichk --with baseonly
--without debug \
--without debuginfo kernel-2.6.spec.
I had modified the .SPEC file according to the WIKI page
http://wiki.centos.org/HowTos/Custom_Kernel
I have NOT installed any patches that will break KABI, but I am wanting to
patch the kernel for SCST, and that will do it. Currently, I?m just trying
to get the beast to build. I have been successful getting this to work on
older versions like 2.6.18-92.1.22, but I have not had success with
?128.1.6. l. I have not worried about build errors at this point, because
I?m hoping someone can say, ?Just do this, and all will be well.?
I am relatively new to CentOS / RedHat, but I do have a significant amount
of Linux experience building kernels.
I am now trying to see if I can get the kernel to build with kabi in place.
Any pointers would be greatly appreciated. TIA.
--
Terry Hull
Network Resource Group, Inc. President
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.centos.org/pipermail/centos/attachments/20090413/6a5e7aa8/attachment-0002.html>
On Mon, Apr 13, 2009 at 3:53 PM, Terry Hull <tah at nrg-inc.com> wrote:> I?m trying to build a 2.6.18-128.1.6.el5 kernel without kabichk. ?I have > downloaded the sources, installed the compiler, etc and ran the following > command > > rpmbuild ?-bb --target=`uname -m` ?--without kabichk --with baseonly > --without debug \ > ????--without debuginfo kernel-2.6.spec. > > I had modified the .SPEC file according to the WIKI page > http://wiki.centos.org/HowTos/Custom_Kernel > > I have NOT installed any patches that will break KABI,If you know your custom kernel retains the kABI, I suggest you entirely skip the section of the Wiki article that deals with the kABI-related modifications. No only this will reduce the chance of making incorrect changes but also it is indeed a good idea to do kABI checking. If the build still fails, please post the last portion of the error log (or e-mail the whole log file to me). Akemi
On Mon, Apr 13, 2009 at 6:53 PM, Terry Hull <tah at nrg-inc.com> wrote:> I?m trying to build a 2.6.18-128.1.6.el5 kernel without kabichk. ?I have > downloaded the sources, installed the compiler, etc and ran the following > command > > rpmbuild ?-bb --target=`uname -m` ?--without kabichk --with baseonly > --without debug \ > ????--without debuginfo kernel-2.6.spec. > > I had modified the .SPEC file according to the WIKI page > http://wiki.centos.org/HowTos/Custom_KernelFor the most part, the build instructions on the link work for me. The only changes I do is to install rpmdevtools first, then run rpmdev-setuptree to create the rpmbuild directories and .rpmmacros file. The x86_64 also had a requirement for the unifdef package.> I have NOT installed any patches that will break KABI, but I am wanting to > patch the kernel for SCST, and that will do it. ?Currently, I?m just trying > to get the beast to build. ?I have been successful getting this to work on > older versions like 2.6.18-92.1.22, but I have not had success with > ?128.1.6. ?l. I have not worried about build errors at this point, because > I?m hoping someone can say, ?Just do this, and all will be well.? > > I am relatively new to CentOS / RedHat, but I do have a significant amount > of Linux experience building kernels. > > I am now trying to see if I can get the kernel to build with kabi in place. > > > Any pointers would be greatly appreciated. ?TIA.Any errors?
On 4/14/09 3:12 AM, in article bfa89a870904140112s490d223ch440cf009d20e88df at mail.gmail.com, "Akemi Yagi" <amyagi at gmail.com> wrote:> On Mon, Apr 13, 2009 at 8:08 PM, Terry Hull <tah at nrg-inc.com> wrote: >> >> >> On 4/13/09 7:01 PM, in article >> bfa89a870904131701i2afd9b41j78b53b0611a9e462 at mail.gmail.com, "Akemi Yagi" >> <amyagi at gmail.com> wrote: > >> The patches I need to make do break kABI. ?I just have not yet applied them. >> I was trying to get the base kernel to build before I added the complexity >> of patching it. > >>> If the build still fails, please post the last portion of the error >>> log (or e-mail the whole log file to me). >> >> I have attached a compressed log file. ?The errors seem to be in the build >> of OCFS. > > Thanks for the err log file. From the looks of it, the error is in the > code itself as you noted. So, that should have nothing to do with > kABI. > > I checked my own log for the kernel 128.1.6 building but did not see > anything (warnings and such) relating to ocfs2. You mentioned " have > NOT installed any patches that will break KABI". Have you installed > any patches at all, that is, patches that do not break kABI ? If so, > would any of them touch the ocfs code? > > AkemiNo, I have not added any patches at all to the source. I just modified the .spec file and compiled with the --without kabichk option. I also did not have any trouble building the kernel as long as kabichk was enabled. -- Terry Hull Network Resource Group, Inc. President
On 4/14/09 3:12 AM, in article bfa89a870904140112s490d223ch440cf009d20e88df at mail.gmail.com, "Akemi Yagi" <amyagi at gmail.com> wrote:> On Mon, Apr 13, 2009 at 8:08 PM, Terry Hull <tah at nrg-inc.com> wrote: >> >> >> On 4/13/09 7:01 PM, in article >> bfa89a870904131701i2afd9b41j78b53b0611a9e462 at mail.gmail.com, "Akemi Yagi" >> <amyagi at gmail.com> wrote: > >> The patches I need to make do break kABI. ?I just have not yet applied them. >> I was trying to get the base kernel to build before I added the complexity >> of patching it. > >>> If the build still fails, please post the last portion of the error >>> log (or e-mail the whole log file to me). >> >> I have attached a compressed log file. ?The errors seem to be in the build >> of OCFS. > > Thanks for the err log file. From the looks of it, the error is in the > code itself as you noted. So, that should have nothing to do with > kABI. > > I checked my own log for the kernel 128.1.6 building but did not see > anything (warnings and such) relating to ocfs2. You mentioned " have > NOT installed any patches that will break KABI". Have you installed > any patches at all, that is, patches that do not break kABI ? If so, > would any of them touch the ocfs code? > > AkemiIt may also be of note that I've done this on two separate machines. I guess I'm a little puzzled by this. It must be true that very few people actually have to turn off kABI, or this would have come up before. I know that I can turn off ocfs in the .config and see if there is anything else that does not build correctly. -- Terry Hull Network Resource Group, Inc.