lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

New Binary for LilyPond on MacOSX 10.7 available


From: James Lowe
Subject: New Binary for LilyPond on MacOSX 10.7 available
Date: Mon, 8 Aug 2011 15:52:08 +0000

Hans, Floris et al

We have built a new binary for use on 10.7 that we wondered if you can try.

http://lilypond.org/~graham/

You can get them from the this link.

Could you let the User and/or Dev list know if it does or doesn't resolve your 
issue?

Thanks

James



)-----Original Message-----
)From: address@hidden
)[mailto:address@hidden On
)Behalf Of Hans Aberg
)Sent: 10 July 2011 09:59
)To: Floris van Manen
)Cc: address@hidden bug
)Subject: Re: midi2ly fails on OSX 10.6.8
)
)Please cc the list, so that others can engage in the issue.
)
)Hans
)
)
)On 10 Jul 2011, at 10:55, Floris van Manen wrote:
)
)>
)> On Jul 10, 2011, at 00:20, Hans Aberg wrote:
)>
)>> 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 use the macport python 2.7 version.
)> Apparently the Lilypond dmg distribution package gets confused as
)what interpreter to use...
)> I believe the distribution package should not address outside its own
)area ...
)>
)> .F
)>
)
)
)_______________________________________________
)bug-lilypond mailing list
)address@hidden
)https://lists.gnu.org/mailman/listinfo/bug-lilypond



reply via email to

[Prev in Thread] Current Thread [Next in Thread]