| Summary: | Repoman could print upstream.workaround if there is a reference to "no-as-needed" in a ebuild | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Samuli Suominen (RETIRED) <ssuominen> |
| Component: | Current packages | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | binki, qa |
| Priority: | High | Keywords: | InVCS |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 234710, 288499 | ||
| Attachments: | Patch to repoman | ||
Created attachment 213482 [details, diff]
Patch to repoman
Suggested patch to repoman
Thanks, this is in svn r15128. This is fixed in 2.1.7.16 and 2.2_rc61. |
The correct way to workaround -Wl,--as-needed failures is, inherit flag-o-matic [ .. ] append-ldflags $(no-as-needed) [ .. ] Using above doesn't mean you can close valid asneeded bugs as resolved, fixed, because, in principle, it's same as using "emake -j1" or MAKEOPTS="${MAKEOPTS} -j1" in a ebuild. So what I'm suggesting is a new repoman warning, like upstream.workaround if repoman sees the wording "no-as-needed" present in a ebuild, like it does for -j1 currently.