If in some script the path to real gcc (/usr/i686-pc-linux-gnu/gcc-bin/3.4.3) is not set, /usr/bin/gcc never execs nothing. Only uses cpu forever. Reproducible: Always Steps to Reproduce: Two ways to doiit. Cooked: 1. As root: export PATH=/usr/bin 2. gcc -dumpversion 3. PROFIT! ;) Or, the way I discovered it: 1. emerge vmware-workstation 2. /opt/vmware/bin/vmware-config.pl 3. wait forever for script to check version of gcc Actual Results: High CPU usage. gcc -dumpversion never returns Expected Results: % gcc -dumpversion 3.4.3 % The path of root user is a vanilla one, that is, I have not added nothing to .bashrc nor .bash_profile. Current gcc version I am using is: i686-pc-linux-gnu-3.4.3 kernel gentoo-dev-sources-2.6.9-r9 Can be fixed using symlinks to binaries ;)
*** This bug has been marked as a duplicate of 74067 ***