Bruno Haible <[EMAIL PROTECTED]> wrote: > Hi Jim, > >> Here's what I hope will be the final snapshot before 6.11: > > There's still a lot to fix for MacOS X 10.5.2 (the current release of > MacOS X). Find attached the log files from > > ./configure --prefix=/Users/bruno/data/local-macos CPPFLAGS=-Wall > make > make -k check > > $ grep FAIL: check.log > FAIL: help-version.log > FAIL: parent-perm.log > FAIL: file-perm-race.log > FAIL: parent-perm-race.log > FAIL: existing-perm-race.log > FAIL: backup-dir.log > FAIL: src-base-dot.log > FAIL: preserve-2.log > FAIL: fail-perm.log > FAIL: cp-parents.log > FAIL: parent-perm.log (exit: 1) > FAIL: file-perm-race.log (exit: 1) > FAIL: parent-perm-race.log (exit: 1) > FAIL: existing-perm-race.log (exit: 1) > FAIL: backup-dir.log (exit: 1) > FAIL: src-base-dot.log (exit: 1) > FAIL: preserve-2.log (exit: 1) > FAIL: fail-perm.log (exit: 1) > FAIL: cp-parents.log (exit: 1) > FAIL: basic-1.log > FAIL: create-leading.log > FAIL: basic-1.log (exit: 1) > FAIL: create-leading.log (exit: 1) > FAIL: misc.log > FAIL: misc.log (exit: 1) > > Can you already guess the causes, based on the log files?
Hi Bruno, Thanks for reporting all that. However, I suspect the vast majority of the trouble is due to infrastructure problems rather than bugs in the tools themselves. It's as if whatever shell it's using is not honoring $PATH and thus s running system-supplied versions of the tools rather than the just-built ones from coreutils. Can you run the tests again, but this time so that they use bash? I.e., if you have installed bash in /usr/local/bin/bash, do this: make check PREFERABLY_POSIX_SHELL=/usr/local/bin/bash _______________________________________________ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils
