cardoe@dlaptop ~ $ gcov gcc-config error: gcov wrapper: Could not determine which compiler to use. Invalid CTARGET or CTARGET has no selected profile. cardoe@dlaptop ~ $ gcc-config -l [1] i686-pc-linux-gnu-4.1.2 * cardoe@dlaptop ~ $ gcc-config 1 * gcc-config: Must be root. cardoe@dlaptop ~ $ sudo gcc-config 1 Password: * Switching native-compiler to i686-pc-linux-gnu-4.1.2 ... [ ok ] cardoe@dlaptop ~ $ sudo env-update >>> Regenerating /etc/ld.so.cache... cardoe@dlaptop ~ $ source /etc/profile cardoe@dlaptop ~ $ gcov gcc-config error: gcov wrapper: Could not determine which compiler to use. Invalid CTARGET or CTARGET has no selected profile. cardoe@dlaptop ~ $ gcc-config -l [1] i686-pc-linux-gnu-4.1.2 * It happens even if I provide gcov with a proper file.
It's those pesky eselect-compiler wrappers again - switching back from eselect-compiler to gcc-config leaves you with wrappers for various bits and bobs that gcc-config doesn't bother with, and you need to get rid of these extra wrappers when you revert to gcc-config (which you may have done a long time ago; the extra wrappers are on executables that aren't used very often). Anything in /usr/bin that contains the error string you report is an eselect-compiler wrapper, and can be ditched. You shouldn't need to re-emerge gcc, as things like 'gcov' will be found in the gcc path. *** This bug has been marked as a duplicate of bug 175523 ***
