Hello Jay. Thanks for theport. On Thursday 19 August 2010, Jay K wrote: > > Once the run of `make -k' is terminated, can you send the files > > `tests/test-suite.log', `lib/Automake/tests/test-suite.log' and > > `config.log' to bug-autom...@gnu.org? This way other developers > > can jump in and analyze the failures. > > > > Thanks again for your contribution, > > Stefano > > I didn't see tests/test-suite.log, Ouch, that's bad. This problem is most probably due to... > make[2]: Leaving directory `/home/jayk/obj/automake/tests' > make check-TESTS > make[2]: Entering directory `/home/jayk/obj/automake/tests' > Stack overflow: pid 14948, proc ksh, addr 0x11dffffe0, pc > 0x3ff801bbf28 make[3]: Entering directory > `/home/jayk/obj/automake/tests' ... this crash, which prevented a complete run of the testsuite (at least all the `[t-z]*.test' and `*-p.test' tests weren't run, and the `test-suite.log' report wasn't generated).
Is your /bin/sh a Korn Shell in disguise? Do you happen to have bash installed on your system? If yes, could you try to run the following command in your Automake build directory to see if the run of the testuite completes? $ (cd tests && make TEST_LOG_COMPILER=/path/to/bash check) If yes, would you care to send the `test-suite.log' resulting from this run? > so how about this: > > tar zcf testlogs.tar.gz config.log tests/*.log > lib/Automake/tests/test-suite.log > => > http://modula3.elegosoft.com/cm3/uploaded-archives/testlogs.tar.gz Yes, this helps. Thank you. > Note: this is old even for OSF/1, being 5.1, not 5.1a, 5.1b, 5.1f, > etc. > FAIL: distdir.test > FAIL: extra5.test > FAIL: extra6.test > FAIL: extra7.test > FAIL: fn99.test > FAIL: fn99subdir.test > FAIL: nobase-libtool.test Hhmmm... all the failures except the last one seem due to strange failures of the `cp' utility... is the cp in your PATH GNU cp, or the system cp? Thanks, Stefano
