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>
This commit is contained in:
parent
f640b61d55
commit
2fc232bd23
1 changed files with 5 additions and 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
|
||||
|
||||
|
|
Loading…
Reference in a new issue