Jim Meyering wrote: ... >> FYI, here's another make distcheck problem, ... > And here's another: ... > make[3]: Makefile: No such file or directory > make[3]: *** No rule to make target `Makefile'. Stop. > make[3]: Entering directory > /h/j/w/co/cu/tests/torture/coreutils/test/coreutils-8.19.68-ea804-dirty' > Making distclean in lib > make[4]: Entering directory > /h/j/w/co/cu/tests/torture/coreutils/test/coreutils-8.19.68-ea804-dirty/lib'
I tracked that to a now-stale use of -C src -f Makefile. You're welcome to merge this into the appropriate patch: diff --git a/dist-check.mk b/dist-check.mk index 6706ea0..6e5726a 100644 --- a/dist-check.mk +++ b/dist-check.mk @@ -11,8 +11,8 @@ pfx=$(t)/i built_programs = \ $$(echo 'spy:;@echo $$(bin_PROGRAMS)' \ - | MAKEFLAGS= $(MAKE) -s -C src -f Makefile -f - spy \ - | fmt -1 | sed 's,$(EXEEXT)$$,,' | sort -u) + | MAKEFLAGS= $(MAKE) -s -f Makefile -f - spy \ + | fmt -1 | sed 's,src/,,;s,$(EXEEXT)$$,,' | sort -u) # More than once, tainted build and source directory names would # have caused at least one "make check" test to apply "chmod 700"
