| commit | 2fc232bd235f969224e6238fb037720d6de8449e | |
| author | H. Peter Anvin <hpa@linux.intel.com> | |
| Thu, 14 Jul 2016 20:51:01 +0000 (14 13:51 -0700) | ||
| committer | H. Peter Anvin <hpa@linux.intel.com> | |
| Thu, 14 Jul 2016 20:51:01 +0000 (14 13:51 -0700) | ||
| tree | c219793314d78b460122a71065e484da15bb78ac | treesnapshot (tar.gz zip) |
| parent | f640b61d55e0c238883a2769540f7c7d946b5117 | commitdiff |
compiler.h: always undefine __STRICT_ANSI__ for gcc
It is not just DJGPP which has broken header files if __STRICT_ANSI__
is defined. Cygwin has also been confirmed to have problems. It
would be somewhat different if configure didn't still detect those
functions.
Undefine __STRICT_ANSI__ for all gcc platforms. If this breaks then,
well, we'll have to really narrow down the problems.
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
It is not just DJGPP which has broken header files if __STRICT_ANSI__
is defined. Cygwin has also been confirmed to have problems. It
would be somewhat different if configure didn't still detect those
functions.
Undefine __STRICT_ANSI__ for all gcc platforms. If this breaks then,
well, we'll have to really narrow down the problems.
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
| compiler.h | diffblobblamehistory |