lilypond-user
[Top][All Lists]
Advanced

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

Re: ghostscript fails on pdf generation


From: Jean Brefort
Subject: Re: ghostscript fails on pdf generation
Date: Sat, 11 Feb 2017 21:08:32 +0100

Le samedi 11 février 2017 à 20:55 +0100, N. Andrew Walsh a écrit :
> PS- ghostscript on my system (gentoo Linux) recently updated: on Jan
> 31st to 9.20-r1. Can anybody else check and see if they encounter the
> same issue with that version of ghostscript? Trawling back through
> old github issues and forum archives shows a number of times over the
> years where a ghostscript update changed some part of the code and
> Lily wasn't yet adapted. For the record, I'm running Lilypond-
> 2.19.54-1, 64-bit.
> 
> On Sat, Feb 11, 2017 at 8:36 PM, N. Andrew Walsh <address@hidden
> l.com> wrote:
> > Hi List,
> > 
> > I realize this isn't strictly an issue with Lily, but pdf output
> > recently started failing. I see the following message in the
> > console output:
> > 
> > Layout output to `/tmp/lilypond-CFV9h3'...
> > Converting to `Reinhold Urmetzer - Lamento di Achille.pdf'...
> > warning: `(gs -q -dSAFER -dDEVICEWIDTHPOINTS=595.28
> > -dDEVICEHEIGHTPOINTS=841.89 -dCompatibilityLevel=1.4 -dNOPAUSE
> > -dBATCH -r1200 -sDEVICE=pdfwrite -sOutputFile=Reinhold Urmetzer -
> > Lamento di Achille.pdf -c.setpdfwrite -f/tmp/lilypond-CFV9h3)'
> > failed (256)
> > 
> > 'gs' is the ghostscript binary, but I haven't updated that
> > recently, nor any of its dependencies (the closest I could find in
> > recent updates was "podofo", which seems only marginally related to
> > pdf generation). 
> > 
> > Is there a way to check what the exact error might be here? I
> > suspect a recent package update somewhere changed a shared library
> > and I'll need to recompile something, but I'm not sure what. Any
> > suggestions?
> > 
> > Cheers,
> > 
> > A
> > 
Hi,

I get that for large score because of not enough RAM.

Regards,
Jean



reply via email to

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