On Nov 8, 2004, at 12:39 AM, Matthias Neeracher wrote:
On Nov 7, 2004, at 11:13 AM, Daniel Johnson wrote:
OK, fontforge-20040930-1 seems to be the last version that can build lilypond. More recent versions have changes in the way it deals with TeX font encodings and this looks to be where the problem is. I'm afraid there's nothing I can do; it'll have to be fixed upstream. As a workaround, installing version 20040930 should work. I've included the necessary .info file. Put it in your /sw/fink/dists/local/main/finkinfo/graphics folder (you may need to create it first) and do "fink install fontforge-20040930-1" to replace the newer version.
A preferable solution might be to go directly to lilypond-2.4.1 instead, which builds with fontforge-20041023-2 just fine (and should be in stable in a few days, based on positive feedback I've received from users).
Matthias
I've just updated fontforge stable and unstable with a patch for this bug from the upstream developer. Any version of lilypond should now be able to use any version of fontforge.
-- Daniel Johnson [EMAIL PROTECTED] PGP public key: http://homepage.mac.com/danielj7/publickey.txt
PGP.sig
Description: This is a digitally signed message part
