[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lilypond-auto] Issue 3488 in lilypond: Patch: lily/parser.yy: Use %
From: |
lilypond |
Subject: |
Re: [Lilypond-auto] Issue 3488 in lilypond: Patch: lily/parser.yy: Use %define api.pure instead of %pure_parser |
Date: |
Mon, 05 Aug 2013 15:09:20 +0000 |
Updates:
Cc: jan.nieuwenhuizen address@hidden
Comment #6 on issue 3488 by address@hidden: Patch: lily/parser.yy: Use %define
api.pure instead of %pure_parser
http://code.google.com/p/lilypond/issues/detail?id=3488
Cripes. Can we upgrade to 2.5 at least? That's the version in Ubuntu
13.04 so it has seen a lot of exposure for work on LilyPond. I suspect
that newer versions would also be ok, but there is probably little
incentive to rush here.
I can't imagine much of a problem with the requirements of 2.5 for
building. Because of its role in bootstrapping, Bison tends to be pretty
careful regarding portability.
--
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
- [Lilypond-auto] Issue 3488 in lilypond: Patch: lily/parser.yy: Use %define api.pure instead of %pure_parser, lilypond, 2013/08/05
- Re: [Lilypond-auto] Issue 3488 in lilypond: Patch: lily/parser.yy: Use %define api.pure instead of %pure_parser, lilypond, 2013/08/05
- Re: [Lilypond-auto] Issue 3488 in lilypond: Patch: lily/parser.yy: Use %define api.pure instead of %pure_parser, lilypond, 2013/08/05
- Re: [Lilypond-auto] Issue 3488 in lilypond: Patch: lily/parser.yy: Use %define api.pure instead of %pure_parser, lilypond, 2013/08/05
- Re: [Lilypond-auto] Issue 3488 in lilypond: Patch: lily/parser.yy: Use %define api.pure instead of %pure_parser, lilypond, 2013/08/05
- Re: [Lilypond-auto] Issue 3488 in lilypond: Patch: lily/parser.yy: Use %define api.pure instead of %pure_parser, lilypond, 2013/08/05
- Re: [Lilypond-auto] Issue 3488 in lilypond: Patch: lily/parser.yy: Use %define api.pure instead of %pure_parser,
lilypond <=
- Re: [Lilypond-auto] Issue 3488 in lilypond: Patch: lily/parser.yy: Use %define api.pure instead of %pure_parser, lilypond, 2013/08/05
- Re: [Lilypond-auto] Issue 3488 in lilypond: Patch: lily/parser.yy: Use %define api.pure instead of %pure_parser, lilypond, 2013/08/06
- Re: [Lilypond-auto] Issue 3488 in lilypond: Patch: lily/parser.yy: Use %define api.pure instead of %pure_parser, lilypond, 2013/08/06
- Re: [Lilypond-auto] Issue 3488 in lilypond: Patch: lily/parser.yy: Use %define api.pure instead of %pure_parser, lilypond, 2013/08/08
- Re: [Lilypond-auto] Issue 3488 in lilypond: Patch: lily/parser.yy: Use %define api.pure instead of %pure_parser, lilypond, 2013/08/11