[Top][All Lists]

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

Re: AC_CHECK_PROG documentation

From: Stepan Kasal
Subject: Re: AC_CHECK_PROG documentation
Date: Fri, 5 Nov 2004 09:42:34 +0100
User-agent: Mutt/1.4.1i


On Thu, Nov 04, 2004 at 01:30:02PM -0800, Paul Eggert wrote:
> Stepan Kasal <address@hidden> writes:
> > "if the variable is already set (and non-null), the macro does nothing"
> The other option would be to change the code to match the documentation.
> Which makes more sense?

I considered both possibilities and I beleive that the code is right and
the docs should be fixed.

What made me to investigate the issue was that I happened to write VAR=""
instead of ``unset VAR''.

One can also use:

        ./configure VAR="" ...
        VAR="" ./configure ...

which has no easy ``unset'' equivalent.

> <http://lists.gnu.org/archive/html/autoconf-patches/2004-10/msg00019.html>?
> It's still in my inbox, unfortunately.

I understand perfectly, sorry for bothering you.

But I'd like to ask you one question (the answer will help me in a discussion
on bug-automake):

Is it intentional that AC_CHECK_PROGS does nothing if the variable is already
set (well, set and non-null)?

(We all know that AC_CHECK_PROG does nothing if the var is set, but is it OK


reply via email to

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