C99 support

2004-11-28 Thread Roger Leigh
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Are there any tests I can use to specify that I want a C99 compiler? AC_PROG_CC isn't sufficient. Would it be possible to introduce a macro to select the C standard required (K&R, C89, C99)? Ideally it could just detemine that gcc could accept the "-

Re: C99 support

2004-11-28 Thread Andreas Schwab
Roger Leigh <[EMAIL PROTECTED]> writes: > Are there any tests I can use to specify that I want a C99 compiler? > AC_PROG_CC isn't sufficient. IMHO the preferred way is to check for the specific features you need (eg. with AC_COMPILE_IFELSE) and abort when not provided (or maybe use workarounds in

Re: C99 support

2004-11-28 Thread Roger Leigh
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andreas Schwab <[EMAIL PROTECTED]> writes: > Roger Leigh <[EMAIL PROTECTED]> writes: > >> Are there any tests I can use to specify that I want a C99 compiler? >> AC_PROG_CC isn't sufficient. > > IMHO the preferred way is to check for the specific feat

Re: C99 support

2004-11-28 Thread Kevin P. Fleming
Roger Leigh wrote: and these work well. What it doesn't do is let me use features such as mixed declarations and code. These require you to use "gcc -std=c99" or "c99" or similar, and I can't enable this portably. If autoconf could find out how to put a given compiler into C99 mode, that would b

Re: C99 support

2004-11-28 Thread Gary V. Vaughan
Kevin P. Fleming wrote: Roger Leigh wrote: and these work well. What it doesn't do is let me use features such as mixed declarations and code. These require you to use "gcc -std=c99" or "c99" or similar, and I can't enable this portably. If autoconf could find out how to put a given compiler int