Hi!
Today there was an update for linux-kbuild-3.10 (3.10-1 to 3.10-2), not
sure, if it is the point, but.
GNUmd:/home/noroot#
echo $KBUILD_VERBOSE
1
GNUmd:/home/noroot#
aptitude install linux-image-3.10-1-686-pae linux-headers-3.10-1-686-pae
***
Examining /etc/kernel/header_postinst.d.
run-parts: executing /etc/kernel/header_postinst.d/dkms 3.10-1-686-pae
Error! Bad return status for module build on kernel: 3.10-1-686-pae (i686)
Consult /var/lib/dkms/nvidia/319.32/build/make.log for more information.
***
It seems, like the problem is no more present, sorry for troubling :)
GNUmd:/home/noroot#
dkms build -k 3.10-1-686-pae v4l2loopback/0.7.0
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area....
make KERNELRELEASE=3.10-1-686-pae -C /lib/modules/3.10-1-686-pae/build
M=/var/lib/dkms/v4l2loopback/0.7.0/build....
cleaning build area....
DKMS: build completed.
GNUmd:/home/noroot#
gcc --version
gcc (Debian 4.8.1-6) 4.8.1
Copyright (C) 2013 Free Software Foundation, Inc.
GNUmd:/home/noroot#
dkms status
nvidia, 319.32, 3.9-1-686-pae, i686: installed
v4l2loopback, 0.6.3, 3.10-1-686-pae, i686: built
v4l2loopback, 0.7.0, 3.10-1-686-pae, i686: built
v4l2loopback, 0.7.0, 3.9-1-686-pae, i686: installed
vboxhost, 4.2.16, 3.10-1-686-pae, i686: installed
vboxhost, 4.2.16, 3.9-1-686-pae, i686: installed
2013/7/18 IOhannes m zmölnig <zmoel...@iem.at>
> On 07/18/13 09:26, IOhannes m zmoelnig wrote:
> > On 2013-07-18 00:50, Трезвый Дворник wrote:
> > It seems, like is not v4l2loopback-dkms problem, have same
> >> dealings with other dkms'es
> >
> > thanks. that's good to know.
>
> hmm, i updated to 3.10 today, and indeed i'm having problems as well,
> e.g. with the proprietary fglrx drivers.
> however, looking at the make.log for the failed build, it seems that
> fglrx is indeed broken for that kernel.
> while i haven't followed recent kernel development, it might be that
> they just added/removed a bunch of things, thus forcing all external
> modules to be updated.
> this would mean that each affected module is indeed buggy and bugs
> should be reported.
>
> >
> > your log-file is a quite generic (which is not your fault), but
> > indicates at a problem with the compiler rather than with the module
> > or the kernel.
> >
> > anyhow, i guess it is time for me to install 3.10 :-)
>
> however, it seems that i do not have problems building v4l2loopback on
> an amd64 machine:
>
> # KBUILD_VERBOSE=1 dkms build -k 3.10-1-amd64/x86_64 v4l2loopback/0.7.0
> Kernel preparation unnecessary for this kernel. Skipping...
> Building module:
> cleaning build area....
> make KERNELRELEASE=3.10-1-amd64 -C /lib/modules/3.10-1-amd64/build
> M=/var/lib/dkms/v4l2loopback/0.7.0/build.....
> cleaning build area....
> DKMS: build completed.
>
> # ls /var/lib/dkms/v4l2loopback/kernel-3.10-1-amd64-x86_64/module/
> v4l2loopback.ko
>
>
> so maybe you have some other problems, e.g. with your compiler.
> does the gcc used for compiling the kernel/module actually work?
>
> the following only works because i have run dkms with the
> "KBUILD_VERBOSE=1" environment:
> $ grep gcc
> /var/lib/dkms/v4l2loopback/0.7.0/3.10-1-amd64/x86_64/log/make.log | awk
> '{print $1}'
> gcc-4.7
>
> $ gcc-4.7 --version
> gcc-4.7 (Debian 4.7.3-6) 4.7.3
>
> if this doesn't reveal anything, please post the make.log after you run
> dkms with KBUILD_VERBOSE=1.
> (check the make.log before posting; it should have plenty of complicated
> gcc calls in there, instead of the elegant "CC [M]" in your original
> make.log)
>
> fgmadsr
> IOhannes
>
>
