Re: midi2ly

[Hans Aberg]

[Please keep the cc to the bug-lilypond list, so that others may help.]

On 18 Mar 2011, at 02:58, Isambard Khroustaliov wrote:

> Thanks for this, running otool I get:
> 
> Zeit-2:~ zeit$ otool -arch i386 -L 
> /Applications/LilyPond.app/Contents/Resources/lib/lilypond/current/python/midi.so
> /Applications/LilyPond.app/Contents/Resources/lib/lilypond/current/python/midi.so:
>       /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current 
> version 7.10.0)
>       /usr/cross/i686-apple-darwin8/lib/libgcc_s.1.dylib (compatibility 
> version 1.0.0, current version 1.0.0)
>       /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current 
> version 88.1.2)
> 
> and nothing when I use the -arch x86_64 flag ...
> 
> I'm guessing then, that it needs to be re-compiled for x86_64, however, i'm 
> afraid I've no idea how to go about doing that ... 

When I rnn
  otool -arch i386 -L /Applications/LilyPond.app/Contents/Resources/bin/lilypond
  otool -arch x86_64 -L 
/Applications/LilyPond.app/Contents/Resources/bin/lilypond
the binary only calls 32-bit libraries.

So it seems that when you compile whatever is calling midi.so with GCC, you 
should add the -arch i386 flag.

Hans