Anthony Fok wrote:
this bug (either in bison-1.875 or in certain versions of g++ like 2.95.3
or g++-3.2) has been reportedly dealt with in bison-1.875a, released a
day or two ago:
ftp://alpha.gnu.org/gnu/bison/bison-1.875a.tar.gz
That's excellent, thank you very much. I built a copy of bison 1.875a
and that appears to have fixed the problem with the parser.
That allowed me to fix a few 'syntax' errors in lilypond-book.py,
the 'import lilypond as ly' one I reported earlier and use of the
' += ' operator - maybe this is a consequence of me having python 1.5
rather than python 2?
I had some further errors in Documentation/users and Documentation/toputil,
details are not on this machine but are probably due to me not having
makeinfo installed properly. I'll try and track these down when I
have time, but removing those directories from the build allowed me to
compile a working version albeit with no documentation.
Thanks to everyone who helped.
Regards
Pete
--
____________________________________________________________________
Pete Young [EMAIL PROTECTED] Phone +44 1473 642740
"Just another crouton, floating on the bouillabaisse of life"
_______________________________________________
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
