[MPlayer-users] CVS compile tv-v4l2 input driver not detected/enabled
Barton Bosch
bartonbosch at gmail.com
Wed Dec 28 08:31:32 CET 2005
RC wrote:
>On Mon, 26 Dec 2005 10:57:20 -0800
>"bartonbosch at gmail.com" <bartonbosch at gmail.com> wrote:
>
>
>
>>Check configure.log if you wonder why an autodetection failed
>>
>>
>
>Doesn't anybody *read* the output (particularly the line above)?
>
>
Heh, got me! Mea culpa, I scanned the output of ./configure and missed
the reminder for configure.log (which, believe it or not, I generally
try to parse when I experience compile probs).
Now that you've pointed me to the relevant line I've tracked the
situation down a bit further. My semi-educated guess is that the v4l2
interface is not being detected because recent mplayer CVS cannot find
videodev2.h:
============ Checking for Video 4 Linux 2 TV interface ============
#include <stdlib.h>
#include <linux/types.h>
#include <linux/videodev2.h>
int main(void) { return 0; }
cc -o /tmp/mplayer-conf-24845-10019.o /tmp/mplayer-conf-885-10019.c
/tmp/mplayer-conf-885-10019.c:3:29: linux/videodev2.h: No such file or
directory
ldd /tmp/mplayer-conf-24845-10019.o
ldd: /tmp/mplayer-conf-24845-10019.o: No such file or directory
Result is: no
##########################################
Which is strange because the v4l2 headers are right there in the same
kernel source directory
(/lib/modules/2.6.12-1.1381_FC3/build/include/linux) as videodev.h,
which mplayer CVS does find:
============ Checking for Video 4 Linux TV interface ============
#include <stdlib.h>
#include <linux/videodev.h>
int main(void) { return 0; }
cc -o /tmp/mplayer-conf-24845-10019.o /tmp/mplayer-conf-885-10019.c
ldd /tmp/mplayer-conf-24845-10019.o
linux-gate.so.1 => (0x00844000)
libc.so.6 => /lib/tls/libc.so.6 (0x0069b000)
/lib/ld-linux.so.2 (0x00681000)
Result is: yes
##########################################
Sooo, having tracked it down a bit more, I find myself halted once
again. How would I go about getting recent mplayer CVS to be able to
find videodev2.h? Is there supposed to be a videodev2.ko driver in
addition to videodev.ko? Or is Fedora Core not playing nice with
mplayer CVS? Thanks for the help folks.
Barton
More information about the MPlayer-users
mailing list