I correct the typo:
So may you confirm that I should keep the new headers for step 1 and 2
and reinstall the old one after (as Kyle told me)?
On Fri, Oct 15, 2010 at 6:01 PM, Ryad Ben-El-Kezadri <ryad.bek(a)gmail.com>wrote:
Sorry, I was not clear enough:
I need to
1)first patch the NEW kernel (to have better time support. I want to add
the patch of Alexander Gordeev for better PPS(=Pulse Per Second) support)
2)then compile some apps in userland (mainly pps-tools which is needed by
LinuxPPS).
Specially the LinuxPPS group say concerning the installation of pps-tools*
"Optionally*, when we have older header files, we update the header files
using the versions from your new kernel.
$ cd /usr/include
$ mv linux linux.old
$ mv asm asm.old
$ mv asm-generic asm-generic.old
$ ln -s /lib/modules/$(uname -r)/build/include/linux linux
$ ln -s /lib/modules/$(uname -r)/build/arch/x86/include/asm asm
$ ln -s /lib/modules/$(uname -r)/build/include/asm-generic asm-generic"
So may can confirm that I should keep the new headers for step 1 and 2
and reinstall the old one after (as Kyle told me)?
Ryad
On Fri, Oct 15, 2010 at 5:27 PM, Josh Boyer <jwboyer(a)gmail.com> wrote:
> On Fri, Oct 15, 2010 at 11:19 AM, Ryad Ben-El-Kezadri
> <ryad.bek(a)gmail.com> wrote:
> > Indeed, I made a mistake:
> > the new headers are installed at the end of the installation process
> > with (see
http://fedoraproject.org/wiki/Docs/CustomKernel):
> > su -c 'rpm -ivh kernel-<version>.<arch>.rpm
> > kernel-firmware-<version>.<arch>.rpm
> > kernel-headers-<version>.<arch>.rpm
kernel-devel-<version>.<arch>.rpm'
> >
> > But still the problem is the same:
> > I need to
> > 1)first patch the kernel
> > 2)then compile some apps in userland
> >
> > and I do not know what kernel headers version (old or new) to use for
> step 1
> > and step 2.
> >
> > Ryad
> >
> > PS: here is what I got when I do
> > rpm -qa | grep kernel-headers
> > kernel-headers-2.6.33.3-85.fc13.i686
> > kernel-headers-2.6.35.6-43.fc13.i686
>
> If you don't know what kernel version you need to patch, we certainly
> won't either. Especially when we have no idea why you need to patch
> it, or what the patch does.
>
> Also, building applications against kernel headers is a practice that
> is generally discouraged overall.
>
> josh
>