Try:
Code:
rpm -qa | grep "^gcc-"
On my Redhat 9 system, this produces:
Code:
bash-2.05b$ rpm -qa | grep "^gcc-"
gcc-c++-3.2.2-5
gcc-3.2.2-5
gcc-g77-3.2.2-5
gcc-java-3.2.2-5
gcc-gnat-3.2.2-5
Having located the fact that gcc-3.2.2-5 is installed, try:
Code:
rpm -ql gcc-3.2.2-5 | grep "gcc$"
(substituting the actual version numbers.) On my Redhat 9 system, this produces:
Code:
bash-2.05b$ rpm -ql gcc-3.2.2-5 | grep "gcc$"
/usr/bin/gcc
/usr/bin/i386-redhat-linux-gcc
I don't know why Redhat puts /usr/bin/i386-redhat-linux-gcc, but it is identical with /usr/bin/gcc.
Then use the "ls" command to verify that gcc is where the package thinks it is. It is possible that the gcc package was installed but someone deleted gcc manually?
Now, after you have located gcc, you should verify that it is actually able to compile a program, for example the simple "Hello, World" program found in all C texts. The reason for this is that ./configure does this to verify that the gcc it finds is actually able to compile a program. If you are missing the assembler (as) or the linker (ld), it will complain about it not being able to find an
acceptable C compiler.
