Have you tried just rerunning the lilypond-book command
again after the crash. At least this used to work as a workaround
a couple of years back, since lilypond-book only processed the
files it hadn't already processed in the first run.
/Mats
Valentin Villenave wrote:
2008/7/2 Nikita <[EMAIL PROTECTED]>:
The problem is that lilypond-book script tries to dissect any file in one pass
and runs out of memory if the file is very large. The solution that worked for
me was to split the file and process it by parts. That could probably be coded
within lilypond-book itself. The latest version I tried 2.11.49 suffered from
the same problem.
Thanks, added to our bug tracker as
http://code.google.com/p/lilypond/issues/detail?id=644
Cheers,
Valentin
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
--
=============================================
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=============================================
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
