cannot find V4l2 API
- From: "Theodoros V. Kalamatianos" <thkala (at) softlab.ece.ntua.gr>
- Date: Wed, 8 Mar 2006 01:27:37 +0200 (EET)
On Tue, 7 Mar 2006, Luo Chris wrote:
Hi,
Here is my problem.
I updated my kernel with V4L2 patch into 2.4.26. After that I try to compile
an application based on V4L2. But it seemed that thing did not find the V4L2
API in my computer. It turned out the compiling message:
V4L2Device.cc: In static member function `static void
V4L2Device::printCapabilities(FILE*, v4l2_capability)':
V4L2Device.cc:41: error: 'struct v4l2_capability' has no member named
'driver'
V4L2Device.cc:41: error: 'struct v4l2_capability' has no member named 'card'
V4L2Device.cc:43: error: 'struct v4l2_capability' has no member named '
capabilities'
bla, bla, bla.... The messages was all about V4L2 APIs. It looked like as if
I did not install V4L2 correctly.
So, I update my kernel into 2.6.10. The one has included V4L2 already.
It turns out the same problem.
That's expected... Applications do not use kernel headers directly, but
rather the header set glibc was compiled with. If that is really old, new
features - especially in rapidly evolving subsystems like V4L - are not
available.
I guess that you can always "persuade" your compiler to use the headers
from your current kernel, but this can have all sorts of results. A more
clean solution would be to update your glibc+header packages. Although
this is also not recommended unless it is accompanied by a full system
recompile/upgrade...
Personally I would suggest coaxing your compiler to use the raw kernel
headers from 2.6.x and if that fails (and you really want to compile that
application) upgrade your distribution. Do not just update the glibc
packages, unless you can handle random programs breaking here and there
for no apparent reason...
here is my modules.conf file discription about V4L. in 2.4.26
conl (at) chris:~/dl/videoserver> cat /etc/modules.conf | grep "video"
alias char-major-81 videodev
modules.conf has nothing to do with any compilation problems...
I hope this helped...
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request (at) redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list