A while ago I had requested help in this forum about the problems in compiling the LIRC
lirc_gpio module which could not be compiled using a stock kernel, due to the missing
bttv.h and
bttvp.h headers from the kernel-devel package. There were no helpful replies and I hadn't managed to find any other relative info, so i had quit. Today i got my hands on this problem once again and here is a general workaround for all such situations.
The kernel
SRC RPM contains the full fedora kernel sources. In order to use the kernel headers from this package (these are complete - no missing files) you have to do some preparation so that they match your
currently running kernel.
1 -
Download the kernel SRPM. Be sure that it's the same version as your running kernel
2 -
follow the instructions of the
fedora 4 release notes paragraph
7.2.2.3.
3 -
change to the directory
/usr/src/linux (the directory names are from the release notes instructions)
4-
Copy the
Module.symvers file from the default kernel headers. (assumes that the kernel config hasn't been edited): [
UPDATE]
Code:
# cp /usr/src/kernels/$(uname -r)-$(arch)/Module.symvers .
Step 4 is needed so that the third party modules we compile have proper dependency information.
5 - Run the following command inside this directory: [
UPDATE]
Code:
# make prepare scripts
The last command is more general and complete than making each file individually (as I had written previously).
What you gain with this is that
1- you have the
complete kernel headers in this directory which can be used to build modules for the currently running kernel
2- you do not have to compile the whole kernel in order to use the headers
What this small howto assumes is that you
do not modify the kernel configuration. In such a case a full compilation of the kernel sources is needed.
Now, for example, when you need to build lirc_gpio, just use these complete headers, instead of those of the kernel-devel.
These instructions can also be found with more detail in this small article i have written:
http://www.raoul.shacknet.nu/2005/12...ernel-headers/
My technical knowledge cannot provide any guarantee that this will work for you.
Enjoy!