I'm filing this bug (from a template, mind you) because the ebuild I'm reporting it against failed to build once I removed my /usr/bin/{gcc,cc,c++,c99} binaries. This means that the ebuild is relying on gcc or cc as compiler, while it should use "$(tc-getCC)" so that user choices are respected, and cross-compiling works as intended. This usually comes down to one of these tasks: - use emake CC="$(tc-getCC)" for building, to ovewrite make's CC variable (defaults to "cc", some upstream rewrites it); - the above plus replacing explicit "gcc" (or similar) calls with $(CC) so that the variable is actually respected; - tc-export CC in src_compile before eventual econf. For C++, you'd have to replace CC with CXX everywhere above, of course. If your package is a special case on this, please let me know. Thanks, Diego
Created attachment 225909 [details, diff] Untested patch to fix CC issue with sloccount-2.26-r1.ebuild The upstream makefile sets "CC=gcc -Wall". The Gentoo ebuild already patched that directive to include user $CFLAGS, but left the use of an unqualified gcc. This patch changes the sed expression to rewrite the entire line, using the result of $(tc-getCC) to look up the relevant compiler. Due to a limitation in the upstream Makefile, the CFLAGS must be appended to CC, since the upstream rules do not use CFLAGS directly.
Fixed in -r2. Oh sorry, Kevin, didn't see your patch there.