Bob Friesenhahn bfriesen at simple.dallas.tx.us writes:
The testsuite.log showing a failed test under Solaris 10 is attached.
And the interesting portion:
! 144. base.at:295: testing ...
! /home/bfriesen/src/gnu/autoconf-2.63/tests/base.at:302: autoconf --force
!
On a Linux/x86 system, I'm getting a test failure:
7: autoconf --trace: builtins ok
8: autoconf: forbidden tokens, basic FAILED (tools.at:360)
9: autoconf: forbidden tokens, exceptions ok
The file tests/testsuite.dir/008/testsuite.log is as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bruno Haible on 9/10/2008 4:26 PM:
When I rename my $HOME/.autom4te.cfg to some other filename, the test
succeeds. When I rename it back, the test fails again.
The test is apparently assuming that the second autoconf run will
