ghostscript-8.70-6 broke my lilypond, no more PDF
I am using lilypond 2.12.3 under CentOS 5.6. Recently, I ran the CentOS recommended updates and I updated from ghostscript-8.15.2-9.12 to ghostscript-8.70-6. Since that time, lilypond no longer works for me in that lilypond .ps files but no longer produces .pdf files. Here is what the output at the command line look like: GNU LilyPond 2.12.3 Processing `song02.ly' Parsing... Interpreting music... [8][16][24][32] Preprocessing graphical objects... Finding the ideal number of pages... Fitting music on 1 page... Drawing systems... Layout output to `song02.ps'... Converting to `./song02.pdf'... `gs -q -dSAFER -dDEVICEWIDTHPOINTS=612.00 -dDEVICEHEIGHTPOINTS=792.00 -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite -sOutputFile="./song02.pdf" -c .setpdfwrite -f "song02.ps"' failed (256) error: failed files: "song02.ly" Have I stumbled onto a bug? How can I get lilypond to produce PDF files again. Evidentally, it is not so easy to roll back updates under CentOS. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: ghostscript-8.70-6 broke my lilypond, no more PDF
Hi, On Mon, Apr 25, 2011 at 03:59:17PM -0500, ivan.k.kuznet...@gmail.com wrote: > I ran the CentOS recommended updates and I updated from > ghostscript-8.15.2-9.12 to ghostscript-8.70-6. > > Since that time, lilypond no longer works for me in that > lilypond .ps files but no longer produces .pdf files. > Here is what the output at the command line look like: > > >GNU LilyPond 2.12.3 >Processing `song02.ly' >Parsing... >Interpreting music... [8][16][24][32] >Preprocessing graphical objects... >Finding the ideal number of pages... >Fitting music on 1 page... >Drawing systems... >Layout output to `song02.ps'... >Converting to `./song02.pdf'... >`gs -q -dSAFER -dDEVICEWIDTHPOINTS=612.00 -dDEVICEHEIGHTPOINTS=792.00 >-dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite >-sOutputFile="./song02.pdf" -c .setpdfwrite -f "song02.ps"' failed (256) >error: failed files: "song02.ly" > > Have I stumbled onto a bug? How can I get lilypond to > produce PDF files again. That run should have left over the file `song02.ps'. Could you try to run ghostscript manually to convert it to pdf (but omit the `-q' flag)? Like, just run gs -dSAFER -dDEVICEWIDTHPOINTS=612.00 -dDEVICEHEIGHTPOINTS=792.00 \ -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 \ -sDEVICE=pdfwrite -sOutputFile="./song02.pdf" -c .setpdfwrite \ -f "song02.ps" from your shell. This may give a hint about what's wrong. FWIW, on OpenBSD, where I'm the maintainer of both lilypond and ghostscript (no coincidence, btw), lilypond-2.12.3 works well with ghostscript-8.63, and it also worked with ghostscript-8.69, -8.70 and -9.00 (which I all tested during the long way to update ghostscript). Ciao, Kili ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: ghostscript-8.70-6 broke my lilypond, no more PDF
Matthias Kilian wrote: > > Could you try > to run ghostscript manually to convert it to pdf (but omit the `-q' > flag)? Like, just run > > gs -dSAFER -dDEVICEWIDTHPOINTS=612.00 -dDEVICEHEIGHTPOINTS=792.00 \ >-dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 \ >-sDEVICE=pdfwrite -sOutputFile="./song02.pdf" -c .setpdfwrite \ >-f "song02.ps" > > from your shell. I just ran the above and song02.pdf was created with no errors. So only difference between the above command and what lilypond executes is the "-q" flag I see. Why does the -q flag now fail? ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: ghostscript-8.70-6 broke my lilypond, no more PDF
On Mon, Apr 25, 2011 at 05:54:24PM -0500, Ivan Kuznetsov wrote: > > Could you try > > to run ghostscript manually to convert it to pdf (but omit the `-q' > > flag)? Like, just run > > > > gs -dSAFER -dDEVICEWIDTHPOINTS=612.00 -dDEVICEHEIGHTPOINTS=792.00 \ > >-dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 \ > >-sDEVICE=pdfwrite -sOutputFile="./song02.pdf" -c .setpdfwrite \ > >-f "song02.ps" > > > > from your shell. > > I just ran the above and song02.pdf was created with no errors. > So only difference between the above command and what lilypond > executes is the "-q" flag I see. Why does the -q flag now fail? I don't think it's the `-q' that causes the failure, because this flag only makes ghostscript quiet (no startup message, no progress information written to stdout). My best guess is that the newer ghostscript (when run from within lilypond) hits some resource limit like open file descriptors or memory. But in this case it *should* have printed *some* error message to stderr, and I've no idea why it didn't in the output you pastet in your original mail. Assuming that you're running a shell like ksh or bash, you can display the current limits for file descriptors with ulimit -n and the data size limit with ulimit -d If those are rather small, try to increase them. For example 512 file descriptors and 1GB data size: ulimit -Sn 512 ulimit -Sd 1048576 But please note that this is just a wild guess. It may help or not. Ciao, Kili ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: ghostscript-8.70-6 broke my lilypond, no more PDF
Matthias Kilian wrote: > > I don't think it's the `-q' that causes the failure, because this > flag only makes ghostscript quiet And it is not the -q flag as I just ran the command with it. It is as you say suggest, lilypond is bombing when trying to run the ghostscript command. But why? > My best guess is that the newer ghostscript (when run from within > lilypond) hits some resource limit like open file descriptors or > memory. [...] Does not seem likely. > Assuming that you're running a shell like ksh or bash, you can display > the current limits for file descriptors with [...] Actually, I normally run things under a tcsh shell, but it is easy enough to start a bash shell. The results: ulimit -n 1024 ulimit -d unlimited I think I might just uninstall lilypond and do a fresh install. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
