diff options
| author | H. Peter Anvin <hpa@linux.intel.com> | 2016-07-14 13:51:01 -0700 |
|---|---|---|
| committer | H. Peter Anvin <hpa@linux.intel.com> | 2016-07-14 13:51:01 -0700 |
| commit | 2fc232bd235f969224e6238fb037720d6de8449e (patch) | |
| tree | c219793314d78b460122a71065e484da15bb78ac | |
| parent | f640b61d55e0c238883a2769540f7c7d946b5117 (diff) | |
| download | nasm-2fc232bd235f969224e6238fb037720d6de8449e.tar.gz | |
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>
| -rw-r--r-- | compiler.h | 7 |
1 files changed, 5 insertions, 2 deletions
@@ -43,8 +43,11 @@ #ifndef NASM_COMPILER_H #define NASM_COMPILER_H 1 -#ifdef __DJGPP__ -/* DJGPP has header file problems if __STRICT_ANSI__ is defined */ +/* + * At least DJGPP and Cygwin have broken header files if __STRICT_ANSI__ + * is defined. + */ +#ifdef __GNUC__ # undef __STRICT_ANSI__ #endif |