mirror/nasm
2
0
Fork 0
mirror of https://github.com/netwide-assembler/nasm.git synced 2024-11-27 08:10:07 +08:00
Code Issues Packages Projects Releases Wiki Activity
456b1c46f8
nasm/aclocal.m4

40 lines
1.3 KiB
Plaintext
Raw Normal View History

Cleaner way to add gcc options We can actually test for the options being accepted, rather than try to test for gcc; this handles differences between gcc versions as well as compilers with a similar command line set.
2007-04-16 06:45:25 +08:00
dnl --------------------------------------------------------------------------
dnl PA_ADD_CFLAGS()
dnl
dnl Attempt to add the given option to CFLAGS, if it doesn't break compilation
dnl --------------------------------------------------------------------------
AC_DEFUN(PA_ADD_CFLAGS,
[AC_MSG_CHECKING([if $CC accepts $1])
pa_add_cflags__old_cflags="$CFLAGS"
CFLAGS="$CFLAGS $1"
AC_TRY_LINK([#include <stdio.h>],
[printf("Hello, World!\n");],
configure: enable additional code cleanliness warnings We are supposed to handle compiling on a "C90 plus long long" compiler, so make gcc (our most common development platform compiler) complain when we don't. However, suppress the complaints about the Microsoft definitions of the <inttypes.h> strings. From master branch checkin 25da6eaf434705a6ad01f252132dc7f109493c67, except that -Wwrite-strings is omitted; making the code base -Wwrite-strings clean is going to take additional work. Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2016-03-02 14:20:10 +08:00
AC_MSG_RESULT([yes])
CFLAGS="$pa_add_cflags__old_cflags ifelse([$2],[],[$1],[$2])",
Cleaner way to add gcc options We can actually test for the options being accepted, rather than try to test for gcc; this handles differences between gcc versions as well as compilers with a similar command line set.
2007-04-16 06:45:25 +08:00
AC_MSG_RESULT([no])
CFLAGS="$pa_add_cflags__old_cflags")])
autoconf: detect the broken bool in OpenWatcom 1.8 OpenWatcom 1.8 has a C99 mode, which implements _Bool and <stdbool.h>. Unfortunately the implementation is broken, and doesn't let _Bool be implicitly converted to integer (as required by the C99 spec). Detect this case in autoconf.
2009-03-02 05:57:40 +08:00
dnl --------------------------------------------------------------------------
dnl PA_WORKING_STDBOOL
dnl
dnl See if we have a working <stdbool.h> and bool support; in particular,
dnl OpenWatcom 1.8 has a broken _Bool type that we don't want to use.
dnl --------------------------------------------------------------------------
AC_DEFUN(PA_WORKING_BOOL,
[AC_MSG_CHECKING([if $CC has a working bool type])
Fix autoconf 2.68 warning. The first argument of AC_COMPILE_IFELSE needs to be wrapped with AC_LANG_SOURCE.
2010-11-08 00:31:27 +08:00
AC_COMPILE_IFELSE([AC_LANG_SOURCE([
autoconf: detect the broken bool in OpenWatcom 1.8 OpenWatcom 1.8 has a C99 mode, which implements _Bool and <stdbool.h>. Unfortunately the implementation is broken, and doesn't let _Bool be implicitly converted to integer (as required by the C99 spec). Detect this case in autoconf.
2009-03-02 05:57:40 +08:00
#ifndef __cplusplus
#include <stdbool.h>
#endif
int foo(bool x, int y)
{
return x+y;
}
Fix autoconf 2.68 warning. The first argument of AC_COMPILE_IFELSE needs to be wrapped with AC_LANG_SOURCE.
2010-11-08 00:31:27 +08:00
])],
autoconf: detect the broken bool in OpenWatcom 1.8 OpenWatcom 1.8 has a C99 mode, which implements _Bool and <stdbool.h>. Unfortunately the implementation is broken, and doesn't let _Bool be implicitly converted to integer (as required by the C99 spec). Detect this case in autoconf.
2009-03-02 05:57:40 +08:00
[AC_MSG_RESULT([yes])
AC_DEFINE(HAVE_WORKING_BOOL, 1,
[Define to 1 if your compiler has a correct implementation of bool])],
[AC_MSG_RESULT([no])])
])
Reference in New Issue Copy Permalink