[Slackbuilds-users] Motion won't compile on -current or 14.2

[Sebastian Arcus]

I notice that Motion has been "magically" upgraded to 4.0.1 :-) However, 
it doesn't compile for me on either -current or 14.2. I get several 
errors as below - is this an incompatibility with gcc?

</snip>

x86_64-slackware-linux-gcc -O2 -fPIC -D_REENTRANT -I/usr/include 
-DMOTION_V4L2 -DTYPE_32BIT="int" -DHAVE_BSWAP    -Wall 
-DVERSION=\"4.0.1\" -Dsysconfdir=\"/etc\"     -c -o vloopback_motion.o 
vloopback_motion.c
vloopback_motion.c: In function ‘v4l_startpipe’:
vloopback_motion.c:181:26: error: storage size of ‘vid_pic’ isn’t known
      struct video_picture vid_pic;
                           ^~~~~~~
vloopback_motion.c:182:25: error: storage size of ‘vid_win’ isn’t known
      struct video_window vid_win;
                          ^~~~~~~
vloopback_motion.c:198:20: error: ‘VIDIOCGPICT’ undeclared (first use in 
this function); did you mean ‘VIDIOC_G_FMT’?
      if (ioctl(dev, VIDIOCGPICT, &vid_pic) == -1) {
                     ^~~~~~~~~~~
                     VIDIOC_G_FMT
vloopback_motion.c:198:20: note: each undeclared identifier is reported 
only once for each function it appears in
vloopback_motion.c:205:20: error: ‘VIDIOCSPICT’ undeclared (first use in 
this function); did you mean ‘VIDIOCGPICT’?
      if (ioctl(dev, VIDIOCSPICT, &vid_pic) == -1) {
                     ^~~~~~~~~~~
                     VIDIOCGPICT
vloopback_motion.c:210:20: error: ‘VIDIOCGWIN’ undeclared (first use in 
this function); did you mean ‘VIDIOCGPICT’?
      if (ioctl(dev, VIDIOCGWIN, &vid_win) == -1) {
                     ^~~~~~~~~~
                     VIDIOCGPICT
vloopback_motion.c:218:20: error: ‘VIDIOCSWIN’ undeclared (first use in 
this function); did you mean ‘VIDIOCGWIN’?
      if (ioctl(dev, VIDIOCSWIN, &vid_win) == -1) {
                     ^~~~~~~~~~
                     VIDIOCGWIN

I've also tried version 3.4.1 from 
here(https://github.com/Motion-Project/motion/releases/tag/release-3.4.1) 
with the same result. Searching online, there are a few bug reports with 
the above error message from 2012-2013 - so either it is a regression - 
or an unrelated new bug.