Re: GUB failure in parser.yy

[David Kastrup]

"Phil Holmes" <address@hidden> writes:

> ----- Original Message ----- 
> From: "David Kastrup" <address@hidden>
> To: "Phil Holmes" <address@hidden>
> Cc: "Devel" <address@hidden>
> Sent: Saturday, September 22, 2012 6:38 PM
> Subject: Re: GUB failure in parser.yy
>
>
>> "Phil Holmes" <address@hidden> writes:
>>
>>> My preference _right now_ would be to remove the code that's causing
>>> the old version of Bison a problem.  To fix Gub, rebuild Gub and then
>>> rebuild lilypond would take considerable time which I don't have now.
>>> I'd like to get an updated version of lilypond out over this weekend.
>>> I'd be happy to discuss how to update Gub and then rebuild it starting
>>> next week.
>>
>> Trickier than expected, just changing lily/parser.yy was not enough.
>>
>> <URL:http://code.google.com/p/lilypond/issues/detail?id=2855>
>>
>> -- 
>> David Kastrup
>
>
> Patchy has OK'd this, so I'd suggest pushing to staging or master
> direct, so I can see what GUB makes of it in the morning.  If you push
> to staging, I'll run patchy-staging if no-one else does to forward it
> to master.

Pushed to staging as
commit d15e5e49e148b253703cdcfad9b66a7fb29d404f
Author: David Kastrup <address@hidden>
Date:   Sat Sep 22 19:36:25 2012 +0200

    parser.yy: get along without %code Bison directive to reduce dependencies



-- 
David Kastrup