Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 243886

Summary: dev-lang/smlnj: CC variable not respected
Product: Gentoo Linux Reporter: Diego Elio Pettenò (RETIRED) <flameeyes>
Component: New packagesAssignee: No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed>
Status: IN_PROGRESS ---    
Severity: normal CC: ssuominen
Priority: High    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Bug Depends on:    
Bug Blocks: 243502    

Description Diego Elio Pettenò (RETIRED) gentoo-dev 2008-10-24 17:33:07 UTC
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
Comment 1 Samuli Suominen gentoo-dev 2010-06-29 12:13:21 UTC
Fix from bug 304625, Comment #5:

+  29 Jun 2010; Samuli Suominen <ssuominen@gentoo.org> smlnj-110.71.ebuild:
+  Respect environment flags and targets wrt #243886 by Michael Weber.
+
Comment 2 Marijn Schouten (RETIRED) gentoo-dev 2011-10-19 14:11:42 UTC
Still needs to go upstream
Comment 3 Marijn Schouten (RETIRED) gentoo-dev 2012-10-19 11:04:09 UTC
I've now fixed this issue with a slight variation of Michael Weber's patch (see bug 304625, thanks xmw!), but I'm leaving this bug open until an upstream solution is available.