On my AMD64 while emerging db-4.2.52_p2-r1 in the configuring-process, I got the "cannot create executable" error with the hint in config.log: ... x86_64-pc-linux-gnu-cc: gcc-config error: x86_64-pc-linux-gnu-cc wrapper: Unable to determine executable. CTARGET=x86_64-pc-linux-gnu exec=gcc ... I got this error all the time if I run "x86_64-pc-linux-gnu-cc" from any terminal. I thought of an problem with my gcc-profile, so I tried: hcompneu ~ # gcc-config -l [1] x86_64-pc-linux-gnu-3.4.6 [2] x86_64-pc-linux-gnu-3.4.6-hardened [3] x86_64-pc-linux-gnu-3.4.6-hardenednopie [4] x86_64-pc-linux-gnu-3.4.6-hardenednopiessp [5] x86_64-pc-linux-gnu-3.4.6-hardenednossp [6] x86_64-pc-linux-gnu-4.1.1 * hcompneu ~ # gcc-config 6 * Switching native-compiler to x86_64-pc-linux-gnu-4.1.1 ... This doesn't make any change. I also tried to switch to my 3.4.6 but the error was the same all the time. From some similar problem with i686-pc-linux-gnu-g77 (bug 136363), I got the tipp to re-emerge gcc-config, so: hcompneu ~ # emerge --oneshot gcc-config Calculating dependencies... done! >>> Emerging (1 of 1) sys-devel/gcc-config-1.3.13-r3 to / >>> Unpacking source... >>> Source unpacked. >>> Compiling source in /var/tmp/portage/gcc-config-1.3.13-r3/work ... >>> Source compiled. >>> Test phase [not enabled]: sys-devel/gcc-config-1.3.13-r3 >>> Install gcc-config-1.3.13-r3 into /var/tmp/portage/gcc-config-1.3.13-r3/image/ category sys-devel >>> Completed installing gcc-config-1.3.13-r3 into /var/tmp/portage/gcc-config-1.3.13-r3/image/ man: strip: x86_64-pc-linux-gnu-strip --strip-unneeded usr/lib64/misc/gcc-config >>> Merging sys-devel/gcc-config-1.3.13-r3 to / --- /usr/ --- /usr/bin/ >>> /usr/bin/gcc-config --- /usr/lib64/ --- /usr/lib64/misc/ >>> /usr/lib64/misc/gcc-config >>> Safely unmerging already-installed instance... --- !mtime obj /usr/lib64/misc/gcc-config --- !mtime obj /usr/bin/gcc-config --- !empty dir /usr/lib64/misc --- !empty dir /usr/lib64 --- !empty dir /usr/bin --- !empty dir /usr >>> Regenerating /etc/ld.so.cache... >>> Original instance of package unmerged safely. * Switching native-compiler to x86_64-pc-linux-gnu-4.1.1 ... [ ok ]>>> Regenerating /etc/ld.so.cache... >>> sys-devel/gcc-config-1.3.13-r3 merged. >>> No packages selected for removal by clean. >>> Auto-cleaning packages... >>> No outdated packages were found on your system. * GNU info directory index is up-to-date. This re-emerge also seems to switch the gcc-profile to GCC 4.1.1, but it was different than before because now the file x86_64-pc-linux-gnu-cc has gone away: hcompneu ~ # ls /usr/bin/x86_64-pc-linux-gnu-cc ls: /usr/bin/x86_64-pc-linux-gnu-cc: No such file or directory So I tried to emerge sys-libs/db again, but no luck: ... checking for x86_64-pc-linux-gnu-cc... x86_64-pc-linux-gnu-cc checking for C compiler default output... configure: error: C compiler cannot create executables See `config.log' for more details. !!! ERROR: sys-libs/db-4.2.52_p2-r1 failed. Call stack: ebuild.sh, line 1546: Called dyn_compile ebuild.sh, line 937: Called src_compile db-4.2.52_p2-r1.ebuild, line 89: Called die !!! configure failed !!! If you need support, post the topmost build error, and the call stack if relevant. The config.log says this time: ... configure:3690: x86_64-pc-linux-gnu-cc -O2 -march=athlon64 -D_GNU_SOURCE -D_REENTRANT conftest.c >&5 x86_64-pc-linux-gnu-cc: No such file or directory configure:3693: $? = 1 configure: failed program was: | #line 3666 "configure" ... I got the same error before after I renamed this x86_64-pc-linux-gnu-cc. The error seems logical, but how is the solution? Did I miss some USE-flags of gcc? hcompneu ~ # emerge -pv gcc These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] sys-devel/gcc-4.1.1 USE="fortran gcj gtk multislot nls objc (-altivec) -bootstrap -build -doc (-hardened) -ip28 -ip32r10k -mudflap (-multilib) (-n32) (-n64) -nocxx -objc++ -objc-gc -test -vanilla" 20 kB -- Albert
Sorry, it seems to be a duplicate of bug 145946. But I don't see a real solution there, it seems that there is only the workaround to not use ccache for this emerge. *** This bug has been marked as a duplicate of 145946 ***
