<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><BR><DIV><DIV>On Jan 17, 2006, at 3:30 PM, Luke wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite">I have a situation here, while trying to compile and install lirc from source on FC4.<BR><BR><UL><LI>I have downloaded the latest kernel source for FC4 and it's installed at:<BR> <SPAN style="font-style: italic;">/usr/src/redhat/BUILD/kernel- 2.6.14/linux-2.6.14/</SPAN></LI><LI>I made a symbolic link like so:<BR><SPAN style="font-style: italic;"> ln -s /usr/src/redhat/BUILD/kernel-2.6.14/linux-2.6.14 /usr/src/linux</SPAN></LI><LI>running the script <SPAN style="font-style: italic;"> ./configure </SPAN>for lirc is successful</LI><LI>the make command generate errors, the first of which is:<BR><SPAN style="font-style: italic;">error: ../drivers/media/video/bttv.h: No such file or directory</SPAN><BR>Further errors below that are probably due to the missing bttv.h and similar files.</LI></UL><BR>I know the so-called missing header files exist at <SPAN style="font-style: italic;">/usr/src/redhat/BUILD/kernel-2.6.14/linux-2.6.14/drivers/media/video/* . </SPAN>Where is <SPAN style="font-style: italic;"> make</SPAN> looking for the header files. This looks straight forward but, I am lost. Any ideas?<BR></BLOCKQUOTE><BR></DIV><DIV>Well "make" is certainly not looking *there*, that's for sure. On my old FC3 system bttv.h is located in /usr/src/linux/drivers/media/video/</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Where /usr/src/linux is a link to the proper kernel tree, as your's is.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>You could simply move the file to that place, but I'm betting that would just cause a different error a little later when it failed to find the next header that it wants.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>You could also make a link from the actual location of the "drivers" to the similar position in the actual kernel tree, might work but it's hackneyed.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>You could also look at the output of "configure" and see where it *thinks* the headers are located, and either point it to the correct place or link that place to the actual location.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Of course, with recent kernel changes, the bttv.h file you have might not be usable or correct for the version of LIRC that you have :-)</DIV></BODY></HTML>