[Top][All Lists]

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

misleading output from AC_PROG_AWK

From: Ben Pfaff
Subject: misleading output from AC_PROG_AWK
Date: Sat, 26 Apr 2008 13:13:58 -0700
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux)

I'm passing along the following bug report that was reported
against the Debian package for Autoconf 2.61.  I've looked over
the Autoconf git repository and I don't see any changes in this
area since 2.61.

This really is a generic cosmetic issue with AC_CHECK_PROGS: if
the first binary tested for is not the most generic name for the
program, then assigning to the overriding variable will seem to
find that first binary instead of the generic program.

Clint Adams <address@hidden> writes:
> I want @AWK@ to be equal to 'awk' so it will not introduce an
> unnecessary dependency on whichever of gawk, mawk, or nawk it
> finds first in the buildd chroot.  Therefore I am forced to
> pass AWK=awk to configure, which then provides the following
> output.
> checking for gawk... awk
> checking whether make sets $(MAKE)... yes
> checking for gawk... (cached) awk
> In this case, awk is not gawk, and configure is not actually
> searching for gawk, so this AC_PROG_AWK output is misleading.

Ben Pfaff 

reply via email to

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