Happens with USE="v4l":
x86_64-pc-linux-gnu-gcc -march=core2 -O2 -msse4.1 -pipe -D_REENTRANT -DMOTION_V4L2 -DMOTION_V4L2_OLD -DTYPE_32BIT="int" -DHAVE_BSWAP -Wall -DVERSION=\""184.108.40.206"\" -Dsysconfdir=\"/etc\" -c -o netcam.o netcam.c
In file included from jpegutils.c:31:0:
motion.h:43:28: fatal error: linux/videodev.h: No such file or directory
If you build with USE="-v4l", then motion will only support IP based cameras. But the package *DOES HAVE* v4l2 (videodev2.h) support too, so it just means the v4lv1 and v4lv2 needs to be separate into their own configure flags etc. in the sources
Is there any update/workaround to solve this issue?
According to http://www.lavrsen.dk/foswiki/bin/view/Motion/BugReport2011x04x06x071405 a patch to separate v4l and v4l2 in configure is in svn but not yet in a release. For now, I have to work around this by masking >=linux-headers-2.6.28.
Understood! Thanks for the quick reply.
Worked around in 3.2.12's ebuild. Feel free to open a new bug for requesting adding motion svn snapshot to tree...
I wasn't suggesting an svn ebuild, but hoping that this particular fix could be implemented in 3.1.12. the current fix merely brute forces all V4L and V4L2 support off.
*** Bug 376019 has been marked as a duplicate of this bug. ***
I believe this bug should be reopened, and the v4l flag be removed/masked for the appropriate ebuild. The warning placed at the end of the ebuild is not at all sufficient.
I have been trying to get my camera working with motion the whole evening.