On Tue, Aug 26, 2014 at 03:55:51PM +0200, Janek Warchoł wrote: > 2014-08-25 0:40 GMT+02:00 Frank Steinmetzger <war...@gmx.de>: > > On Sun, Aug 24, 2014 at 10:51:53PM +0200, Malte Meyn wrote: > >> That is a known problem. If I remember correctly this only occurs with > >> some old versions of LilyPond when using a certain version of > >> ghostscript, but I don’t remember the exact details ... > >> > >> What versions of LilyPond (lilypond --version) and ghostscript > >> (ghostscript --version) do you use? > > > > Thanks for the reply. > > Lilypond 2.16.2 and ghostscript 9.10. But it has been so since I installed > > this system in March, there were no upgrades ever since. Some other package > > must be the culprit. > > The problem was actually caused by metafont or metapost, not > ghostscript.
I rebuild the direct dependencies for lilypond and also for ghostscript (including texlive-metapost), but that didn’t help. However, I encountered a problem actually building lilypond 2.16.2 -- it fails with freetype-error.cc:34:31: warning: freetype/fterrors.h: No such file or directory The file it was looking for is actually at /usr/include/freetype2/fterrors.h. I checked a few other freetype-dependent packages and also another distro (Arch), in case it was a problem of my own (Gentoo). All use include/freetype2. It’s EOL now, but could this be a bug in the lilypond code? > I think that upgrading to the latest stable LilyPond > release may help you (and anyway 2.16 is quite old). I am aware of that, but apparently the package maintainer is not (the 2.18 package has been available for a while now, but not marked yet as “stable” and I don’t want to customise my package manager setup too much). > See http://lists.gnu.org/archive/html/lilypond-devel/2013-10/msg00204.html > for more details. Interesting. What puzzled me at first was that both my machines had the same versions of stuff installed, but still had different output. So I dug a bit deeper and found out that the last time I actually built lilypond on the working one it still had texlive 2012. There is a separate metapost package available which provides version 1.803. I installed that, set the system to use it and rebuilt lilypond. Now the output is fine again. I’ll remember that for later. Cheers. -- Gruß | Greetings | Qapla’ Please do not share anything from, with or about me with any Facebook service. The flesh was willing, but the grass was wet.
signature.asc
Description: Digital signature
_______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
