This is a configure test failing that I mentioned early on: rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags make[2]: Leaving directory `/usr/local/src/gnulib/libposix/libposix/libposix-2010.10.05/_build' rm -f config.status config.cache config.log configure.lineno configure.status.lineno rm -f Makefile ERROR: files left in build directory after distclean: ./core.9442 make[1]: *** [distcleancheck] Error 1 make[1]: Leaving directory `/usr/local/src/gnulib/libposix/libposix/libposix-2010.10.05/_build' make: *** [distcheck] Error 2 >build_distro> die 'make distcheck failed' >die> echo 'mk-libposix error: make distcheck failed' mk-libposix error: make distcheck failed >die> trap '' EXIT >die> kill -TERM 22043 Terminated
I don't know which one because the core only says "configure.c" for the source file. *Which* configure.c would that be? What if the configure tests were done in a subdirectory and the whole subdirectory were blown away on configure exiting? Then, you could easily name the .c's after the test and you'd know where the dinkleberries came from.
