On Sat, Sep 18, 2004 at 07:09:31AM -0500, D. Joe Anderson wrote: > On Fri, Sep 17, 2004 at 09:44:48PM -0700, Daniel & Kimberly Cotter wrote: > > > I don't want to be a pest > > Then a good place to start would be, at the very least, > to acknowledge previous attempts to help, viz: > > http://www.mail-archive.com/[EMAIL PROTECTED]/msg01428.html > > http://www.mail-archive.com/[EMAIL PROTECTED]/msg01429.html
OK, my bad. I see the attempt is there (I missed it because the threading and quoting and such is all screwed up somehow). The find command recommended was a good one, but a more thorough look would be: find / -name "gcc*" This would then catch files that begin with "gcc" but have something tacked onto the end. Again, I don't know if Mandrake is using anything like /etc/alternatives, but I heard Redhat was moving to that. On my Debian system, /usr/bin/gcc is just a symlink to a binary the name of which is the specific version: $ ls -ld /usr/bin/gcc lrwxrwxrwx 1 root root 8 Jul 27 2003 /usr/bin/gcc -> gcc-2.95 So, you might have the gcc package installed, but some magic that was supposed to happen at the end of the install to make a similar symlink got busted. So, what do you get if you just do: ls -ld /usr/bin/gcc* or if you do the find command as above? Also, I think I'd like to see the results of something like: rpm -qa | grep gcc to see more direct evidence that the system really thinks it has gcc installed. -- Joe --
