Re: v2.50 on cygwin fails tests 15 thru 21

[david]

Akim, 

I'll attempt to answer the questions you posed. Thanks for any help you can 
provide.

-David

On Tue, 22 May 2001, Akim Demaille wrote:

> This is very bizarre, these tests have nothing in common.  To me, it
> looks like something went wrong on your host, e.g., you were running
> the test suite twice concurrently.  Or maybe the first one leaves a
> mess, and it's only 21/22 which recovers?

No, I was not running two test suites at the same time. Also, this was the 
first time it had been run; no chance that previous runs had muddied the water. 
Here's what I did:
- gunzip *gz
- tar -xvf *tar
- cd autoconf-2.50
- ./configure
- make
- make check

> 
> | Skipped tests:
> |   37: compile.at:169  AC_PROG_CPP without warnings
> |   38: compile.at:206  AC_PROG_CPP via CC
> 
> Hm.  I'd like to know why the test suite decided to skip them.  Could
> you run
> 
> ./testsuite -v -x 37 38
> 
results:

address@hidden ~/autoconf-2.50/tests
$ ./testsuite -v -x 37 38
================================
Test suite for GNU Autoconf 2.50
================================
37. ./compile.at:169: testing AC_PROG_CPP without warnings...
+ set +vx
./compile.at:172: /lib/cpp </dev/null || exit 77
+ /lib/cpp
+ exit 77
stderr:
/lib/cpp: not found
stdout:
37. ./compile.at:169: ok (skipped near `compile.at:172')

38. ./compile.at:206: testing AC_PROG_CPP via CC...
+ set +vx
./compile.at:209: /lib/cpp </dev/null || exit 77
+ /lib/cpp
+ exit 77
stderr:
/lib/cpp: not found
stdout:
38. ./compile.at:206: ok (skipped near `compile.at:209')
=======================================
All 2 tests were successful (2 skipped)
=======================================

> Grrr...
> 
> What does ./testsuite -x -v 15 report?

results (new testsuite.log also attached):

address@hidden ~/autoconf-2.50/tests
$ ./testsuite -x -v 15
================================
Test suite for GNU Autoconf 2.50
================================
15. ./m4sh.at:12: testing AS_DIRNAME & AS_DIRNAME_SED...
+ cat
+ set +vx
./m4sh.at:50: autoconf --autoconf-dir .. -l $at_srcdir
+ autoconf --autoconf-dir .. -l /home/dcarter/autoconf-2.50/tests
+ set +vx
./m4sh.at:51: top_srcdir=$top_srcdir ./configure
+ top_srcdir=.. ./configure
--- /dev/null   Tue May 22 11:56:38 2001
+++ at-stderr   Tue May 22 11:56:38 2001
@@ -0,0 +1 @@
+./configure: not found
stdout:
./m4sh.at:51: exit code was 127, expected 0
./m4sh.at:51: config.log
cat: config.log: No such file or directory
15. ./m4sh.at:12: FAILED near `m4sh.at:51'
==============================================
ERROR: Suite unsuccessful, 1 of 1 tests failed
==============================================

Writing `debug-NN.sh' scripts, NN = 15, done

You may investigate any problem if you feel able to do so, in which
case the testsuite provide a good starting point.

Now, failed tests will be executed again, verbosely, and logged
in the file ./testsuite.log.
================================
Test suite for GNU Autoconf 2.50
================================
15. ./m4sh.at:12: testing AS_DIRNAME & AS_DIRNAME_SED...
./m4sh.at:50: autoconf --autoconf-dir .. -l $at_srcdir
./m4sh.at:51: top_srcdir=$top_srcdir ./configure
--- /dev/null   Tue May 22 11:56:50 2001
+++ at-stderr   Tue May 22 11:56:50 2001
@@ -0,0 +1 @@
+./configure: not found
stdout:
./m4sh.at:51: exit code was 127, expected 0
./m4sh.at:51: config.log
cat: config.log: No such file or directory
15. ./m4sh.at:12: FAILED near `m4sh.at:51'
==========================
./testsuite.log is created
==========================

Please send `./testsuite.log' to <address@hidden> together with all
the information you think might help.

testsuite.log
Description: Binary data