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
If CC is set, CC will be used. You didn't set CC to a functional compiler, so this bug isn't about CC not being respected, it's about CC not being given a default value, and your arguments don't apply to that at all. Would you like to explain why this would be a good idea?
(In reply to comment #1) > If CC is set, CC will be used. You didn't set CC to a functional compiler, so > this bug isn't about CC not being respected, it's about CC not being given a > default value, and your arguments don't apply to that at all. Would you like to > explain why this would be a good idea? This comment also applies to several other bugs you've reported, at least those for dev-lang/icon and dev-libs/tvision.
No reply, so closing.
