This is an auto-filled bug because sys-cluster/sanlock does not respect LDFLAGS. The issue was originally discovered on arm64, 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 636800 [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=05b4374649b60e5aed18180481f35c7b2095aeca commit 05b4374649b60e5aed18180481f35c7b2095aeca Author: Marc Schiffbauer <mschiff@gentoo.org> AuthorDate: 2020-08-21 17:57:36 +0000 Commit: Marc Schiffbauer <mschiff@gentoo.org> CommitDate: 2020-08-21 18:05:51 +0000 sys-cluster/sanlock: add new version Bug: https://bugs.gentoo.org/718532 Closes: https://bugs.gentoo.org/721594 Package-Manager: Portage-2.3.103, Repoman-2.3.23 Signed-off-by: Marc Schiffbauer <mschiff@gentoo.org> sys-cluster/sanlock/Manifest | 1 + .../files/sanlock-fence_sanlock-LDFLAGS.patch | 12 +++ sys-cluster/sanlock/sanlock-3.8.2.ebuild | 85 ++++++++++++++++++++++ 3 files changed, 98 insertions(+)
