]> Dogcows Code - chaz/openbox/commit
add -fno-strict-aliasing to the gcc compiler flags. this is needed, see:
authorDana Jansens <danakj@orodu.net>
Sat, 3 Mar 2007 00:58:37 +0000 (00:58 +0000)
committerDana Jansens <danakj@orodu.net>
Sat, 3 Mar 2007 00:58:37 +0000 (00:58 +0000)
commitc5b551b25a1d89a3f20599adeec6c6c6a31946e5
tree421b127d31c5cee16818ec9e68908efbc4f2fd9e
parent4084f5d82dab7224785a1cc3ac8b00361e2fad57
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
This page took 0.025508 seconds and 4 git commands to generate.