"Matthias Urlichs" <[EMAIL PROTECTED]> writes: > Thomas Bushnell BSG: > > > The size is always 46, and this seems to happen on m68k only. > > > Any idea where that comes from? > > > > Not a clue, but with a build log I might be able to figure it out. > > > Look at the latest successful log, it's been there last time.
Not sure what that is; it looks like it's getting printed by fontforge, which is outline tracing the bitmap fonts produced by metafont. Tracing is a CPU and memory intensive process. It wouldn't surprise me if these are malloc failures or some other problem in fontforge. So my suggestion is to ask the fontforge maintainer why it might be printing that. The newer versions of lilypond have a better build system; instead of building the fonts this way on every build (which is indeed icky), the fonts are split off into a separate package. Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
