This is an auto-filled bug because app-misc/ltunify 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".
Created attachment 638048 [details] build.log build log and emerge --info
tinderbox has reproduced this issue with version 0.2-r2 - Updating summary.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3f7b4b2fba5aa60adcd170aae8e4f46eb382137d commit 3f7b4b2fba5aa60adcd170aae8e4f46eb382137d Author: Patrick McLean <chutzpah@gentoo.org> AuthorDate: 2023-12-08 19:35:41 +0000 Commit: Patrick McLean <chutzpah@gentoo.org> CommitDate: 2023-12-08 19:35:51 +0000 app-misc/ltunify: add 0.3, drop 0.2-r2 Closes: https://bugs.gentoo.org/722406 Signed-off-by: Patrick McLean <chutzpah@gentoo.org> app-misc/ltunify/Manifest | 2 +- .../files/ltunify-0.3-compiler-warning.patch | 26 ++++++++++++++++ app-misc/ltunify/files/ltunify-0.3-ldflags.patch | 19 ++++++++++++ .../{ltunify-0.2-r2.ebuild => ltunify-0.3.ebuild} | 35 +++++++++++++++++----- 4 files changed, 73 insertions(+), 9 deletions(-)
