Re: compile failure - parsed object should be dead in 2.19.20

2015-05-01 Thread N. Andrew Walsh
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

Re: compile failure - parsed object should be dead in 2.19.20

2015-04-28 Thread N. Andrew Walsh
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

Re: compile failure - parsed object should be dead in 2.19.20

2015-04-28 Thread Urs Liska
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

compile failure - parsed object should be dead in 2.19.20

2015-04-28 Thread N . Andrew Walsh
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

Re: compile failure - parsed object should be dead in 2.19.20

2015-04-28 Thread Thomas Morley
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