While checking for regressions in very old m4 patches I hadn't gotten round to submitting, I notice that the HEAD revision of both branch-1.4 and branch-1.6 fail this test:
; cd Devo/m4--release--1.4 ; git pull && ./bootstrap && mkdir +build && cd +build && ../configure && make all check [[...]] PASS: test-vc-list-files-git.sh FAIL: test-vc-list-files-cvs.sh PASS: test-version-etc.sh PASS: test-wchar PASS: test-wcrtomb.sh PASS: test-wctype PASS: test-xalloc-die.sh PASS: test-xmemdup0 PASS: test-xvasprintf =============================== 1 of 115 tests failed See tests/test-suite.log Please report to bug-m4@gnu.org =============================== [[...]] ; cat tests/test-suite.log ================================================ GNU M4 1.4.14.1-a90f: tests/test-suite.log ================================================ 1 of 102 tests failed. (1 test was not run). .. contents:: :depth: 2 SKIP: test-c-stack2.sh (exit: 77) ================================= cannot tell stack overflow from crash; consider installing libsigsegv FAIL: test-vc-list-files-cvs.sh (exit: 1) ========================================= find: illegal option -- - ind: illegal option -- - ind: illegal option -- t ind: illegal option -- y ind: illegal option -- p ind: illegal option -- e ind: illegal option -- = ind: illegal option -- A ind: illegal option -- F ind: illegal option -- G ind: illegal option -- M find: ind: No such file or directory --- expected 2010-05-28 11:36:21.000000000 +0700 +++ actual 2010-05-28 11:36:21.000000000 +0700 @@ -1,3 +1,3 @@ -b -c -d/a +.: +? actual +? expected Obviously, the test is assuming GNU find (which is called gfind on my machine, but it doesn't come with Mac OS, which ships only BSD find), but with a cursory look around I couldn't see where the failing find was invoked. With gfind in my PATH, I also tried rerunning the testsuite with: ; FIND=gfind make check ...but I get the same failure. Cheers, -- Gary V. Vaughan (g...@gnu.org)
