From c5b551b25a1d89a3f20599adeec6c6c6a31946e5 Mon Sep 17 00:00:00 2001 From: Dana Jansens Date: Sat, 3 Mar 2007 00:58:37 +0000 Subject: [PATCH] add -fno-strict-aliasing to the gcc compiler flags. this is needed, see: http://www.exim.org/mail-archives/exim-users/Week-of-Mon-20030721/msg00141.html | It's not a compiler bug. It is a C99 bug, or more exactly, a | feature. C99 changed the semantic of the C language with respect to | aliasing questions. Now, the compiler can assume that pointer to | different types points to different memory location. This breaks all | the OO code written in C. | | This is a very good idea that the compiler issues a warning message | because the semantic of language really changed and you want to revert | to the old semantic. | | The make package MUST add -fno-strict-aliasing. It is not a | convenience to get rid off warnings. --- m4/openbox.m4 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/m4/openbox.m4 b/m4/openbox.m4 index a69a093d..32162353 100644 --- a/m4/openbox.m4 +++ b/m4/openbox.m4 @@ -64,7 +64,7 @@ AC_DEFUN([OB_COMPILER_FLAGS], if test "$GCC" = "yes"; then AC_MSG_RESULT([yes]) if test "$DEBUG" = "yes"; then - FLAGS="$FLAGS -g -fno-inline" + FLAGS="$FLAGS -g -fno-inline -fno-strict-aliasing" FLAGS="$FLAGS -Wall -Wsign-compare -Waggregate-return" FLAGS="$FLAGS -Wcast-qual -Wbad-function-cast -Wpointer-arith" # for Python.h -- 2.39.2