bug-autoconf
[Top][All Lists]
Advanced

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

Re: Documentation and AC_DEFINE/AC_DEFINE_UNQUOTED


From: Eric Blake
Subject: Re: Documentation and AC_DEFINE/AC_DEFINE_UNQUOTED
Date: Mon, 24 Sep 2012 08:00:42 -0600
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120911 Thunderbird/15.0.1

On 09/22/2012 05:38 AM, Brad Smith wrote:
> Hi,
> 
> Looking at the autoconf documentation it shows AC_DEFINE / AC_DEFINE_UNQUOTED
> as being able to be used without specifying a value or description, .e.g.
> 
> AC_DEFINE([FOO])
> 
> and yet autoconf pukes on this. If I add an empty value field with [] and
> a description then autoconf no longer rejects this. Is this expected?

From the autoconf manual for AC_DEFINE:

If neither @var{value} nor @var{description} are given, then
@var{value} defaults to 1 instead of to the empty string.  This is for
backwards compatibility with older versions of Autoconf, but this usage
is obsolescent and may be withdrawn in future versions of Autoconf.

So if you are asking autoconf to warn about obsolete usage, this might
explain why you are running into issues.


-- 
Eric Blake   address@hidden    +1-919-301-3266
Libvirt virtualization library http://libvirt.org

Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

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