Re: lilypond build on m68k

2005-03-27 Thread Richard Zidlicky
On Fri, Mar 18, 2005 at 06:24:16PM -0800, Thomas Bushnell BSG wrote: > "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 l

Re: lilypond build on m68k

2005-03-18 Thread Thomas Bushnell BSG
"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

Re: lilypond build on m68k

2005-03-17 Thread Matthias Urlichs
Hi, 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. -- Matthias Urlichs | {M:U}

Re: lilypond build on m68k

2005-03-17 Thread Thomas Bushnell BSG
Matthias Urlichs <[EMAIL PROTECTED]> writes: > lilypond, building on m68k, logs heaps of lines like the next two: > > Attempt to free something of size 46 > Attempt to allocate something of size 46 > > The size is always 46, and this seems to happen on m68k only. > > Any idea where that comes f

lilypond build on m68k

2005-03-17 Thread Matthias Urlichs
Hi, lilypond, building on m68k, logs heaps of lines like the next two: Attempt to free something of size 46 Attempt to allocate something of size 46 The size is always 46, and this seems to happen on m68k only. Any idea where that comes from? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] wit