From 49263be47aaa2358a0fb12ee90220137ca260b92 Mon Sep 17 00:00:00 2001
From: "Richard W.M. Jones" <rjones@redhat.com>
Date: Sun, 10 Dec 2017 21:12:01 +0000
Subject: [PATCH] configure: Don't define _FORTIFY_SOURCE.

We routinely test the upstream code by running everything under
valgrind, and in any case _FORTIFY_SOURCE is usually defined by
downstream Linux distros and we can leave the optimization vs safety
decision to them.

See this bug: https://bugs.gentoo.org/640494
---
 m4/guestfs-c.m4 | 6 ------
 1 file changed, 6 deletions(-)

diff --git a/m4/guestfs-c.m4 b/m4/guestfs-c.m4
index ef9f44f3f..416cbfb1a 100644
--- a/m4/guestfs-c.m4
+++ b/m4/guestfs-c.m4
@@ -119,12 +119,6 @@ AC_SUBST([NO_UM_CFLAGS])
 
 AC_DEFINE([lint], [1], [Define to 1 if the compiler is checking for lint.])
 AC_DEFINE([GNULIB_PORTCHECK], [1], [Enable some gnulib portability checks.])
-AH_VERBATIM([FORTIFY_SOURCE],[
-/* Enable compile-time and run-time bounds-checking, and some warnings. */
-#if __OPTIMIZE__ && (! defined (_FORTIFY_SOURCE) || _FORTIFY_SOURCE < 2)
-# undef _FORTIFY_SOURCE
-# define _FORTIFY_SOURCE 2
-#endif])
 
 AC_C_PROTOTYPES
 test "x$U" != "x" && AC_MSG_ERROR([Compiler not ANSI compliant])