https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: net-libs/libotr-4.1.1-r1 redefines _FORTIFY_SOURCE (HARDENED-SYSTEM). Discovered on: amd64 (internal ref: hardened_tinderbox) NOTE: (HARDENED-SYSTEM) in the summary means that the bug was found on a machine that runs an hardened profile with -D_FORTIFY_SOURCE=3 and -D_GLIBCXX_ASSERTIONS (https://www.gentoo.org/support/news-items/2023-01-01-hardening-fortify-assertions.html) but this bug MAY or MAY NOT BE related to the changes related to hardened.
Created attachment 853450 [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=0bda0617c2f10663b24210f00dea77208f9f59a3 commit 0bda0617c2f10663b24210f00dea77208f9f59a3 Author: Sam James <sam@gentoo.org> AuthorDate: 2023-10-04 15:10:18 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2023-10-04 15:10:45 +0000 net-libs/libotr: don't redefine _FORTIFY_SOURCE Closes: https://bugs.gentoo.org/895680 Signed-off-by: Sam James <sam@gentoo.org> .../libotr-4.1.1-dont-clobber-fortify-source.patch | 23 +++++++++++++ net-libs/libotr/libotr-4.1.1-r2.ebuild | 40 ++++++++++++++++++++++ 2 files changed, 63 insertions(+)