Dana Jansens c5b551b25a 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.		2007-03-03 00:58:37 +00:00
..
Makefile.am	add the new m4s	2003-07-23 04:15:00 +00:00
openbox.m4	add -fno-strict-aliasing to the gcc compiler flags. this is needed, see:	2007-03-03 00:58:37 +00:00
x11.m4	just make configure --help output slightly less confusing, no functional change	2006-08-22 16:17:50 +00:00