On 10/23/07, Frank Mehnert <[EMAIL PROTECTED]> wrote: > > Brian, > > On Tuesday 23 October 2007, Brian Keener wrote: > > I have no idea what this guy is talking about, but here's my Virtualbox > on > > MDK 2008 experience: > > You are using the shipped VirtualBox 1.5.0, right? I think Richard > was talking about using our mdv2007.1 VBox 1.5.2 binary from > www.virtualbox.org.\
I tried the OSE version first, but I also tried two of the proprietary binary releases as well. > [...] > > > > Building modules, stage 2. > > make -f /usr/src/linux-2.6.22.9-desktop-1mdv/scripts/Makefile.modpost > > scripts/mod/modpost -i > > /usr/src/linux-2.6.22.9-desktop-1mdv/Module.symvers -I > > /tmp/vbox.11/Module.symvers -o /tmp/vbox.11/Module.symvers -w > > /bin/sh: scripts/mod/modpost: No such file or directory > > make[2]: *** [__modpost] Error 127 > > make[1]: *** [modules] Error 2 > > make[1]: Leaving directory `/usr/src/linux-2.6.22.9-desktop-1mdv' > > > > I can post the full error log if the above is insufficient. > > > > I get the same thing from the x86_64 .run file. > > Yes, it would be nice if you could post the complete log or send it to > me via private E-mail (frank at innotek dot de). > > Yes, that would have been nice, but I forgot to save that log file. What I can tell you is that it was definitely a kernel header problem of some sort or another, when I deleted the source tree and re-installed the kernel devel package it worked great.
_______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
