sys-devel/automake-1.10.1 fails tests on ppc64: [...] FAIL: instsh2.test [...] ===================================== 1 of 584 tests failed (30 tests were not run) Please report to bug-automake@gnu.org ===================================== This does not happen with sys-devel/automake-1.10. # ./instsh2.test /var/tmp/portage/sys-devel/automake-1.10.1/work/automake-1.10.1/tests:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:/usr/powerpc64-unknown-linux-gnu/gcc-bin/4.1.2:/opt/ibm-jdk-bin-1.4.2.10/bin:/opt/ibm-jdk-bin-1.4.2.10/jre/bin:/usr/kde/3.5/sbin:/usr/kde/3.5/bin:/usr/qt/3/bin === Running test ./instsh2.test ++ pwd /var/tmp/portage/sys-devel/automake-1.10.1/work/automake-1.10.1/tests/testSubDir + set -e + ./install-sh ./install-sh: no input file specified. + ./install-sh -m 644 dest ./install-sh: no input file specified. + ./install-sh -d + ./install-sh -d d0 + test -d d0 + ./install-sh -d d1 d2 d3 d4 + test -d d1 + test -d d2 + test -d d3 + test -d d4 + ./install-sh -d p1/p2/p3 p4//p5//p6// + test -d p1/p2/p3 + test -d p4/p5/p6 + : + ./install-sh -c -m 644 x y + test -f x + test -f y + ./install-sh -m 644 y z + test -f y + test -f z + ./install-sh -m 644 -c x z d1 + test -f x + test -f z + test -f d1/x + test -f d1/z + ./install-sh -m 644 x z d2// + test -f x + test -f z + test -f d2/x + test -f d2/z + ./install-sh -t d3 -m 644 x z + test -f x + test -f z + test -f d3/x + test -f d3/z + ./install-sh -t d4// -m 644 x z + test -f x + test -f z + test -f d4/x + test -f d4/z + ./install-sh -T x d3/y + test -f x + test -f d3/y + ./install-sh -T x d3 ./install-sh: d3: Is a directory + ./install-sh -T x d4// ./install-sh: d4//: Is a directory + echo foo + ./install-sh -C file d1 + TZ=UTC0 + touch -t 198309271735.59 d1/file + ./install-sh -C file d1 + is_newest file d1/file ++ find file d1/file -newer file + test x = x + echo foo1 + ./install-sh -C file d1 + diff file d1/file + ./install-sh -C -m 444 file d1 + test -r d1/file + test '!' -w d1/file # echo $? 1
Same on alpha/ia64/sparc/x86
ive added the fix already in upstream ... the error is harmless, so it's safe to ignore