| Summary: | app-editors/qemacs: CC variable not respected | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
| Component: | New packages | Assignee: | Emacs project <emacs> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 243502 | ||
| Attachments: | Build log | ||
I'm not sure what is going on here, since the package uses econf and emake in the standard way. Could you please attach the build.log, so that we see where it fails. Created attachment 169662 [details]
Build log
autoconf 2.1 does not detect our compiler properly, you need a tc-export CC before calling it (toolchain-funcs eclass)
(In reply to comment #2) > autoconf 2.1 does not detect our compiler properly, you need a tc-export CC > before calling it (toolchain-funcs eclass) Nope, that doesn't work for this package. The following does: econf --cc="$(tc-getCC)" |
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