Browse Source

document why we don't enable fortify without optimizations

Samuel Thibault 8 years ago
parent
commit
6b343fd01d
1 changed files with 3 additions and 0 deletions
  1. 3 0
      configure.ac

+ 3 - 0
configure.ac

@@ -1517,6 +1517,9 @@ AC_MSG_RESULT($enable_fast)
 if test x$enable_fast = xyes; then
 if test x$enable_fast = xyes; then
 	AC_DEFINE(STARPU_NO_ASSERT, [1], [disable assertions])
 	AC_DEFINE(STARPU_NO_ASSERT, [1], [disable assertions])
 else
 else
+        # fortify gets really enabled only with optimizations, avoid enabling it
+        # when they optimizations are not enabled, because with some glibc it
+        # spews a lot of warnings.
 	if test x$enable_debug != xyes; then
 	if test x$enable_debug != xyes; then
 		if test x$GCC = xyes; then
 		if test x$GCC = xyes; then
 			CPPFLAGS="$CPPFLAGS -D_FORTIFY_SOURCE=1"
 			CPPFLAGS="$CPPFLAGS -D_FORTIFY_SOURCE=1"