lilypond-auto
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Lilypond-auto] Issue 3577 in lilypond: Patch: Build: Fix bison-less


From: lilypond
Subject: Re: [Lilypond-auto] Issue 3577 in lilypond: Patch: Build: Fix bison-less build from tarball.
Date: Tue, 01 Oct 2013 08:57:53 +0000


Comment #12 on issue 3577 by address@hidden: Patch: Build: Fix bison-less build from tarball.
http://code.google.com/p/lilypond/issues/detail?id=3577

I have no actual idea why the presence of Documentation/out/ly-grammar.txt should make _any_ difference for an out-of-tree build.

Or why deleting the autoconf cache should make a difference. Now clearly we also have the problem that the dependencies for ly-grammar.txt are wrong: I see
git grep ly-grammar.txt
Documentation/GNUmakefile:OUT_DIST_FILES = $(outdir)/ly-grammar.txt
Documentation/GNUmakefile:$(outdir)/notation.texi: $(outdir)/ly-grammar.txt
Documentation/GNUmakefile:$(outdir)/ly-grammar.txt: $(top-src-dir)/lily/parser.yy
Documentation/contributor.texi:@verbatiminclude ly-grammar.txt
Documentation/de/notation.tely:@verbatiminclude ly-grammar.txt
So we have an outdated dependency of notation.texi on ly-grammar.txt but it turns out that even that outdated dependency simply was wrong since notation.texi will _still_ contain the @verbatiminclude and consequently _not_ depend on ly-grammar.txt. What actually depends on ly-grammar.txt is any target compiled _from_ notation.texi. Or now, contributor.texi.

We still need to fix that. But in the mean time, we can reduce the number of points we need to take care of by forcing the Bison dependency. That also avoids Heisenbugs based on whether Bison is run or not.

--
You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings



reply via email to

[Prev in Thread] Current Thread [Next in Thread]