> >I recently download gcc-2.6.3.bin.tar.gz and executed the commands:
> >cd /
> >gzip -dc gcc-2.6.3.bin.tar.gz | tar xvvf -
> >and it seemed to work ok, with the exception that now when I type `gcc'
> >at the command line, I get "gcc: command not found". If I type
> >`which gcc' it says /usr/bin/gcc, and gcc is mod 755, as it should be.
> >is going on here? Suddenly, I can't compile anything!
> >Please help! Thanks in advance.
>Not sure what shell you are using, but some shells "cache" the paths for
>executables in your path. When you change such a file you have to do a
>"rehash" command (tcsh) or equivalent to update the shell's internal
I've just had *exactly* the same experience! I tried logging out
then logging in again and all sorts of things... and still get
the "command not found" error. Weird.
I had only just installed 2.5.8 from the slackware distribution,
and for some reason it didn't work (I couldn't compile anything,
not even a simple "hello world"). So I tried for 2.6.3 and this
happens. Now I'm faced with deleting all the development stuff
from my hard drive and starting again fresh. :-(
Is there some way to install software in a manner that isn't so
brutal and crude as a gzip -dc | tar xvf - from the root
directory (or wherever)? So that it gets recorded nicely into
the /var/adm/* subdirs etc. Is there something magical about
.lsm files that allows this to happen?
_ ___ _ _ _ _
|\| / /\ __/\|(:)======================(:)=============================(:)
|=|/ / /\ \ |=||=| "There are three kinds of lies: lies, damn lies, |=|
|\/__/ \_\/ |\||\| and statistics." |\|
|=\__\/\ \ |=||=| - Mark Twain |=|
~ ~ ~ ~