Bug#478065: misleading output from AC_PROG_AWK

2008-06-20 Thread Ralf Wildenhues
Hi Eric, * Eric Blake wrote on Fri, Jun 20, 2008 at 02:08:46PM CEST: > According to Ralf Wildenhues on 6/19/2008 11:42 AM: >> | checking for gawk... (user-provided) awk >> >> One drawback is that this may be wrong, too, for example when AWK >> is passed from one configure script to the next (maybe

Bug#478065: misleading output from AC_PROG_AWK

2008-06-20 Thread Eric Blake
According to Ralf Wildenhues on 6/19/2008 11:42 AM: 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. What are the alternatives? - output a line for each name we check, or even each dire

Bug#478065: misleading output from AC_PROG_AWK

2008-06-19 Thread Ralf Wildenhues
Hello Clint, Ben, apologies for the long delay. * Ben Pfaff wrote on Sat, Apr 26, 2008 at 10:13:58PM CEST: > 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

Bug#478065: misleading output from AC_PROG_AWK

2008-04-26 Thread Ben Pfaff
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