At 06:17:20 on Friday Friday 12 March 2010, "Brian K. White" <brian@aljex.com> wrote:
Stan Goodman wrote:
At 21:12:20 on Thursday Thursday 11 March 2010, Markus Koßmann
<mkossmann_ml1@gmx.de> 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".
According to YaST, the following packages related to gcc are installed: cpp43 gcc gcc43 gcc43-c++ gcc43-gij gcc-c++ gcc-gij libgcc43 libgcc43-32bit libgcj43
As I look at the list, I still think I have gcc installed, even granted that some of the above are for Java, which I assume is irrelevant. What other packages from the very long list might be necessary?
From another message it's clear that not only does the rpm database think that you have the gcc package installed, which is all that above shows, but there really is a gcc binary and it's even in your $PATH, since gcc responded "no input files" .
But, this error shows that in the environment set up by rpm to do installs, gcc is not in PATH. "make" and "/bin/sh" couldn't find gcc. I don't know off hand where that is defined for rpm if it doesn't simply come from your own environment before running rpm.
In the absence of advice, I do not have the foggiest notion of what to do about that tangle. If gcc is indeed in $PATH, I don't see that deleting and then reinstalling it can help. Nor do I know how to coax make to see it. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org