On Sunday 10 May 2009 20:56:47 Frank Mehnert wrote: > David, > > On Sunday 10 May 2009, David Baron wrote: > > On Sunday 10 May 2009 11:46:55 Frank Mehnert wrote: > > > David, > > > > > > On Saturday 09 May 2009, David Baron wrote: > > > > Trying to build the vboxdrv.ko for an rt-patched kernel. For some > > > > reason, the script is trying to (or thinks it sees) the unpatched > > > > version. > > > > > > > > m-a built modules do not have this problem. > > > > > > which VBox package did you install on which Linux distribution? > > > Wild guess: If you are talking about the Debian OSE version please, > > > please ask at the Debian mailing list. > > > > Debian Lenny version from Sun's site. > > However, could be a Debian problem so will CC to there as well. > > Did you patch the kernel yourself? How did you install the kernel? > In general, /lib/modules/$(uname -r)/build should be a symlink to > the kernel sources of your currently running kernel. Don't create > this link yourself but install the proper kernel-headers package > which creates this link.
and this was indeed the problem. Since the sources were sources I patched, I did set the proper symlink manually and the the thing plays. How did I get the wrong symlink there? There have been problems of this nature in versions of kernel-package, I believe, which have presumably been fixed (?). _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
