This is an auto-filed bug because x11-misc/xlockmore does not respect 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 LDFLAGS="${LDFLAGS} -Wl,--defsym=__gentoo_check_ldflags__=0". If this is not something about c/c++ context you may want to see this bug as an hint to hide the QA warning where is not possible to respect LDFLAGS.
Created attachment 642748 [details] build.log build log and emerge --info
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=922539a7c779164aba0bc14f6ef7a1eff057def4 commit 922539a7c779164aba0bc14f6ef7a1eff057def4 Author: Jeroen Roovers <jer@gentoo.org> AuthorDate: 2020-05-30 14:49:13 +0000 Commit: Jeroen Roovers <jer@gentoo.org> CommitDate: 2020-05-30 14:49:33 +0000 x11-misc/xlockmore: Inject LDFLAGS Package-Manager: Portage-2.3.100, Repoman-2.3.22 Closes: https://bugs.gentoo.org/726280 Signed-off-by: Jeroen Roovers <jer@gentoo.org> .../files/xlockmore-5.64_alpha0-LDFLAGS.patch | 33 ++++++++++++++++++++++ x11-misc/xlockmore/xlockmore-5.64_alpha0.ebuild | 1 + 2 files changed, 34 insertions(+)
