bug-autoconf
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Subject: [GNU Autoconf 2.59] testsuite: 40 41 51 183 failed


From: John L. Ries
Subject: Re: Subject: [GNU Autoconf 2.59] testsuite: 40 41 51 183 failed
Date: Fri, 7 Apr 2006 11:19:59 -0700 (PDT)

After compiling and installing Automake 1.9, the number of failures is down to 2 (51 and 183).

--------------------------|
John L. Ries              |
Salford Systems           |
Phone: (619)543-8880 x107 |
or     (435)865-5723      |
--------------------------|


On Wed, 5 Apr 2006, John L. Ries wrote:

Looks like I had Automake installed at one time and parts of it still remain. Probably the thing to do is to reinstall it and see if the three "flunkings" in question go away. Since my primary goal is to get GCC 4.1 to compile, I'll ignore the fourth "flunking" for now.

Thanks.

--------------------------|
John L. Ries              |
Salford Systems           |
Phone: (619)543-8880 x107 |
or     (435)865-5723      |
--------------------------|


On Wed, 5 Apr 2006, Ralf Wildenhues wrote:

Hi John,

* John L. Ries wrote on Wed, Apr 05, 2006 at 01:51:06AM CEST:
The Autoconf in question was built on a DEC 3000/600 under Tru64 UNIX 5.0
with GNU m4 1.4, Perl v5.8.6, and gawk 3.0.4.  Please let me know if you
need further information.

Well, it would be great if you could redo testing with the next alpha
release, which is hopefully done rather soon now.

But it's still quite interesting to take a look at this bug report, for
which I'd like to thank you.

Snipped to the important parts:

uname -m = alpha
uname -r = V5.0
uname -s = OSF1
uname -v = 910

ERROR: 182 tests were run,
4 failed unexpectedly.
1 test was skipped.

## ------------------------ ##
## Summary of the failures. ##
## ------------------------ ##
Failed tests:
GNU Autoconf 2.59 test suite test groups:

 NUM: FILENAME:LINE      TEST-GROUP-NAME
      KEYWORDS

  40: torture.at:558     Configuring subdirectories
      autoreconf
  41: torture.at:654     Deep Package
      autoreconf
  51: c.at:88            C keywords
 183: foreign.at:27      Libtool

Skipped tests:
GNU Autoconf 2.59 test suite test groups:

 NUM: FILENAME:LINE      TEST-GROUP-NAME
      KEYWORDS

   1: tools.at:47        Syntax of the shell scripts

## ---------------------- ##
## Detailed failed tests. ##
## ---------------------- ##

40. torture.at:558: testing ...
torture.at:562: aclocal --version || exit 77
stderr:
stdout:
aclocal (GNU automake) 1.5

torture.at:564: grep '1.[01234]' stdout && exit 77
stdout:
torture.at:607: autoreconf
stderr:
aclocal: couldn't open directory `/usr/local/share/aclocal': No such file or directory

I can only guess this was a bug in old Automake 1.5, since fixed.  But
maybe your installation of Automake is broken?  Its `make install' step
should have created that directory.

41. torture.at:654: testing ...
torture.at:658: aclocal --version || exit 77
stderr:
stdout:
aclocal (GNU automake) 1.5

torture.at:687: autoreconf -Wall -v
stderr:
Can't locate Automake/Struct.pm in @INC (@INC contains: /usr/local/share/automake /usr/local/lib/perl5/5.8.6/alpha-dec_osf-ld /usr/local/lib/perl5/5.8.6 /usr/local/lib/perl5/site_perl/5.8.6/alpha-dec_osf-ld /usr/local/lib/perl5/site_perl/5.8.6 /usr/local/lib/perl5/site_perl .) at /usr/local/bin/automake line 39.

Hmm.  I'd assume that the installation would search below
/usr/local/share/automake-1.5 and not /usr/local/share/automake.
That's what it does here.

BEGIN failed--compilation aborted at /usr/local/bin/automake line 39.
autoreconf: Entering directory `.'
autoreconf: configure.in: not using Gettext
autoreconf: running: aclocal  --output=aclocal.m4t
aclocal: couldn't open directory `/usr/local/share/aclocal': No such file or directory

Ditto.

autoreconf: aclocal failed with exit status: 2
stdout:
torture.at:687: exit code was 2, expected 0
41. torture.at:654: 41. Deep Package (torture.at:654): FAILED (torture.at:687)

51. c.at:88: testing ...
c.at:88: autoconf -W obsolete
c.at:88: autoheader
c.at:88: top_srcdir=$abs_top_srcdir ./configure
0a1
configure: error: failed to detect `const', `inline', `restrict', or `volatile' support

This failure is neat, because..

stdout:
./../../c.at:88: config.log
checking for gcc... gcc

checking for an ANSI C-conforming const... yes
checking for inline... inline
checking for C/C++ restrict keyword... no
checking for working volatile... yes
c.at:88: exit code was 1, expected 0

configure:1598: gcc --version </dev/null >&5
2.8.0

.. the test assumes that GCC has working support for volatile,
const, and restrict.  I know 2.95 has support for restrict, but
I don't know whether that was the first version to have it.
It seems though that 2.8.0 simply did not have it.  :-)

I guess we could restrict our test to not mind missing restrict in GCC
before 2.95.

configure:2388: checking for C/C++ restrict keyword
configure:2406: gcc -c -g -O2  conftest.c >&5
conftest.c:9: parse error before `x'

51. c.at:88: 51. C keywords (c.at:88): FAILED (c.at:88)


183. foreign.at:27: testing install-sh ltconfig libtool at-path ltmain.sh config.guess config.sub...
foreign.at:31: libtoolize --version || exit 77
stderr:
stdout:
libtoolize (GNU libtool) 1.4.2
foreign.at:39:
case `libtoolize --version |
      sed -n '/^.* \([0-9][0-9.a-z]*\)$/{s//\1/;p;q;}'` in
  0.*          ) exit 77;;
  1.[0123]*    ) exit 77;;
esac
stderr:
stdout:
foreign.at:51: libtoolize
stderr:
/usr/local/share/libtool: No such file or directory
libtoolize: cannot list files in `/usr/local/share/libtool'
stdout:
foreign.at:51: exit code was 1, expected 0
183. foreign.at:27: 183. Libtool (foreign.at:27): FAILED (foreign.at:51)

This libtoolize is from a rather old version of Libtool, too.
But again this looks like your installation is not complete.

Cheers,
Ralf

Attachment: testsuite.log
Description: Text document


reply via email to

[Prev in Thread] Current Thread [Next in Thread]