Re: lilypond build on m68k
On Fri, Mar 18, 2005 at 06:24:16PM -0800, Thomas Bushnell BSG wrote:
> "Matthias Urlichs" <firstname.lastname@example.org> 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.
such messages may point struct alignment issues - m68k does not
pad shorts to 32 bits so structs get easilly misaligned or unexpected
size. Usually no pronlem unless the software does strange things
like garbage collection etc