... configure:1942: checking for i686-pc-linux-gnu-gcc configure:1958: found /usr/bin/i686-pc-linux-gnu-gcc configure:1968: result: i686-pc-linux-gnu-gcc configure:2250: checking for C compiler version configure:2253: i686-pc-linux-gnu-gcc --version </dev/null >&5 gcc-config error: i686-pc-linux-gnu-gcc wrapper: Could not determine which compiler to use. Invalid CTARGET or CTARGET has no selected profile. ... and so on. Details in the soon-to-be-attached log file. Note: I just switched to using x86_64-pc-linux-gnu-4.2.0, and I am running emerge -ev system All the other emerges (so far, 46 out of 440) are proceeding without error.
Created attachment 125527 [details] emerge --info
Created attachment 125528 [details] config.log
*** This bug has been marked as a duplicate of bug 133209 ***
As suggested in #133209: I ran binutils-config and it is set to x86_64-pc-linux-gnu-2.17, the latest version available. Running "find | xargs strings -f 2> /dev/null | grep 'Unable to determine executable' | cut -d : -f 1" produced no output. Running the emerge as "FEATURES=-sandbox emerge =sys-apps/sandbox-1.2.18.1" resulted in the same error. So I am reopening the bug.
*** This bug has been marked as a duplicate of bug 135688 ***