Dear Sirs,
I found that
/Applications/LilyPond.app/Contents/Resources/lib/lilypond/current/python/midi.so
has wrong information regarding the dynamic shared libraries it uses.
Juns-MacBook-Air:~ tamura$ cd
/Applications/LilyPond.app/Contents/Resources/lib/lilypond/current/python
Juns-MacBook-Air:python tamura$ otool -L midi.so
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)
I had to correct this by using the install_name_tool command in order to get
midi2ly working (besides the issue #2208.)
Juns-MacBook-Air:python tamura$ install_name_tool -change
/usr/cross/i686-apple-darwin8/lib/libgcc_s.1.dylib /usr/lib/libgcc_s.1.dylib
midi.so
Juns-MacBook-Air:python tamura$ otool -L midi.so
midi.so:
/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current
version 7.10.0)
/usr/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)
Best regards,
Jun
_______________________________________________
bug-lilypond mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-lilypond
