Re: re autoconf

[Paul Eggert]

twlevo <address@hidden> writes:

> If one of tests in GNU Bison testsuite fails the logfile has for example:
> 82. calc.at:567: testing ...
> ./calc.at:567: bison -o calc.c calc.y
> ./calc.at:567: $CC $CFLAGS $CPPFLAGS $LDFLAGS -o calc calc.c $LIBS
>
> and the generated data/testsuite file in GNU Bison has a line:
>
> echo "$at_srcdir/calc.at:556: \$CC \$CFLAGS \$CPPFLAGS \$LDFLAGS -o calc 
> calc.c \$LIBS"
> echo calc.at:556 >"$at_check_line_file"
>
> If in autoconf cvs the file lib/autotest/general.m4 is changed:
>
> m4_define([_AT_CHECK],
> [$at_traceoff
> echo "$at_srcdir/AT_LINE: $1"
> echo AT_LINE >"$at_check_line_file"
>
> Then the logfile in testsuite has:
> 82. calc.at:567: testing ...
> ./calc.at:567: bison -o calc.c calc.y
> ./calc.at:567: gcc -g    -DHAVE_CONFIG_H=1 -I/home/bison/current-bison/bison  
>  -o calc calc.c  


Alas, that won't work, as AT_CHECK is supposed to generate a test case
that handles any string that you give it.  For example, if $1 is:

echo '${=invalid}'

AT_CHECK is supposed to generate a test that fails.  With the proposed
change, the failure will cause the entire test harness to exit, which
is too much.

Also, the string might contain $(CMD), and we don't want to execute
CMD more than once.

You are indeed pointing out a problem, but the solution is not so
easy.