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 07:22:40 +0000


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

We are currently having the problem that the released tar ball for 2.17.27 does not build with simple

./autogen.sh --noconf
mkdir build
cd build
../configure
make

I've spent already more than a day with attempts of reproducing this behavior in-tree. One key to the failure appears to be the presence of Documentation/out/ly-grammar.txt which is not found when building in a separate build directory. Creating such a file (even if empty) seems to make the failure appear even with older tarballs.

This is reproducible from a _fresh_ checkout (add an mkdir Documentation/out; touch Documentation/out/ly-grammar.txt to the front of the recipe). "make clean" or "make distclean" are not sufficient for getting back to a pristine state; instead you need to use git clean -x -d -f for the cleanup.

This "separate build directory" problem is _unique_ to the bison-less build as far as I can tell: autoconf is _always_ run in the _original_ directory.

Now there is more involved than just the build directory: clearly the dependencies on ly-grammar.txt are broken in the wake of issue 3015 which failed to adjust them. The German translation still includes the grammar for some reason, however.

And I think there was work added for generating dependencies for includes. That stuff is likely fragile against moving the build directory, and pregenerated files do not help with that and get minimal testing.

So my vote is strongly on stopping Bison being an optional dependency. We don't make Flex optional, either.

Without the pregenerated grammar files, we have a whole dark corner regarding separate build dir, source/derived distinction and file modification date dependency _gone_. Sure, it is an interesting intellectual challenge to get all that right, but it does not buy us anything important, and we have lousy test coverage for it.

--
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]