Am 31.07.2011 um 16:50 schrieb Floris van Manen:
>
> On Jul 31, 2011, at 15:38, Christian Hitz wrote:
>
>>
>> Am 31.07.2011 um 14:31 schrieb Floris van Manen:
>>>> Attachments:
>>>> LilyPond-lilypad.zip 4.6 MB
>>>> 0001-fix-app-creation-on-Mac-OS-X-10.7.patch 2.1 KB
>>> These were not attached on arrival.
>>
>> The are attached to the bug report:
>> http://code.google.com/p/lilypond/issues/detail?id=1781
>
>
>
> -
> '/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/shutil.py',
> +
> '/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/shutil.py',
>
> Maybe you could point to the internal python version in the Lilypond package
> rather then the system version.
Actually, that is what this line is for. It instructs py2app to copy shutil.py
from the given location into the LilyPond.app package.
> That might also solve the problem of conflicting libraries when trying to
> launch midi2ly .
You mean the following error?
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
I don't think there is a connection. This particular seems to indicate a 32bit
to 64bit mismatch between Python and the midi library.
Regards,
Christian
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
