[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: midi2ly
From: |
Hans Aberg |
Subject: |
Re: midi2ly |
Date: |
Thu, 17 Mar 2011 20:51:01 +0100 |
On 17 Mar 2011, at 17:39, Sam Britton wrote:
> I've been trying for a while now to get midi2ly to work to no avail.
> I get the error below. Is there anyway to fix this?
...
> /Applications
> /LilyPond.app
> /Contents
> /Resources
> /lib
> /lilypond
> /current
> /python
> /midi.so
>
> : mach-o, but wrong architecture
>
> _______
>
> Lilypond Version: 2.12.3-1
>
> System Version: Mac OS X 10.6.6 (10J3210)
> Kernel Version: Darwin 10.7.1
>
> Model Name: MacBook Pro
> Model Identifier: MacBookPro8,2
> Processor Name: Intel Core i7
> Processor Speed: 2.2 GHz
Try:
$ otool -arch x86_64 -L
/Applications/LilyPond.app/Contents/Resources/lib/lilypond/current/python/midi.so
$ otool -arch i386 -L
/Applications/LilyPond.app/Contents/Resources/lib/lilypond/current/python/midi.so
I got that the library is compiled for 32-bit. Possibly, you are compiling you
own code for x86_64, the default on Mac OS 10.6. You then have to add the -arch
i386 flag, and also -arch x86_64 if you want a fat binary.
Also, the current libtool, which Guile calls, cannot open dynamic libraries
ending in .dylib. But that is to e fixed. This is not a problem if you stick to
.so.
http://lists.gnu.org/archive/html/bug-guile/2011-03/msg00030.html
Hans
- midi2ly, Sam Britton, 2011/03/17
- Re: midi2ly,
Hans Aberg <=