Re: compile failure - parsed object should be dead in 2.19.20
Addendum: this is not a bug with ghostscript, at least for me, but rather with a part of ghostscript failing against recent versions of fontconfig (on my gentoo system, fontconfig-2.11.93 fails to compile .ly files with the errors above, but downgrading to 2.11.1 allows files to compile). Can anybody else confirm? Cheers, A On Tue, Apr 28, 2015 at 10:11 PM, N. Andrew Walsh n.andrew.wa...@gmail.com wrote: according to Urs Liska, this resembles an error he encountered with ghostscript, as the output on my machine when using --verbose confirms. If you're also on the user list, the longer output is there. If not, I can post here (but I imagine you'd prefer avoiding double-posting if it isn't necessary). I'm using gs 9.15. Cheers, A On Tue, Apr 28, 2015 at 9:52 PM, Thomas Morley thomasmorle...@gmail.com wrote: 2015-04-28 21:15 GMT+02:00 N. Andrew Walsh n.andrew.wa...@gmail.com: I'm not top posting. With a MWE: \version 2.19.20 \relative c' { a4 b c d } I get the following error in the console output under frescobaldi: 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. - Error output is the same on larger files. Cheers Can't confirm with a build from latest master in LilyDev (Ubuntu 10.04) All works as expected. Cheers, Harm ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: compile failure - parsed object should be dead in 2.19.20
according to Urs Liska, this resembles an error he encountered with ghostscript, as the output on my machine when using --verbose confirms. If you're also on the user list, the longer output is there. If not, I can post here (but I imagine you'd prefer avoiding double-posting if it isn't necessary). I'm using gs 9.15. Cheers, A On Tue, Apr 28, 2015 at 9:52 PM, Thomas Morley thomasmorle...@gmail.com wrote: 2015-04-28 21:15 GMT+02:00 N. Andrew Walsh n.andrew.wa...@gmail.com: I'm not top posting. With a MWE: \version 2.19.20 \relative c' { a4 b c d } I get the following error in the console output under frescobaldi: 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. - Error output is the same on larger files. Cheers Can't confirm with a build from latest master in LilyDev (Ubuntu 10.04) All works as expected. Cheers, Harm ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: compile failure - parsed object should be dead in 2.19.20
Am 28.04.2015 um 21:52 schrieb Thomas Morley: Can't confirm with a build from latest master in LilyDev (Ubuntu 10.04) All works as expected. Cheers, Harm That's consistent with my experience from 2.19.18 on. It works with self-compiled versions (on Debian stable) but not with binary releases. It is related to calling a system vs. a packaged Ghostscript. At least it doesn't seem to be an issue with my personal configuration ... Urs -- Urs Liska www.openlilylib.org ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
compile failure - parsed object should be dead in 2.19.20
I'm not top posting. With a MWE: \version 2.19.20 \relative c' { a4 b c d } I get the following error in the console output under frescobaldi: 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. - Error output is the same on larger files. Cheers ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: compile failure - parsed object should be dead in 2.19.20
2015-04-28 21:15 GMT+02:00 N. Andrew Walsh n.andrew.wa...@gmail.com: I'm not top posting. With a MWE: \version 2.19.20 \relative c' { a4 b c d } I get the following error in the console output under frescobaldi: 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. - Error output is the same on larger files. Cheers Can't confirm with a build from latest master in LilyDev (Ubuntu 10.04) All works as expected. Cheers, Harm ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond