baldu...@units.it writes:
[...]
>> Can you check which (if any) of parser.cc and parser.hh get rebuilt for
>> you? It's likely that one of the two is kept in the version from the
>> tarball while the other is recreated with a different Bison, and this
>> mismatch is what is causing the problems.
>
> Oopsie daisy. The idea behind that might be that one can build a
> version of LilyPond without having flex/bison available at all. That
> makes sense for bootstrapping things like, well, flex/bison/gcc and so
> on.
oops, sorry for being so naive: I did not even consider such a
perspective;
baldu...@units.it writes:
> hi there,
>
> > I've just installed a version of bison-3.0 in a temporary directory and
> > used that for compilation. No problem whatsoever. Huh.
> >
> > And parser.cc does start with
> >
> > /* A Bison parser, made by GNU Bison 3.0. */
>
hi there,
> I've just installed a version of bison-3.0 in a temporary directory and
> used that for compilation. No problem whatsoever. Huh.
>
> And parser.cc does start with
>
> /* A Bison parser, made by GNU Bison 3.0. */
>
> /* Bison implementation for Yacc
gabriele balducci writes:
> hello,
>
>
> >> I've tried that but see a new error while generating documentation:
> >>
> >>
> /scratch/wip/lilypond-devel/work/lilypond-2.17.24/out/share/lilypond/current/ly/chord-modifiers-init.ly:26:4:
> error: syntax error, unexpected REAL
> >> <
> >>
hello,
>> I've tried that but see a new error while generating documentation:
>>
>>
/scratch/wip/lilypond-devel/work/lilypond-2.17.24/out/share/lilypond/current/ly/chord-modifiers-init.ly:26:4:
error: syntax error, unexpected REAL
>> <
>>c e gis>1-\markup { "+" }
>
> Nothing t
Thomas Klausner writes:
> I've tried that but see a new error while generating documentation:
>
> /scratch/wip/lilypond-devel/work/lilypond-2.17.24/out/share/lilypond/current/ly/chord-modifiers-init.ly:26:4:
> error: syntax error, unexpected REAL
> <
>c e gis>1-\markup { "+" }
Nothing the
On Wed, Aug 14, 2013 at 09:35:46PM +0200, David Kastrup wrote:
> Marek Klein writes:
>
> > Hello David,
> > do we need a tracker issue for this?
> >
> > Marek
> >
> > 2013/8/5 David Kastrup
> >
> >> Thomas Klausner writes:
> >>
> >> > Hi!
> >> >
> >> > The latest stable and development branches
Marek Klein writes:
> Hello David,
> do we need a tracker issue for this?
>
> Marek
>
> 2013/8/5 David Kastrup
>
>> Thomas Klausner writes:
>>
>> > Hi!
>> >
>> > The latest stable and development branches of lilypond do not compile
>> with
>> > the recently released bison-3.0.
>> >
>> > The fol
Hello David,
do we need a tracker issue for this?
Marek
2013/8/5 David Kastrup
> Thomas Klausner writes:
>
> > Hi!
> >
> > The latest stable and development branches of lilypond do not compile
> with
> > the recently released bison-3.0.
> >
> > The following patch fixes this (sorry, whitespace
Thomas Klausner writes:
> Hi!
>
> The latest stable and development branches of lilypond do not compile with
> the recently released bison-3.0.
>
> The following patch fixes this (sorry, whitespace may be off):
>
> --- lily/parser.yy.orig 2013-01-04 13:41:57.0 +
> +++ lily/parser.yy
>
Hi!
The latest stable and development branches of lilypond do not compile with
the recently released bison-3.0.
The following patch fixes this (sorry, whitespace may be off):
--- lily/parser.yy.orig 2013-01-04 13:41:57.0 +
+++ lily/parser.yy
@@ -100,7 +100,7 @@ or
-%pure_parser
12 matches
Mail list logo
