Hello,

We needed to compile a custom Kernel provided by a hardware vendor and would like to produce RPM files for this kernel so that we can subsequently deploy them to other host machines quickly.

We have successfully built the kernel using the standard series of commands :-

patch
make menuconfig
make rpm-pkg
mkinitrd


However, once our new kernel is deployed we cannot compile any source code because we not have the kernel header files for this custom kernel.

My colleague was able to produce these by manually building the kernel with 'make bzImage modules' but tells me that 'make rpm-pkg' does produce the header files during the build, but but not retain them.

My question is can 'make rpm-pkg' be told to retain the header files along with the RPM files it creates so that these are available for compiling software on the machines running the custom kernel.


Sorry if this is an obvious question. I have tried searching prior to posting this.


Many Thanks,



Max.

I thought 'make rpm-pkg' made .src.rpms while it built the .rpm... If it doesn't (do check) then you could run 'make -n rpm-pkg' to see what commands it runs, create a shell script with those commands and substitute the 'rpmbuild' line to build you the .src.rpm (should be the "-bs" switch AFAIK). Not the most elegant way of doing things but it shouldn't be an impossible task either.


//NTLB

How did you go with this maxvonseibold

The src.rpm created just contains a tarball of the source files and a kernel.spec file. Not bad for rebuilding the kernel but does not serve the need of building other software that needs kernel source.

I have created SRC RPMs manually by unpacking this tarball and making my own spec file but I too was hoping there is way/command in the "make rpm" stage.

Thanks