lilypond-auto
[Top][All Lists]
Advanced

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

[Lilypond-auto] Issue 3030 in lilypond: midi2ly failure


From: lilypond
Subject: [Lilypond-auto] Issue 3030 in lilypond: midi2ly failure
Date: Sun, 16 Dec 2012 10:17:54 +0000

Status: Accepted
Owner: ----
Labels: Type-Scripts OpSys-OSX

New issue 3030 by address@hidden: midi2ly failure
http://code.google.com/p/lilypond/issues/detail?id=3030

Mike Solomon reported here:

http://lists.gnu.org/archive/html/bug-lilypond/2012-12/msg00067.html

a problem with midi2ly from Lilypond 2.17.8 on MacOSX as follows:

Hey all,

A colleague of mine got the following error message while running midi2ly on
his MacBook :

macbook:~ vanhovef$ /Applications/LilyPond.app/Contents/Resources/bin/midi2ly
wil
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

The LilyPond binary works just fine, so maybe it is an issue w/ the GUB
cross-compilation for python?  I only have 2.14.2 on my computer in terms of
pre-compiled binaries & midi2ly works ok out of the box there - if someone is
working with the precompiled devel version for mac and could test this I'd
appreciate it.  Otherwise I can download and test.

Cheers,
MS









reply via email to

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