| Summary: | dev-python/shm: CC variable not respected | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
| Component: | New packages | Assignee: | Sebastian Pipping <sping> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | python |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 243502 | ||
Good catch, indeed CC is not respected.
For testing I removed /usr/bin/{gcc,cc,c++,c99} locally.
While trying to make shm compile with Intel CC I found that "cc" is called directly from setup.py. I made a patch for it which made it compile with ICC, reading CC properly. As upstream states "This module isn't being developed anymore" I did not take the patch online.
+ 26 Jun 2010; Sebastian Pipping <sping@gentoo.org> shm-1.2.2.ebuild,
+ +files/shm-1.2.2-compiler.patch:
+ Fix setup.py to respect CC variable (bug #243966)
+
Closing. Thanks Diego.
|
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 P.S.: this happens during check, not build.