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 181951 [details, diff] Patch to nbsmtp-1.00-r3.ebuild to fix use of unqualified cc and to respect user LDFLAGS The upstream Makefile.in uses an explicit linking rule that ignores user LDFLAGS. This patch adds the suggested "tc-export CC" in src_compile and uses a sed expression to delete the explicit rule, so that GNU make's implicit linking rule, which respects user LDFLAGS, is used.
Fixed Thanks Kevin
