https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: net-proxy/torsocks-2.4.0-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 853892 [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=9ff2562afb78630fdc3b6e9b9853a26a8181e637 commit 9ff2562afb78630fdc3b6e9b9853a26a8181e637 Author: Sam James <sam@gentoo.org> AuthorDate: 2024-03-24 07:12:48 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2024-03-24 07:32:54 +0000 net-proxy/torsocks: fix bashism in configure & don't clobber _F_S Closes: https://bugs.gentoo.org/895874 Signed-off-by: Sam James <sam@gentoo.org> net-proxy/torsocks/Manifest | 2 +- .../torsocks/files/torsocks-2.4.0-configure.patch | 23 ++++++++++++++++++++++ ...ks-2.4.0-r1.ebuild => torsocks-2.4.0-r2.ebuild} | 12 +++++------ 3 files changed, 30 insertions(+), 7 deletions(-)