Graham Percival <[email protected]> writes: > On Thu, Dec 22, 2011 at 06:17:57AM -0800, Graham Percival wrote: >> That order of commands suggests that lily-lexer-scheme.cc does not >> depend on parser.cc. I see that it contains such an #include, so >> I would assume that make would catch it... but apparently not. > > Skimming through lily/GNUmakefile, this makes sense. There's a > couple of explicit dependencies for parser.hh, but these don't > mention lily-lexer-scheme.cc, which is the file that triggers the > fail.
But the out/lily-lexer-scheme.dep file mentions it in the last line: ../flower/include/arithmetic-operator.hh include/pitch.hh out/parser.hh Does that mean that we generate the dependencies without actually using them? That sounds rather stupid, but then I don't understand the build system anyhow. > Could somebody check this in more detail, then add the required > dependencies to lily/GNUmakefile? Push directly to staging. I'll check what is there. As I said already: the single-job build does not appear to have a problem. Sorry for the inconvenience, but that was really unforeseeable for me. -- David Kastrup _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
