[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Warnings for excessive macro arguments
From: |
Yavor Doganov |
Subject: |
Warnings for excessive macro arguments |
Date: |
Mon, 23 Aug 2010 20:02:05 +0300 |
User-agent: |
Wanderlust/2.15.5 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (Gojō) APEL/10.7 Emacs/23.2 (i486-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) |
I was wondering if it is possible (and whether it is a good idea in
general) autoconf to print warnings for extra macro arguments instead
of silently ignoring them.
Minimalistic example (from
https://savannah.gnu.org/bugs/index.php?30766):
AC_INIT
AC_CHECK_HEADERS(pthread.h,, [AC_MSG_ERROR([Unable to find pthread.h.])])
AC_CHECK_ALIGNOF(pthread_mutex_t,,[AC_INCLUDES_DEFAULT
#include <pthread.h>])
AS_IF([test -z $ac_cv_alignof_pthread_mutex_t],
[AC_MSG_ERROR([Unable to determine alignment of pthread_mutex_t.])])
AC_OUTPUT
The generated configure script fails on OpenBSD and Woe32, because
<pthread.h> is not #include'd in the test program.
It took me some time to spot where the problem is :-)
- Warnings for excessive macro arguments,
Yavor Doganov <=
- Re: Warnings for excessive macro arguments, Eric Blake, 2010/08/23
- Re: Warnings for excessive macro arguments, Yavor Doganov, 2010/08/23
- Re: Warnings for excessive macro arguments, Ralf Wildenhues, 2010/08/23
- Re: Warnings for excessive macro arguments, Eric Blake, 2010/08/23
- Re: Warnings for excessive macro arguments, Ralf Wildenhues, 2010/08/24
- Re: Warnings for excessive macro arguments, Yavor Doganov, 2010/08/24
- Re: Warnings for excessive macro arguments, Ralf Wildenhues, 2010/08/24
- Re: Warnings for excessive macro arguments, Yavor Doganov, 2010/08/24