Re: Call for testing CVS Autoconf

[Lars Hecking]

Akim Demaille writes:
> >>>>> "Pavel" == Pavel Roskin <address@hidden> writes:
> 
> >> 67. ./syntax.at:27 FAILED near `syntax.at:27'
> 
> Pavel> AC_F77_WRAPPERS
> 
> I suppose you have a Fortran compiler on this machine, but not GNU.
> Autoconf has indeed weaknesses wrt Fortran support.
 
 I just realise that this machine has no Fortran compiler at all.
 We have kept only a few SunOS 4 machines for specific tasks, and
 all sw upgrades have ceased. They're still running gcc 2.8.1.

> >> 80. ./syntax.at:40 FAILED near `syntax.at:40'
> 
> Pavel> AC_FUNC_MKTIME
> 
> Lars, could you
> 
>         cd ~tests
>         ./testsuite -v 80 >debug.log 2>&1

 Here's the result:

=========================================
Testing suite for autoconf, version 2.49b
=========================================
testing AC_FUNC_MKTIME
     80. ./syntax.at:40...
./syntax.at:40: autoconf --autoconf-dir .. -l $at_srcdir
./syntax.at:40: autoheader --autoconf-dir .. -l $at_srcdir
./syntax.at:40: top_srcdir=$top_srcdir ./configure
--- empty       Thu Nov 30 10:10:47 2000
+++ stderr      Thu Nov 30 10:13:46 2000
@@ -0,0 +1 @@
+./configure: 24794 Alarm call
loading cache /dev/null
checking for gcc... gcc
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking whether we are using the GNU C compiler... yes
checking for object suffix... o
checking for executable suffix... 
checking whether gcc accepts -g... yes
checking whether time.h and sys/time.h may both be included... yes
checking how to run the C preprocessor... gcc -E
checking for sys/time.h... yes
checking for unistd.h... yes
checking for alarm... yes
checking for working mktime... no
creating ./config.status
creating config.h
     80. ./syntax.at:40: FAILED near `syntax.at:40'

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

==============================================
ERROR: Suite unsuccessful, 1 of 1 tests failed
==============================================

When reporting failed tests to maintainers, do not merely list test
numbers, as the numbering changes between releases and pretests.
Be careful to give at least all the information you got about them.
You may investigate any problem if you feel able to do so, in which
case the testsuite provide a good starting point.
information.  Now, failed tests will be executed again, verbosely.
=========================================
Testing suite for autoconf, version 2.49b
=========================================
testing AC_FUNC_MKTIME
     80. ./syntax.at:40...
./syntax.at:40: autoconf --autoconf-dir .. -l $at_srcdir
./syntax.at:40: autoheader --autoconf-dir .. -l $at_srcdir
./syntax.at:40: top_srcdir=$top_srcdir ./configure
--- empty       Thu Nov 30 10:14:43 2000
+++ stderr      Thu Nov 30 10:17:39 2000
@@ -0,0 +1 @@
+./configure: 25271 Alarm call
loading cache /dev/null
checking for gcc... gcc
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking whether we are using the GNU C compiler... yes
checking for object suffix... o
checking for executable suffix... 
checking whether gcc accepts -g... yes
checking whether time.h and sys/time.h may both be included... yes
checking how to run the C preprocessor... gcc -E
checking for sys/time.h... yes
checking for unistd.h... yes
checking for alarm... yes
checking for working mktime... no
creating ./config.status
creating config.h
     80. ./syntax.at:40: FAILED near `syntax.at:40'

=========================================
Testing suite for autoconf, version 2.49b
=========================================