On 9 Jul 2011, at 22:19, Floris van Manen wrote: > L.S. > While trying to launch the midi2ly app, it will fail to start: > > $/Applications/LilyPond.app/Contents/Resources/bin/midi2ly > Traceback (most recent call last): > File "/Applications/LilyPond.app/Contents/Resources/bin/midi2ly", > line 54, in <module> > import midi > ImportError: > dlopen( > /Applications/LilyPond.app/ > Contents/Resources/lib/lilypond/current/python/midi.so, 2): > no suitable image found. > Did find: > /Applications/LilyPond.app/ > Contents/Resources/lib/lilypond/current/python/midi.so: > mach-o, but wrong architecture
It seems that the 'import midi' line in the midi2ly script tries to open an x86_64 binary, though all else is i386. One may try fix it using 'arch -i386' somewhere. The architecture cane be checked using 'file', and what it is calling using 'otool'. > (I had to break up the lines, as this mailing app will not allow > lines longer then 80 chars. why?) I think the original mail protocol has such a limit, so mail programs break it up, and paste it together so as to make it appear that longer lines are possible. Hans _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
