Re: build problem with lilypond-2.17.24 & 25

[David Kastrup]

Thomas Klausner <address@hidden> writes:

>> Can you also report which of the preexisting files in lily/out/ gets
>> overwritten by the problematic build, and which not?
>
> The header file is not recreated, but the cc file is:
>
> -rw-r--r-- 1 pbulk builder 258460 Sep 2 07:14
> work/lilypond-2.17.25/lily/out/parser.cc
> -rw-r--r-- 1 pbulk builder 9822 Sep 2 07:14
> work/lilypond-2.17.25/lily/out/parser.dep
> -rw-r--r-- 1 pbulk builder 7646 Aug 25 14:42
> work/lilypond-2.17.25/lily/out/parser.hh
> -rw-r--r-- 1 pbulk builder 597408 Sep 2 07:14
> work/lilypond-2.17.25/lily/out/parser.o

I suspected Documention/GNUmakefile:

$(outdir)/notation.texi: $(outdir)/ly-grammar.txt

## Rules for the automatically generated documentation
$(outdir)/ly-grammar.txt: $(top-src-dir)/lily/parser.yy
        cd $(outdir) && $(BISON) -v $<
        $(buildscript-dir)/yyout2grammar $(outdir)/parser.output $@

I assume that we are not distributing out/ly-grammar.txt as well?  If we
don't, we likely should (as it can't be generated without bison).

But actually, this should not overwrite parser.cc but merely
parser.tab.cc, so this should not be the real reason.  I am somewhat at
a loss for the real reason, though.

-- 
David Kastrup