new release? (because timer api change)

[xlotlu]

Hi guys, this isn't really a bug report because you fixed things already:
4.15 is starting to land in distros, and building fails because of the api change which you handled in 00eb0df.

I'm gonna file a bug report with debian about this. Do you intend to make a release soon, or should I ask them to apply the patch?

P.S.: thanks for the software.

• v4l2loopback version: 0.10.0
• kernel version: 4.15.4
• Distribution (+version): Debian unstable

Building v4l2-loopback driver...
make -C /lib/modules/4.15.0-1-amd64/build M=/var/lib/dkms/v4l2loopback/0.10.0/build modules
make[1]: Entering directory '/usr/src/linux-headers-4.15.0-1-amd64'
  CC [M]  /var/lib/dkms/v4l2loopback/0.10.0/build/v4l2loopback.o
/var/lib/dkms/v4l2loopback/0.10.0/build/v4l2loopback.c: In function ‘v4l2_loopback_init’:
/var/lib/dkms/v4l2loopback/0.10.0/build/v4l2loopback.c:2206:2: error: implicit declaration of function ‘setup_timer’; did you mean ‘setup_irq’? [-Werror=implicit-function-declaration]
  setup_timer(&dev->sustain_timer, sustain_timer_clb, nr);
  ^~~~~~~~~~~

[shark0der]

Are there any news regarding this? Almost 3 months have passed and I'm still unable to build it. I'm using Ubuntu 16.04 with 4.15.0-22-generic.

[umlaeute]

this has been closed because the issue was supposedly fixed with the v0.11.0 release, 2 months ago.

[shark0der]

I was able to build by cloning the repo. The xenial release is outdated: 0.9.1-4.

[umlaeute]

well, no.

afaict, xenial comes with linux-4.4, which should work nicely with v4l2loopback-0.9.1.
if you choose to manually add incompatible components, then it's your own responsibility to fix (in this case: upgrade) any reverse dependencies manually.

[shark0der]

By default, it indeed comes with 4.4. Not entirely sure what you mean by manually. I did not compile or manually download a new kernel - I've installed the linux-image-generic-hwe-16.04-edge package which comes with 4.15 (it's in the official repo).

[umlaeute]

well in any case, your problem is (was) an ubuntu packaging issue. unrelated to v4l2loopback upstream development (or release cycles).

[shark0der]

Understood. Thanks.

…

On Fri, Jun 1, 2018, 18:47 umläute ***@***.***> wrote: well in any case, your problem is (was) an ubuntu packaging issue. unrelated to v4l2loopback upstream development (or release cycles). — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#158 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAgSP7kFgFkEmjWaS4I3QjepOdiUpKLAks5t4WH_gaJpZM4Sd4QY> .