On Mon, 27 Mar 2006 16:24:01 +1200 Volker Kuhlmann <[EMAIL PROTECTED]> wrote:
> > NINE:~ # which gcc > > (nothing returned) > > First, shell lesson no. $N: > > Don't use which for locating binaries, it first runs up a csh(!) login > shell(!) and therefore changes $PATH according to your csh(!!!) login > configuration, then searches in $PATH for your binary. Obviously this > only gives you the same result if your csh setup is identical not only > to your bash setup (often distros don't manage that, though SUSE makes > an effort if I knock them hard), but also to whatever way you changed > $PATH manually since you started bash. In other words, which is a > useless command, forget it exists. It's probably only shipped for > eternal backwards compatibility. I disagree. This only true if you use [t]csh, and are calling it in the recommended way ( in fact, it uses source from the bash shell codebase to extract user info ). /usr/bin/which is an executable built from c source code, and calls no shells whatsoever ( getenv is about as close as it gets ) to perform it's function. For more details, man which will explain further. > > With tcsh, you use where - it displays a list of commands in $PATH, the > first one would be run. Unfortunately, sh has no complete equivalent to > where, but in bash, it's type -ap. You ought to alias type -ap to where > in bash. > > Now, to answer your question: > > You'll probably find that "where gcc" or "type -ap gcc" returns nothing. > This is a dead give-away, as is > > > NINE:~ # rpm -qa|grep gcc > > libgcc-4.0.2_20050901-3 > > which tells you that you don't have the compiler installed. Package gcc, > in yast somewhere under devlopment, or easier, type gcc into the search > field. > > When the vmware thingy told you it didn't find gcc, it was spot on > target ;) > > Volker > > -- > Volker Kuhlmann is list0570 with the domain in header > http://volker.dnsalias.net/ Please do not CC list postings to me. The only *guaranteed* way to find a file on your computer, irrespective of search path is to use find / -name gcc ( adding | xargs ls -ld also makes sense to give you some idea of what you've found ) as the (s)locate database may be out of date. http://www.novell.com/coolsolutions/feature/15963.html provides you with a list of the prerequisites for vmware, how to test for them, and how to install if they're missing. hth, Steve
