| Summary: | dev-util/cargo-ebuild does not respect CFLAGS/LDFLAGS | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Agostino Sarubbo <ago> |
| Component: | Current packages | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | esigra, sam |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 59506, 331933 | ||
| Attachments: | build.log | ||
Created attachment 640434 [details]
build.log
build log and emerge --info
it's rust ebuild and can't realistically support CFLAGS. maybe cargo.eclass could omit that check for those packages, or check can be improved. |
This is an auto-filed bug because dev-util/cargo-ebuild does not respect CFLAGS/LDFLAGS. The issue was originally discovered on amd64, but it may be reproducible on other arches as well. If you think that a different summary clarifies the issue better, feel free to change it. Attached build log and emerge --info. NOTE: To reproduce this issue you may want to set CFLAGS="${CFLAGS} -frecord-gcc-switches" and LDFLAGS="${LDFLAGS} -Wl,--defsym=__gentoo_check_ldflags__=0". If this is not something about c/c++ context you may want to set also FFLAGS and FCFLAGS or just see this bug as an hint to hide the QA warning where is not possible to respect CFLAGS/LDFLAGS.