Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: > Thomas Bushnell BSG wrote: >> Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: >> >>> Hrmmph. Is this still an mftrace problem (does mftrace cmr10 >>> produce a .pfa which looks good in fontforge?) >> Alas, no. I get no glyphs, and the output of mftrace is as follows. >> BTW, there is presumably a missing "\n" on one of these printfs. >> > > The problem is the gf2pbm program included in mftrace. Can you compile > gf2pbm.c from mftrace for yourself (using WORDS_BIGENDIAN in config.h > for ppc), and check whether that works. Usage: > > mf-nowin cmr10 > gf2pbm -n 65 cmr10.2602gf > > produces 65.pbm containing the glyph A.
Ah, I have found the problem. The Debian package builds gf2pbm with optimization on (-O2). gf2pbm misbehaves when compiled with optimization, and works fine when compiled without. This is almost certainly not a compiler bug, of course, it's much more likely a problem inside gf2pbm. Thomas _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
