lilypond-user
[Top][All Lists]
Advanced

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

Re: OS X 10.5 SDK


From: Maurits Lamers
Subject: Re: OS X 10.5 SDK
Date: Tue, 18 Dec 2007 13:12:01 +0100


Op 18 dec 2007, om 12:17 heeft Hans Aberg het volgende geschreven:

On 18 Dec 2007, at 01:10, Maurits Lamers wrote:

It turns out Lilypond is not working as it should. Running Lilypond with correct paths errors with the following message:

/opt/local/share/guile/1.8/srfi/srfi-1.scm:223:1: In procedure dynamic-link in expression (load-extension "libguile-srfi-srfi-1- v-3" "scm_init_srfi_1"): /opt/local/share/guile/1.8/srfi/srfi-1.scm:223:1: file: "libguile- srfi-srfi-1-v-3", message: "dlopen(libguile-srfi-srfi-1-v-3.so, 9): image not found"

After inspecting the library directory, the reason for the error is all to clear: there is no file libguile-srfi-srfi-1-v-3.so There are other library types (.a, .la, .dylib), but no .so and using a symbolic link to the .a or .dylib won't change the error message.

Any idea to solve this?

The .so ending is used for a dynamic library format used on the GNU/ Linux OS. Mac OS X uses the Mach-O format with ending .dylib. However, I think the functions calling these are named the same.

So I think that if the dynamic library you are calling is compiled for Mac OS X, just changing the ending when looking for it from ".so" to ".dylib" might do the trick. The Mach-O format do not support some things that can be used with the".so" format, so when compiling a dynamic library with GCC, one may have to change some option there. Don't know what it was, but if you get an error, it might be --dynamic or something. Check at the site <http://developer.apple.com/ >.

As mentioned in a previous message, I tried to compile things with --- static, but that didn't do anything. Providing a symbolic link to the dylib that is called doesn't do the trick, the error message stays the same.

Immanuel Litzroth wrote on the list about a way to nudge guile into using the .dylib extenstion instead of the .so when searching for libraries.
To me this seems the most promising, especially with the future in mind.

regards

Maurits




reply via email to

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