Your message dated Thu, 29 Aug 2013 20:14:45 +0200
with message-id <[email protected]>
and subject line Re: Bug#721247: 4l2loopback-dkms: DKMS fails to build
v4l2loopback agains kernel, 3.10-0.bpo.2-amd64
has caused the Debian Bug report #721247,
regarding 4l2loopback-dkms: DKMS fails to build v4l2loopback agains kernel,
3.10-0.bpo.2-amd64
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
721247: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721247
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: v4l2loopback-dkms
Version: 0.6.1-1
Severity: important
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
Enabling Wheezy backports and upgrading the system to kernel
3.10-0.bpo.2-amd64.
DKMS fails to build v4l2loopback agains kernel 3.10-0.bpo.2-amd64.
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
run-parts: executing /etc/kernel/header_postinst.d/dkms 3.10-0.bpo.2-amd64
Error! Bad return status for module build on kernel: 3.10-0.bpo.2-amd64
(x86_64)
Consult /var/lib/dkms/v4l2loopback/0.6.1/build/make.log for more
information.
$ more /var/lib/dkms/v4l2loopback/0.6.1/build/make.log
DKMS make.log for v4l2loopback-0.6.1 for kernel 3.10-0.bpo.2-amd64 (x86_64)
Thu Aug 29 13:33:05 CEST 2013
make: Entering directory `/usr/src/linux-headers-3.10-0.bpo.2-amd64'
LD /var/lib/dkms/v4l2loopback/0.6.1/build/built-in.o
CC [M] /var/lib/dkms/v4l2loopback/0.6.1/build/v4l2loopback.o
/var/lib/dkms/v4l2loopback/0.6.1/build/v4l2loopback.c: In function
‘init_buffers
’:
/var/lib/dkms/v4l2loopback/0.6.1/build/v4l2loopback.c:2027:6: error: ‘struct
v4l
2_buffer’ has no member named ‘input’
/var/lib/dkms/v4l2loopback/0.6.1/build/v4l2loopback.c: At top level:
/var/lib/dkms/v4l2loopback/0.6.1/build/v4l2loopback.c:2230:3: warning:
initializ
ation from incompatible pointer type [enabled by default]
/var/lib/dkms/v4l2loopback/0.6.1/build/v4l2loopback.c:2230:3: warning: (near
ini
tialization for ‘v4l2_loopback_ioctl_ops.vidioc_s_std’) [enabled by
default]
/var/lib/dkms/v4l2loopback/0.6.1/build/v4l2loopback.c:2250:3: warning:
initializ
ation from incompatible pointer type [enabled by default]
/var/lib/dkms/v4l2loopback/0.6.1/build/v4l2loopback.c:2250:3: warning: (near
ini
tialization for ‘v4l2_loopback_ioctl_ops.vidioc_s_audio’) [enabled by
default]
/var/lib/dkms/v4l2loopback/0.6.1/build/v4l2loopback.c:2252:3: warning:
initializ
ation from incompatible pointer type [enabled by default]
/var/lib/dkms/v4l2loopback/0.6.1/build/v4l2loopback.c:2252:3: warning: (near
ini
tialization for ‘v4l2_loopback_ioctl_ops.vidioc_s_audout’) [enabled by
default]
make[3]: *** [/var/lib/dkms/v4l2loopback/0.6.1/build/v4l2loopback.o] Error 1
make[2]: *** [_module_/var/lib/dkms/v4l2loopback/0.6.1/build] Error 2
make[1]: *** [sub-make] Error 2
make: *** [all] Error 2
make: Leaving directory `/usr/src/linux-headers-3.10-0.bpo.2-amd64'
* What outcome did you expect instead?
*** End of the template - remove these lines ***
-- System Information:
Debian Release: 7.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.10-0.bpo.2-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages v4l2loopback-dkms depends on:
ii dkms 2.2.0.3-1.2
v4l2loopback-dkms recommends no packages.
Versions of packages v4l2loopback-dkms suggests:
ii v4l2loopback-utils 0.6.1-1
-- no debconf information
--- End Message ---
--- Begin Message ---
Tags: wontfix
On 08/29/13 14:19, Miro Moman wrote:
> Package: v4l2loopback-dkms
> Version: 0.6.1-1
> Severity: important
>
> Dear Maintainer,
> *** Please consider answering these questions, where appropriate ***
>
> * What led up to the situation?
>
> Enabling Wheezy backports and upgrading the system to kernel
> 3.10-0.bpo.2-amd64.
>
> DKMS fails to build v4l2loopback agains kernel 3.10-0.bpo.2-amd64.
yes, v4l2loopback-0.6.1 is incompatible with newer kernels.
you need v4l2loopback-0.7.0 (which is already in jessie) for kernel-3.10.
since you are using a backports-kernel, i don't think you can really
expect that all kernel-modules (found in your distribution, not in
backports) can work with any future kernel.
luckily you should be able to simply install the v4l2loopback-dkms
package from jessie.
gmfsdr
IOhannes
signature.asc
Description: OpenPGP digital signature
--- End Message ---
