Il giorno mar, 07/08/2012 alle 22.40 +0000, Colin Hall ha scritto:
> Thanks for letting us know about this David.
> One of the developers may be able to make some suggestions.
> I'm not going to create an issue tracker for this. I'm very
> sorry but we only accept bug reports for official builds
> on a limited set of well-known platforms.
To second this, the developers team is making effort towards releasing
next stable branch (2.16) within a reasonable time frame; if you can
reproduce the error with running latest unstable release (2.15.43) on
the convert-lyed file and still get a crash, there *might* be a
qualified developer to help you on a self-compiled lilypond, but you
must provide enough details (a trace, compilation flags (relevant
environment variables, configure and make arguments), versions of
relevant dependencies, in this case Guile/GCC...).
I recall that there have been issues with building and/or running
LilyPond using recent GCC compilers, that have been fixed in the
development branch 2.15, so building and using latest 2.15 might help
with your issue. Currently I'm not qualified enough in Scheme/c++
debugging to help decently with this, so if using 2.15 development
version is not an option for you, our fallback suggestion is using the
precompiled binaries from lilypond.org.