Hello Václav, thanks for the bug report.
* v.hais...@sh.cvut.cz wrote on Tue, Feb 23, 2010 at 02:33:38PM CET: > I am reporting the results of make check run for autoconf-2.65 on my FreeBSD > 7.2 box. testsuite.dir tar ball is attached, if it does not make it through, > it is also available as on > <http://shell.sh.cvut.cz/~wilx/testsuite.dir-2.65-20100221.tar.bz2>. I can reproduce these two failures on FreeBSD 6.4 (i386): > 35. tools.at:1174: testing ... > ../../tests/tools.at:1191: : > sub/some-file && exit 77 > stderr: > /home/users/wilx/tmp/autoconf-2.65/objdir/tests/testsuite.dir/at-groups/35/test-source: > cannot create sub/some-file: Permission denied > stdout: > ../../tests/tools.at:1191: exit code was 2, expected 1 > 35. tools.at:1174: 35. autom4te cache creation (tools.at:1174): FAILED > (tools.at:1191) > 239. c.at:57: testing ... > ../../tests/c.at:65: autoconf --force > ../../tests/c.at:66: ./configure $configure_options > stderr: > configure: error: in > `/home/users/wilx/tmp/autoconf-2.65/objdir/tests/testsuite.dir/239': > configure: error: C compiler cannot create executables > See `config.log' for more details. > stdout: > checking for gcc... no-such-compiler > checking whether the C compiler works... no > ../../tests/c.at:66: exit code was 1, expected 77 The second is us failing to adhere to '(autoconf.info)Shell Functions': Likewise, the state of `$?' is not reliable when entering a shell function. in AS_ERROR. The first seems to be a genuine shell error difference (from glancing at SUSv3 I can only gather that a failed redirection should result in an exit status > 0, but no further specification). I'm assuming the rest of the failures, which happen because no Fortran compiler is installed, are due to the same issue as 239. I'm working on a fix. Sorry BTW for not seeing this sooner, I somehow managed to not exclude bash from the list of candidate shells on my FreeBSD test system. Thanks, Ralf