> > build m4.spec
> > + autoreconf --force --install
> > configure.ac:20: error: Autoconf version 2.60 or higher is required
>
> That's your problem. 'build' is too complicated, and tries to invoke too
> many tools. Do NOT use 'build' for bootstrapping your installation.
I commented the autoreconf invokation and reran
build m4.spec
This time, compilation worked!
So indeed, m4 does not require autoconf - unless you insist on rebuilding its
configure script using autoconf, either directly, or indirectly (e.g. through a
call to autoreconf). I suggest to add the "unless" part to the FAQ.
But now,
make check
results in 1 failed test:
...
PASS: test-frexp-nolibm
PASS: test-frexpl-nolibm
PASS: test-fseeko.sh
Skipping test: ungetc cannot handle arbitrary bytes
SKIP: test-fseeko2.sh
test-ftello.c:119: assertion failed
./test-ftello.sh: line 3: 11120 Aborted ./test-ftello${EXEEXT}
1 <"$srcdir/test-ftello.sh"
FAIL: test-ftello.sh
Skipping test: ungetc cannot handle arbitrary bytes
SKIP: test-ftello2.sh
PASS: test-getdtablesize
PASS: test-gettimeofday
PASS: test-isnand-nolibm
...
===============================
1 of 74 tests failed
(3 tests were not run)
Please report to bug...@gnu.org
===============================
make[5]: *** [check-TESTS] Error 1
I regard the "Autoconf requires m4 and m4 requires autoconf" problem resolved
at this point - thanks for all the help and patience!
But now, what do I do with the failed test? Do I really have to report to
bug...@gnu.org, or can we continue from here?
--
Regards
Chris Karakas
http://www.karakas-online.de
