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
It seems to work fine for me. If I remove all the gcc's in my path (/usr/bin/gcc and /usr/i686-pc-linux-gnu/gcc-bin/4.3.3/gcc ) and then set CC="/usr/bin/i686-pc-linux-gnu-gcc-4.1.2" then it builds fine, and uses that compiler.
(In reply to comment #1) > It seems to work fine for me. > > If I remove all the gcc's in my path (/usr/bin/gcc and > /usr/i686-pc-linux-gnu/gcc-bin/4.3.3/gcc ) and then set > CC="/usr/bin/i686-pc-linux-gnu-gcc-4.1.2" then it builds fine, and uses that > compiler. > Thanks. I also want to note that before configure: %% grep CC Makefile.in CC=@CC@ after configure: %% grep CC Makefile CC=gcc So, I think this bug is an error too.
Please don't close the bugs without verify it!
Created attachment 187541 [details, diff] cw-1.0.15.ebuild patch
(In reply to comment #3) > Please don't close the bugs without verify it! > sry, didn't understand it. thx for the patch. fixed...no bump
