<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><DIV><SPAN class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-align: auto; -khtml-text-decorations-in-effect: none; text-indent: 0px; -apple-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><BR class="Apple-interchange-newline"></SPAN> </DIV><BR><DIV><DIV>On Jan 18, 2006, at 5:49 AM, Luke wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><BR><BR><DIV><SPAN class="gmail_quote">On 18/01/06, <B class="gmail_sendername">Brian Wood</B> <<A href="mailto:beww@beww.org">beww@beww.org</A>> wrote:</SPAN><BLOCKQUOTE class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <DIV><SPAN class="e" id="q_108da9c456e86cae_0"><BR><DIV><DIV>On Jan 17, 2006, at 3:30 PM, Luke wrote:</DIV><BR><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></SPAN></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></DIV><DIV>Where /usr/src/linux is a link to the proper kernel tree, as your's is.</DIV><DIV><BR></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></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></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></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> <BR></BLOCKQUOTE><DIV><BR>It appears this is a kernel 2.6.14. Since this is so new, there is no patch for it yet from <A href="http://lirc.org">lirc.org</A>. Maybe I should wait for a patch. </DIV></DIV></BLOCKQUOTE><BR></DIV><DIV>The kernel version per se shouldn't be a problem. I was running 2.6.14 on a Gentoo system that worked just fine with what they were calling lirc version 0.8.0_pre1 (before a HDD crash took the system down that is).</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Gentoo has a version " lirc-0.8.0_pre3" that is claimed to have modifications for the 2.6.15 kernel, all I know about it is that it does not appear to work with 2.6.14.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>But your header location problems should not be directly related to kernel version, more likely to a squirrely installation of kernel sources, a problem I've had with FC systems in the past.</DIV><BR></BODY></HTML>