Well, since we're all here, I might as well join in as well. I was getting the same ghostscript error, and I fixed it by doing the following:
Editing the /usr/share/ghostscript/9.20/Resource/Init/Fontmap file to comment out the line about local fontmaps results in successful compilation and display. change the ghostscript directory for the version you have installed. I have to do this every time I update ghostscript, or I get error 256 on pdf generation. Hope this helps, A On Tue, Jan 23, 2018 at 10:17 AM, Urs Liska <[email protected]> wrote: > Hi Andrew(s) > > Am 22.01.2018 um 23:07 schrieb Andrew Smith: > > I'm getting a failure all-around on a new Arch VM I'm running in my > windows machine. I'm using lyp here to make a/b version testing easier. > Basically, the gs command is failing when liilypond runs it but it works > just fine when I copy/paste it and run it manually. > > 2.19.17 works, but 2.19.18 fails. Shell info + file is below. > GhostScript system version is 9.22. > > https://gist.github.com/andrewcsmith/eb17a859e62921f3ad50a4c5298628e9 > > This is urgent for me, as I don't have access to the old machine where > this worked, and I have some libraries that use the recent font changes -- > thanks a lot. > > > No guarantee it works for you, but I have a strong suspicion. > When installing LilyPond the normal way from the downloaded archive it > creates a wrapper command "lilypond" (usually as ~/bin/lilypond). > This doesn't only call the lilypond executable but also adds > export LD_LIBRARY_PATH=/path/to/lilypond/usr/lib:$LD_LIBRARY_PATH > > to make sure the libraries shipped with LilyPond are used and avoid such > version mismatches with system libraries. > I'm not sure how lyp invokes LilyPond but you should look into this (and > maybe call LilyPond directly/through a custom wrapper script). > > We had to learn that with Frescobaldi too. Frescobaldi can manage > arbitrary LilyPond installations, and by now it injects that library path > (for the chosen LilyPond) in the invocation command. > > HTH > Urs > > > ``` > [vagrant@bazinga ly_test]$ lyp use 2.19.18 > Using Lilypond version 2.19.18 > [vagrant@bazinga ly_test]$ lyp compile test.ly > Lyp 1.3.5 > GNU LilyPond 2.19.18 > Processing `/tmp/lyp/wrappers/test.ly' > Parsing... > Interpreting music... > Preprocessing graphical objects... > Finding the ideal number of pages... > Fitting music on 1 page... > Drawing systems... > Layout output to `test.ps'... > Converting to `./test.pdf'... > warning: `(gs -q -dSAFER -dDEVICEWIDTHPOINTS=595.28 > -dDEVICEHEIGHTPOINTS=841.89 > -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite > -sOutputFile=./test.pdf -c.setpdfwrite -ftest.ps)' failed (256) > > fatal error: failed files: "/tmp/lyp/wrappers/test.ly" > > [vagrant@bazinga ly_test]$ lyp use 2.19.17 > Using Lilypond version 2.19.17 > [vagrant@bazinga ly_test]$ lyp compile test.ly > Lyp 1.3.5 > GNU LilyPond 2.19.17 > Processing `/tmp/lyp/wrappers/test.ly' > Parsing... > Interpreting music... > Preprocessing graphical objects... > Finding the ideal number of pages... > Fitting music on 1 page... > Drawing systems... > Layout output to `test.ps'... > Converting to `./test.pdf'... > Success: compilation successfully completed > ``` > > File: > > \score { > \new Voice { > c'4 d' e' f' > } > > \layout { } > } > > > > > > _______________________________________________ > lilypond-user mailing > [email protected]https://lists.gnu.org/mailman/listinfo/lilypond-user > > > > _______________________________________________ > lilypond-user mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/lilypond-user > >
_______________________________________________ lilypond-user mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-user
