I'm a bit confused about the snipped you post: if I understand right, the point is that " kbuild is not meant to build vbox kernel modules". So to build the modules I'm supposed to do something like ./configure make make install ? is that right?
if so, i think that this bug should be reassigned to virtualbox-source package rather than closed. The reason is that inside the source shipped with virtualbox-source there is a rule file full of "kmk rules" that should be converted to the standard "make rules". Otherwise I don't see the reason of having a virtualbox-source package that fail to build the vbox module with m-a and that, as far as I know, is used only by module-assistant. correct me if I'm wrong Lorenzo 2015-05-13 12:08 GMT+02:00 Gianfranco Costamagna < costamagnagianfra...@yahoo.it>: > I talked on irc with virtualbox/upstream folks (who always have the best > solution :) ) > > > this is a snippet of the conversation: > -I don't think this has anything to do with kBuild which we use to compile > the VirtualBox source code. > -don't think anyone ever promised that one can mix and match kbuild and > vbox... we define in our repo (or the tarball) what's known to work. if you > use anything else you're on your own, and most likely out of luck. > -When compiling the Linux kernel modules, kBuild is not / should not be > used at all. The Linux kernel modules are built with the Linux kernel make > system. > -I don't know. For VirtualBox 4.3 we are currently using r2780, for 5.0 > Beta we are using r2782. > -The kernel modules need to be compiled with the Linux build system and > this has nothing to do with kBuild. > -Perhaps he does 'alias make=kmk' which he should not do. > -The VirtualBox kernel modules are just external Linux kernel modules. > They exist on their own and don't need the VirtualBox sources nor the > kBuild system. > -it might use kbuild for "extracting" them from the full vbox tree. we > don't define any other way. > -We do. src/VBox/HostDrivers/linux/export_modules is the official way for > exporting the Linux modules from our tree. > -And for the Additions this is src/VBox/Additions/linux/export_modules. We > did both years ago for the Debian folks :-) > > > > so seems that what you are trying to achive isn't supported, I'm tempted > to close this bug... > > thanks, > > Gianfranco > > > > Il Mercoledì 13 Maggio 2015 10:40, lorenz lor <lorenzo.r...@gmail.com> ha > scritto: > > > > Hi Gianfranco, > thank you for your reply. > With version 1:0.1.9998svn2745+dfsg-1 I can do the build without any > problem. > > Lorenzo > > > 2015-05-13 9:07 GMT+02:00 Gianfranco Costamagna < > costamagnagianfra...@yahoo.it>: > > Hi Lorenzo, in order to bisect the problem, would be nice if you could test > >version 1:0.1.9998svn2745+dfsg-1 and 1:0.1.9998svn2734+dfsg-1 in > experimental > > > > > >you can grab them from snapshots [1] if needed. > > > >thanks a lot, > > > >Gianfranco > > > > > >[1] http://snapshot.debian.org/package/kbuild/ > > > > > > > > > > > >Il Mercoledì 13 Maggio 2015 0:48, Lorenzo <lorenzo.r...@gmail.com> ha > scritto: > >Package: kbuild > >Version: 1:0.1.9998svn2780+dfsg-1 > >Severity: important > > > >Dear Maintainer, > > > >when I try to build virtualbox kernel modules using > ># m-a build virtualbox-source > >the build fails with the following error: > > > > CC [M] /usr/src/modules/virtualbox/vboxdrv/r0drv/memobj-r0drv.o > >│ CC [M] > /usr/src/modules/virtualbox/vboxdrv/r0drv/mpnotification-r0drv.o > >│ CC [M] > >│ /usr/src/modules/virtualbox/vboxdrv/r0drv/powernotification-r0drv.o > >│ ld: cannot open linker script file > >│ /usr/src/modules/virtualbox/vboxdrv/r0drv/.tmp_: No such file or > directory > >│ kmk[3]: *** > >│ [/usr/src/modules/virtualbox/vboxdrv/r0drv/mpnotification-r0drv.o] > Error 1 > >│ kmk[3]: *** Waiting for unfinished jobs.... > >│ kmk[3]: Leaving directory `/home/ombra/Downloads/linux-van-4.0.1' > >│ kmk[3]: Entering directory `/home/ombra/Downloads/linux-van-4.0.1' > >│ kmk[3]: *** Exiting with status 2 > >│ kmk[2]: *** [/usr/src/modules/virtualbox/vboxdrv] Error 2 > >│ kmk[2]: Leaving directory `/home/ombra/Downloads/linux-van-4.0.1' > >kmk[1]: *** [_module_/usr/src/modules/virtualbox] Error 2 > >│ kmk[1]: Leaving directory `/home/ombra/Downloads/linux-van-4.0.1' > >│ kmk: *** [binary-modules] Error 2 > >│ /usr/share/modass/include/common-rules.make:56: recipe for target > >│ 'kdist_build' failed > >│ make: *** [kdist_build] Error 2 > > > >Note that this problem is related to kbuild and m-a but does not affect > the dkms building system. > >I file this bug against kbuild because downgrading m-a itself or > virtualbox-source package to a previuos version doesn't solve the problem, > while downgrading kbuild to the stable version (1:0.1.9998svn2695+dfsg-2) > allow me to build virtualbox modules. > > > >Thanks > > > >Lorenzo > > > > > >-- System Information: > >Debian Release: stretch/sid > > APT prefers unstable > > APT policy: (500, 'unstable') > >Architecture: amd64 (x86_64) > > > >Kernel: Linux 4.0.1-van (SMP w/2 CPU cores; PREEMPT) > >Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > >Shell: /bin/sh linked to /bin/dash > >Init: sysvinit (via /sbin/init) > > > >Versions of packages kbuild depends on: > >ii libc6 2.19-18 > > > >kbuild recommends no packages. > > > >kbuild suggests no packages. > > > >-- no debconf information > > >
