Hi - Having just built GNU coreutils-8.12 against GNU libc 2.13,
coreutils SKIPS a test normally run as part of "make check"
because "system getcwd() is buggy" :
(after coreutils-8.12 'configure' and 'make -j2' succeeds :)
$ make check
...
./misc/pwd-unreadable-parent: skipping test: can't use buggy system getcwd
SKIP: misc/pwd-unreadable-parent
...
=======================
All 221 tests passed
(25 tests were not run)
=======================
make[6]: Leaving directory `/tmp/coreutils-8.12/gnulib-tests'
make[5]: Leaving directory `/tmp/coreutils-8.12/gnulib-tests'
make[4]: Leaving directory `/tmp/coreutils-8.12/gnulib-tests'
make[3]: Leaving directory `/tmp/coreutils-8.12/gnulib-tests'
make[2]: Leaving directory `/tmp/coreutils-8.12/gnulib-tests'
make[2]: Entering directory `/tmp/coreutils-8.12'
make[2]: Nothing to be done for `check-am'.
make[2]: Leaving directory `/tmp/coreutils-8.12'
make[1]: Leaving directory `/tmp/coreutils-8.12'
[ root@jvdspc:/tmp/coreutils-8.12 19:10:50 1717:1210 ]
$ echo $?
0
$ DESTDIR=`pwd`/inst make install
I think it's a shame that the latest stable GNU coreutils thinks the latest stable GNU libc's getcwd() is "buggy" . Why is this ? Why not get glibc fixed if it is "buggy" before releasing a coreutils that complains about it ? I'll investigate further - I don't know if this is a glibc bug or a coreutils bug so I raised glibc bug #12713 about this also. Just though I'd should let you know, and thanks for an otherwise flawless coreutils, Jason (JVD) <[email protected]>
