lilypond-devel
[Top][All Lists]
Advanced

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

Re: GUB failure in parser.yy


From: David Kastrup
Subject: Re: GUB failure in parser.yy
Date: Sat, 22 Sep 2012 17:56:39 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2.50 (gnu/linux)

"Phil Holmes" <address@hidden> writes:

> I'm trying to build 2.17.3.  I get this failure:
>
> make[1]: Entering directory
> /home/gub/gub/target/darwin-ppc/build/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/lily'
> bison -o out/parser-tmp.cc -d 
> /home/gub/gub/target/darwin-ppc/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/lily/parser.yy
> /home/gub/gub/target/darwin-ppc/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/lily/parser.yy:30.1-5:
> invalid directive: `%code'
> /home/gub/gub/target/darwin-ppc/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/lily/parser.yy:30.7-14:
> syntax error, unexpected identifier
> make[1]: *** [out/parser.hh] Error 1
>
> I'll have another go once this is fixed.

That would likely be a Bison version that is too old.  There are two
options to deal with it:

a) update the required version of Bison in the configure script and in GUB
b) try to make do without %code

I'd prefer option a) since a smaller range of supported versions makes
for fewer surprises, in particular since I was planning to make some
changes soon that will require somewhat predictable details in the
generated Bison code.

It is just the question how much pain requiring newer versions will be.
"Let's keep GUB old" is not really an overly convincing reason, but if
it breaks other supported configurations, that might be cause to
retract.

-- 
David Kastrup



reply via email to

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