https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: app-crypt/libscrypt-1.22 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 849698 [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=5b0f61ca5820d9fad9344c6681a79095d2ffa9cf commit 5b0f61ca5820d9fad9344c6681a79095d2ffa9cf Author: Sam James <sam@gentoo.org> AuthorDate: 2023-10-04 16:37:30 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2023-10-04 16:47:17 +0000 app-crypt/libscrypt: don't redefine _FORTIFY_SOURCE Closes: https://bugs.gentoo.org/892928 Signed-off-by: Sam James <sam@gentoo.org> .../libscrypt-1.22-no-clobber-fortify-source.patch | 14 ++++++++++ app-crypt/libscrypt/libscrypt-1.22-r1.ebuild | 31 ++++++++++++++++++++++ 2 files changed, 45 insertions(+)