I find that in my patchy runs, I get directories /tmp/lilypond-autobuild (my configured build directory) and a hierarchy of "build" directories under it, possibly one per tested patch (?).
Here is the output of ls /tmp/lilypond-autobuild/build/build/build/build/ GNUmakefile local.make If I look in those files, I see 2012-03-19 10:46 /tmp/lilypond-autobuild/build/build/build/build/GNUmakefile Page 1 depth=../../../ include $(depth)/config$(if $(conf),-$(conf),).make include $(configure-srcdir)/./build/build/build/GNUmakefile MODULE_INCLUDES += $(src-dir)/$(outbase) ^L 2012-03-19 10:46 /tmp/lilypond-autobuild/build/build/build/build/local.make Page 1 include $(depth)/config$(if $(conf),-$(conf),).make include $(configure-srcdir)/./build/build/build/local.make ^L So it looks like there is some configure process going on that creates continuously deeper nestings of the "build" directory. One level above we have ls -R /tmp/lilypond-autobuild/build/build/build/ /tmp/lilypond-autobuild/build/build/build/: build flower lily make ps scripts vim Documentation GNUmakefile local.make mf python stepmake elisp input ly po scm tex /tmp/lilypond-autobuild/build/build/build/build: GNUmakefile local.make /tmp/lilypond-autobuild/build/build/build/Documentation: GNUmakefile /tmp/lilypond-autobuild/build/build/build/elisp: GNUmakefile /tmp/lilypond-autobuild/build/build/build/flower: GNUmakefile /tmp/lilypond-autobuild/build/build/build/input: GNUmakefile /tmp/lilypond-autobuild/build/build/build/lily: GNUmakefile /tmp/lilypond-autobuild/build/build/build/ly: GNUmakefile /tmp/lilypond-autobuild/build/build/build/make: abc-rules.make lilypond-rules.make musicxml-rules.make abc-targets.make lilypond-targets.make musicxml-targets.make abc-vars.make lilypond-vars.make musicxml-vars.make doc-i18n-root-rules.make ly.make mutopia-inclusions.make doc-i18n-root-targets.make ly-rules.make mutopia-rules.make doc-i18n-root-vars.make lysdoc-rules.make mutopia-targets.make generic-rules.make lysdoc-targets.make mutopia-vars.make generic-targets.make lysdoc-vars.make stepmake.make generic-vars.make ly-targets.make substitute.make GNUmakefile ly-vars.make toplevel-version.make lilypond-book-rules.make midi-rules.make website.make lilypond-book-targets.make midi-targets.make lilypond-book-vars.make midi-vars.make /tmp/lilypond-autobuild/build/build/build/mf: GNUmakefile /tmp/lilypond-autobuild/build/build/build/po: GNUmakefile /tmp/lilypond-autobuild/build/build/build/ps: GNUmakefile /tmp/lilypond-autobuild/build/build/build/python: GNUmakefile /tmp/lilypond-autobuild/build/build/build/scm: GNUmakefile /tmp/lilypond-autobuild/build/build/build/scripts: GNUmakefile /tmp/lilypond-autobuild/build/build/build/stepmake: GNUmakefile /tmp/lilypond-autobuild/build/build/build/tex: GNUmakefile /tmp/lilypond-autobuild/build/build/build/vim: GNUmakefile So it looks like the "recursion" focuses on the Makefiles. Does anybody have a clue what this is about? -- David Kastrup _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
