sys-cluster/kronosnet: don't set FORTIFY_SOURCE=2 twice; forward Werror patch

Closes: https://bugs.gentoo.org/847790
Bug: https://bugs.gentoo.org/750548
Signed-off-by: Sam James <sam@gentoo.org>
This commit is contained in:
Sam James
2022-06-01 01:30:40 +01:00
parent b4ec8c54b1
commit f017304f5a
2 changed files with 23 additions and 0 deletions

View File

@@ -0,0 +1,18 @@
We already set this via GCC (patched in) and setting it individually per-package
like this causes redefinition errors if folks try to use the new =3 level.
So, protection is the same without this, and this patch removes
the trouble of upgrading to =3 which we're working on.
https://bugs.gentoo.org/847790
--- a/configure.ac
+++ b/configure.ac
@@ -324,7 +324,7 @@ if test "x${enable_debug}" = xyes; then
FORTIFY_CFLAGS=""
else
OPT_CFLAGS="-O3"
- FORTIFY_CFLAGS="-D_FORTIFY_SOURCE=2"
+ FORTIFY_CFLAGS=""
fi
# Check for availablility of hardening options

View File

@@ -30,6 +30,11 @@ BDEPEND="
app-doc/doxygen[dot]
)"
PATCHES=(
"${FILESDIR}"/${PN}-1.19-no-Werror.patch
"${FILESDIR}"/${PN}-1.23-no-extra-fortify-source.patch
)
src_configure() {
local myeconfargs=(
$(use_enable doc man)