Summary: | No more qa notice for LDFLAGS | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Agostino Sarubbo <ago> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Agostino Sarubbo
![]() Detection works for me: * QA Notice: Files built without respecting LDFLAGS have been detected * Please include the following list of files in your report: * /usr/bin/ansifilter You most likely forgot to add -Wl,--defsym=__gentoo_check_ldflags__=0 to LDFLAGS. You are right...however I remember that the behavior in the past was different. The main issue here, I guess, is that nobody communicate to do this change to the arch teams, or at least I missed that. (In reply to Agostino Sarubbo from comment #2) It was documented as a bug fix in the release notes for portage-2.3.12. I highly recommend reading the release notes periodically. (In reply to Agostino Sarubbo from comment #2) > The main issue here, I guess, is that nobody communicate to do this change > to the arch teams, or at least I missed that. Although not all architectures, but AMD64 and X86 teams were notified in bug #680828... |