autoconf
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AC_TRY_COMPILE() annoyances with 2.63b


From: Mike Frysinger
Subject: Re: AC_TRY_COMPILE() annoyances with 2.63b
Date: Sun, 18 Oct 2009 02:15:33 -0400
User-agent: KMail/1.12.1 (Linux/2.6.31; KDE/4.3.1; x86_64; ; )

On Sunday 05 April 2009 20:46:03 Eric Blake wrote:
> According to Mike Frysinger on 4/5/2009 4:10 PM:
> > AC_TRY_COMPILE() is invoked with an empty 4th argument: [].  i think
> >
> >     [ sp_expire_available=yes ], []
> >     )
> 
> That's not an empty fourth argument.  Remember, trailing space IS
> significant, and only leading space is stripped.  The bug is in your
> configure.ac.
> 
> That said, autoconf could probably be taught that, for some macros, an
> argument of all whitespace is morally equivalent to an empty argument.

seems the issue is worse than people being pedantic with [].  for example, if 
a macro is expanded implicitly, then a user explicit call to that macro gets 
nooped and we're back where we started -- syntax error

simple example:
$ cat configure.ac
AC_INIT
AS_IF([:], [
        : some random user stuff
],[
        AC_PROG_LEX
        AC_DECL_YYTEXT
])
AC_OUTPUT
$ autoconf --version
autoconf (GNU Autoconf) 2.64
$ autoconf && ./configure -q
./configure: line 2676: syntax error near unexpected token `fi'
./configure: line 2676: `fi'
-mike




reply via email to

[Prev in Thread] Current Thread [Next in Thread]