-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2010-03-11 at 21:39 +0200, Stan Goodman wrote:

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?

In YaST, the pattern "basic development" or something similar. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkuZUikACgkQtTMYHG2NR9V20QCeMx7jXNkjM+ulv+lj6cyk24BR YvcAn27csgDSArRoI6AhhhKDjdqZF39A =1lrJ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

At 23:01:05 on Thursday Thursday 11 March 2010, Martin Jungowski wrote:

On Thu, 11 Mar 2010 21:39:48 +0200 Stan Goodman wrote:

...

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?

According to the error message the gcc command could not be found. What happens when you open a terminal and start "gcc"? Maybe you wanna try to reinstall gcc?

:~> gcc gcc: no input files :~> I will reinstall if Carlos's suggestion doesn't turn up anything. I am very surprised at the lack of gcc, because the system must have used it when it installed the ose version of Vbox a long time ago.

Martin

-- Rieke Computersysteme GmbH Hellerholz 5 D-82061 Neuried Email: martin@rhm.de

-- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

At 23:48:39 on Thursday Thursday 11 March 2010, Patrick Shanahan wrote:

* Stan Goodman [03-11-10 16:15]:

...

At 23:01:05 on Thursday Thursday 11 March 2010, Martin Jungowski

wrote:

...

According to the error message the gcc command could not be found. What happens when you open a terminal and start "gcc"? Maybe you wanna try to reinstall gcc?

:~> gcc

gcc: no input files

:~>

I will reinstall if Carlos's suggestion doesn't turn up anything.

Why would you reinstall. gcc responded, ie: It *is* installed.

You are asking the wrong man. It was a suggestion made by Carlos. I'm open to any suggestion from people who know more than I do.

...

I am very surprised at the lack of gcc, because the system must have used it when it installed the ose version of Vbox a long time ago.

rpm -q gcc

:~> rpm -q gcc gcc-4.3-34.243 :~>

you know not what you have.

And worse, I know not what the error message is trying to tell me. All the above has been on my desktop machine. In the past hour, I tried to install the same rpm on the laptop, which according to YaST, has exactly the same gcc-related packages as the desktop. After a false start to install kernel-sources and then to run (twice, because the first time seemed not to have got as far as leaving an executable file) the laptop machine has a running Vbox. In a perfect world, so would the desktop machine. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

At 06:17:20 on Friday Friday 12 March 2010, "Brian K. White" wrote:

Stan Goodman wrote:

...

At 21:12:20 on Thursday Thursday 11 March 2010, 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".

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

At 03:16:08 on Saturday Saturday 13 March 2010, Jos van Kan wrote:

Stan Goodman schreef: (snip)

...

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.

You could try

CC=$(which gcc) make

If make can't find gcc it must be in some outlandish place and that is what deleting and reinstalling it could repair. If it is in its normal place (/usr/bin) then something is really broken in your setup.

# CC=$(which gcc) make make: *** No targets specified and no makefile found. Stop. So that gcc can be found, which I think was not in doubt.. # find -name "gcc" ./usr/share/virtualbox/src/vboxdrv/math/gcc ./usr/share/virtualbox/src/vboxnetadp/math/gcc ./usr/share/virtualbox/src/vboxnetflt/math/gcc ./usr/lib64/gcc ./usr/bin/gcc ./tmp/vbox.0/math/gcc ./tmp/vbox.1/math/gcc The first three, and also the last two, are directories, all containing identical files, even with the same date. The next two are expected, and there are no duplicates. No doubt I can discard the tmp directories; can some of the others go? Is this likely to be the problem? -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Hello, In the Message; Subject : Re: [opensuse] Installing RPM, unable to compile Message-ID : <201003131109.29032.stan.goodman@hashkedim.com> Date & Time: Sat, 13 Mar 2010 11:09:28 +0200 [Stan] == Stan Goodman has written: [...] Stan> # find -name "gcc" Stan> ./usr/share/virtualbox/src/vboxdrv/math/gcc Stan> ./usr/share/virtualbox/src/vboxnetadp/math/gcc Stan> ./usr/share/virtualbox/src/vboxnetflt/math/gcc Stan> ./usr/lib64/gcc Stan> ./usr/bin/gcc Stan> ./tmp/vbox.0/math/gcc Stan> ./tmp/vbox.1/math/gcc Stan> The first three, and also the last two, are directories, all containing Stan> identical files, even with the same date. The next two are expected, and Stan> there are no duplicates. No doubt I can discard the tmp directories; can Stan> some of the others go? Is this likely to be the problem? Maybe, gcc means "/tmp/vbox.2/math/gcc". Anyway, # rm -rf /tmp/vbox.* Then, try to install VBox 3.1.4. Regards, --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ 「私たちが今日直面している化学物質の危険性に関する疑問に対し、通常の 科学的な正確さをもって答えようとすれば、たぶんさらに数十年を要するで あろう。」 -- J. V. Rodricks -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

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