https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: app-arch/unalz-0.65 does not respect LDFLAGS. Discovered on: amd64 (internal ref: guru_tinderbox) 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 (with QA_FLAGS_IGNORED) where is not possible to respect LDFLAGS.
Created attachment 697965 [details] build.log build log and emerge --info
It sounds like it's a makefile issue, if I understand correctly? Like, the bot set some LDFLAGS and the ebuild accepted them, but the build process itself discarded them, is that correct?
Exactly. :) I took the liberty and pushed https://sources.gentoo.org/repo/proj/guru.git/commit/?id=9b18dc3759829ce133604c7d097e750b37ce5720 to fix this.
Thanks for fixing it! I think I was completely mistaken as my first thought was: "oh crap, I'll have to fork and either fix that crazy makefile or port it to cmake". Glad it was less complicated than all that! :)
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=9b18dc3759829ce133604c7d097e750b37ce5720 commit 9b18dc3759829ce133604c7d097e750b37ce5720 Author: Florian Schmaus <flo@geekplace.eu> AuthorDate: 2021-04-07 11:38:10 +0000 Commit: Florian Schmaus <flo@geekplace.eu> CommitDate: 2021-04-07 11:39:41 +0000 app-arch/unalz: respect LDFLAGS Closes: https://bugs.gentoo.org/780600 Signed-off-by: Florian Schmaus <flo@geekplace.eu> app-arch/unalz/{unalz-0.65.ebuild => unalz-0.65-r1.ebuild} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
Changing TRACKER as requested by QA.