aboutsummaryrefslogtreecommitdiffstats
path: root/community/openvas-libraries/000-fortify-source.patch
diff options
context:
space:
mode:
authorFrancesco Colista <fcolista@alpinelinux.org>2019-02-19 10:24:50 +0000
committerFrancesco Colista <fcolista@alpinelinux.org>2019-02-19 10:24:50 +0000
commit65c9d893ce9e9832f94cf7c754001075c09e2202 (patch)
treecd64f53b86a7046074d39468b037457cc5683d96 /community/openvas-libraries/000-fortify-source.patch
parent4787e5a94c50ec4d137750a129ed7939ec0d3f04 (diff)
downloadaports-65c9d893ce9e9832f94cf7c754001075c09e2202.tar.bz2
aports-65c9d893ce9e9832f94cf7c754001075c09e2202.tar.xz
community/openvas-libraries: renamed back from gvm-libs
Openvas are going to release gvm-libs with 1.0.0 rather than 10.0.0. This will break upgrades. See: https://github.com/greenbone/gvm-libs/issues/189 for an issue opened at this regard. In order to prepare openvas to next version, is better to rename it back to openvas-libraries.
Diffstat (limited to 'community/openvas-libraries/000-fortify-source.patch')
-rw-r--r--community/openvas-libraries/000-fortify-source.patch13
1 files changed, 13 insertions, 0 deletions
diff --git a/community/openvas-libraries/000-fortify-source.patch b/community/openvas-libraries/000-fortify-source.patch
new file mode 100644
index 0000000000..26ceb25ca9
--- /dev/null
+++ b/community/openvas-libraries/000-fortify-source.patch
@@ -0,0 +1,13 @@
+diff --git a/CMakeLists.txt b/CMakeLists.txt
+index a85088f..9d47f3a 100644
+--- a/CMakeLists.txt
++++ b/CMakeLists.txt
+@@ -302,7 +302,7 @@ if (NOT MINGW)
+
+ endif (NOT MINGW)
+
+-set (HARDENING_FLAGS "-Wformat -Wformat-security -O2 -D_FORTIFY_SOURCE=2 -fstack-protector -Wl,-z,relro -Wl,-z,now")
++set (HARDENING_FLAGS "-Wformat -Wformat-security -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fstack-protector -Wl,-z,relro -Wl,-z,now")
+ set (CMAKE_C_FLAGS_DEBUG "${CMAKE_C_FLAGS_DEBUG} -Werror")
+
+