Re: Log from LFS Development build autoconf-2.67 on Compaq Evo N600c

[Ralf Wildenhues]

Hello Eric, Clark,

* Eric Blake wrote on Mon, Oct 25, 2010 at 07:40:56PM CEST:
> On 10/19/2010 06:16 PM, Clark Fredenburg wrote:
> >I was doing a development build of LFS and the output from this step
> >told me to send you this testlog.
> >
> >I did see the following error in the output displayed in red:
> >197: parallel syntax error           FAILED (autotest.at:1356)
> 
> Thanks for the report.  There is a known bug in the testsuite (the
> test assumes that it is forcing SIGPIPE, but in reality is
> triggering non-portable behavior), which I hope to at least comment
> out before releasing 2.68.1 in the near future.  Help in making the
> test more robust would also be appreciated.  At any rate, it is safe
> to use the just-built autoconf in spite of this test failure.

While it may be safe to use this Autoconf, the reported failure is not
the SIGPIPE one:

> > ./autotest.at:1356: ${CONFIG_SHELL-$SHELL} -c 'case `. ./syntax; echo $?` in
> >                   0|"") exit 77;;
> >                 esac'
> > stderr:
> > ./syntax: line 2: syntax error: unexpected end of file
> > ./syntax: line 2: warning: syntax errors in . or eval will cause future 
> > versions
> > +of the shell to abort as Posix requires
> > stdout:
> > ./autotest.at:1356: $CONFIG_SHELL ./micro-suite -j
> > stderr:
> > ./micro-suite: line 1742:
> > +/sources/autoconf-2.67/tests/testsuite.dir/197/micro-suite.dir/at-job-fifo:
> > +Interrupted system call
> > stdout:
> > ## --------------------------------------------------- ##
> > ## GNU Nonsense 1.0 test suite: artificial test suite. ##
> > ## --------------------------------------------------- ##
> > 
> >   1: my only test                                    ok
> > ./autotest.at:1356: grep "unable to parse test group: 2" stderr
> > stdout:
> > ./autotest.at:1356: exit code was 1, expected 0
> > ./micro-suite.log:

Clark, which shell and which exact version is /bin/sh on your system,
which distro are you on?  How often is this issue reproducible; try
e.g.,
  cd tests
  for try in `seq 20`; do
    ./testsuite -x 197
  done

Thanks,
Ralf