lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lilypond 2.19.20 fails to compile


From: Urs Liska
Subject: Re: lilypond 2.19.20 fails to compile
Date: Tue, 28 Apr 2015 21:14:39 +0200
User-agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.6.0

Could you please post the end of the output of running with --verbose?

This *reminds* me of a problem I recently had that was/is related to a change in Ghostscript handling.

Am 28.04.2015 um 21:03 schrieb N. Andrew Walsh:
Hi All,

I'm not sure if this is the place to post about recent versions and possible bugs. I get the following error when trying to compile a MWE:

Starting lilypond 2.19.20 [Untitled]...

Processing `/tmp/frescobaldi-NJlynW/tmpIzKobr/document.ly'

Parsing...

Interpreting music...

Preprocessing graphical objects...

Finding the ideal number of pages...

Fitting music on 1 page...

Drawing systems...

Layout output to `document.ps'...

Converting to `./document.pdf'...

warning: `(gs -q -dSAFER -dDEVICEWIDTHPOINTS=595.28 -dDEVICEHEIGHTPOINTS=841.89 -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite -sOutputFile=./document.pdf -c.setpdfwrite -fdocument.ps)' failed (256)


programming error: Parsed object should be dead: #<Grob NoteSpacing >

continuing, cross fingers

programming error: Parsed object should be dead: #<Prob: paper-system C++: Prob((Y-offset . 1.0) (system-grob . #<Grob System >) (staff-refpoint-extent -3.776 . -3.776) (last-in-score . #t) (page-turn-penalty) (page-break-penalty) (page-turn-permission . allow) (page-break-permission . allow) (vertical-skylines . #<Skyline_pair>) (stencil . #<Stencil>))() >


continuing, cross fingers

fatal error: failed files: "/tmp/frescobaldi-NJlynW/tmpIzKobr/document.ly"

Exited with return code 1.


MWE was:

\version "2.19.20"


\relative c' {

a4 b c d

}


I get the same errors on more complex files, so I'm guessing it's something deeper than the level of file syntax. 


But then, this is the dev version of lilypond, so stuff like this is probably expected?


Should this be sent to lilypond-dev?


Cheers,


A



_______________________________________________
lilypond-user mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/lilypond-user


reply via email to

[Prev in Thread] Current Thread [Next in Thread]