Markus Koßmann wrote:
Am Donnerstag, 11. März 2010 schrieb Stan Goodman:
To install VirtualBox v3.1.4, I have d/l the appropriate RPM file from the VM site. Running rpm -U <filename> gets a failure message directing me to inspect the logfile /var/log/vbox-install.log, which is as follows:
***** ** Compiling vboxdrv make KBUILD_VERBOSE= -C /lib/modules/2.6.27.45-0.1-default/build SUBDIRS=/tmp/vbox.2 SRCROOT=/tmp/vbox.2 modules make -C ../../../linux-2.6.27.45-0.1 O=/usr/src/linux-2.6.27.45-0.1-obj/x86_64/default/. modules make -C /usr/src/linux-2.6.27.45-0.1-obj/x86_64/default \ KBUILD_SRC=/usr/src/linux-2.6.27.45-0.1 \
KBUILD_EXTMOD="/tmp/vbox.2" -f /usr/src/linux-2.6.27.45-0.1/Makefile \ modules make[3]: gcc: Command not found CC [M] /tmp/vbox.2/linux/SUPDrv-linux.o /bin/sh: gcc: command not found make[4]: *** [/tmp/vbox.2/linux/SUPDrv-linux.o] Error 127 make[3]: *** [_module_/tmp/vbox.2] Error 2 make[2]: *** [sub-make] Error 2 make[1]: *** [all] Error 2 make: *** [vboxdrv] Error 2 *****
I do not understand what the trouble is. The installed kernel source, according to YaST is "linux-2.6.27.45-0.1.1". I see the two notations of missing commands, but it isn't clear what commands it is that are lacking.
You didn't install gcc , the C-Compiler and probably more packages needed for doing "Kernel-development".
Which is sort of saying it wrong. Stan is not at fault for failing to somehow know he needs to install gcc. The creator of that rpm should have included gcc in the requires section. Then depending on how it was actually being installed (manual rpm command, from within zypper or yast or some other rpm front-end, etc) the rpm would have pulled in gcc automatically, or at least would have issued a simpler and clearer (for regular users) error message that just said you need to install gcc first and it wouldn't have even tried to install just to fail half way through like that. -- bkw -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org