Re: midi2ly error

[Quentin Spencer]

Jan Nieuwenhuizen wrote:
> Johan Vromans <address@hidden> writes:
>
>   
> > It's also in Fedora Core 5.
> >     
>
>   
> > Klaas, if you need a wordk-around just email me.
> >     
>
> Workaround?  Why isn't this fixed in Fedora?
>
> [Where is LilyPond's bug page with Fedora, I cannot find the word Bug
> on http://fedora.redhat.com or any of its subpages I tried and,
> http://bugs.fedora.redhat.com does not exist either?]
>
>   

This problem only exists in the 2.8.x packages included in FC5. In FC6, 
the 2.10.x packages don't have this problem. A bug has already been 
filed (https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=219254). I 
figured I would fix it by upgrading to 2.10.2, but the build on PPC 
failed with the following (after I had already closed the bug):

adding font directory: 
/builddir/build/BUILD/lilypond-2.10.2/out/bin/../share/lilypond/2.10.2/fonts/type1/Building 
font database.

*** buffer overflow detected ***: 
/builddir/build/BUILD/lilypond-2.10.2/out/bin/lilypond terminated

Any ideas?
I noticed that on this page: 
http://lilypond.org/doc/v2.10/Documentation/topdocs/INSTALL.html, it 
says that guile 1.8.0 is required to run, but 1.6.7 is required to build 
2.10 (the configure script says it's 1.6.7, but in versions >=2.10.1, it 
fails the check on FC5 because it detects the version as 1.6). Is it 
correct? Is it possible that having an old version of guile could be 
causing the crash?

If I need to go back to 2.8.x, are the changes listed in the bug report 
adequate?

Quentin