Re: bison-3.0 fix lilypond

[Marek Klein]

Hello David,
do we need a tracker issue for this?

Marek

2013/8/5 David Kastrup <address@hidden>

> Thomas Klausner <address@hidden> 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.000000000 +0000
> > +++ lily/parser.yy
> > @@ -100,7 +100,7 @@ or
> >
> >
> >
> > -%pure_parser
> > +%pure-parser
> >  %locations
>
> That does not seem like a bison-3.0 fix: according to the documentation,
> %pure-parser is the right form even for 2.6.2.  The question is what
> effect the wrong declaration had, if any.
>
> > While I'm here, I'll just report a minor issue too:
> > scripts/auxiliar/cg-section.sh uses the unportable "==" operator for
> > test(1), only supported by bash, not even by GNU coreutils. Please use
> the
> > portable "=" instead.
>
> Typical bashism, yes.  Personally, I prefer using case/esac for almost
> everything.  That usually is quite more flexible and has been a shell
> builtin for quite longer than test.
>
> --
> David Kastrup
>
>
> _______________________________________________
> bug-lilypond mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/bug-lilypond
>



-- 
Marek Klein
0918 610 720
http://gregoriana.sk
Gregoriana on 
youtube<http://www.youtube.com/playlist?list=PLBQHqmaUgUMZ4Bd4w4heeQF9lV9L7BS-s>
Graduale Project <http://gregoriana.sk/graduale/>