Re: fix AC_C_CONST to work with CFLAGS -O2 -Wall -Werror

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Didier Barvaux on 5/10/2008 9:37 AM: | Hi all, | | I seems that GCC fails to compile the code generated by the AC_C_CONST | macro if the -O2 -Wall -Werror CFLAGS are specified. Thanks for the report. AC_C_CONST is obsolete - as of

fix AC_C_CONST to work with CFLAGS -O2 -Wall -Werror

Hi all, I seems that GCC fails to compile the code generated by the AC_C_CONST macro if the -O2 -Wall -Werror CFLAGS are specified. I tried with both autoconf 2.61 and 2.62.17-684d2-dirty (taken from git repo). GCC version is 4.1.2. Below is the part of the config.log file describing what

Extend AT_CHECK_MACRO to test macros with -O2 -Wall -Werror

Hi all, I encountered a problem with the AC_C_CONST macro when using -O2 -Wall -Werror as CFLAGS. The AC_C_CONST macro broke with similar CFLAGS some time ago [1]. Thus I created a patch that extends the AT_CHECK_MACRO macro used in the testsuite. [1]

Re: Extend AT_CHECK_MACRO to test macros with -O2 -Wall -Werror

Thanks for the patch. However, I don't want to apply it just yet. There is a bigger issue that several tests fail when running the autoconf testsuite under -Wall -Werror (I have tried this in the past); in particular, some warnings occur when testing for functions that might be implemented

Re: fix AC_C_CONST to work with CFLAGS -O2 -Wall -Werror

Thanks for the report. AC_C_CONST is obsolete - as of autoconf 2.60, there were no known compilers on typical porting platforms that lacked const support. The easier fix is just to delete that macro from gcc's configure.ac, and require C89 support from the system compiler. Don't known

Re: Extend AT_CHECK_MACRO to test macros with -O2 -Wall -Werror

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Didier Barvaux on 5/10/2008 12:39 PM: | | Look at the patch. Use -fno-builtin to silence the warning. gcc isn't the only compiler, but -fno-builtin is not universally available. Blindly setting CFLAGS to include options that are not

AC_OPENMP, default off

It seems that AC_OPENMP always defaults to enabled by default. This causes problems for packages that would prefer that this feature be disabled by default. OpenMP is pretty invasive since it adds additional library dependencies. Is there a way to use AC_OPENMP in a default disabled state

Site configuration files and configure defaults

Hello again, I have been reading the Autoconf documentation regarding site specific configuration files. I have been trying to find a way to change sysconfdir to just be ${sysconfdir}, not ${prefix}/${sysconfdir}. I'd like to set that as a configure default for my program. I see that this is

autoconf-2.62: `make check' falls foul of MSYS bug

Having successfully built autoconf-2.62 for use with MSYS, on MS-Windows, `make check' fails as follows:-- $ make check [...] /bin/sh ./testsuite rm: reading directory `tdir /': No such file or directory testsuite: error: invalid content: atlocal make[3]: *** [check-local] Error 1

Re: autoconf-2.62: `make check' falls foul of MSYS bug

On Saturday 10 May 2008 20:13, Eric Blake wrote: According to Keith Marshall on 5/9/2008 2:18 PM: | Having successfully built autoconf-2.62 for use with MSYS, on | MS-Windows, `make check' fails as follows:-- | | $ make check | [...] | /bin/sh ./testsuite | rm: reading directory