<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>_______________________________________________<br>mythtv-users mailing list<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br><a onclick="return top.js.OpenExtLink(window,event,this)" href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users" target="_blank">
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a></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.
<br></div><br></div><br>