Re: Lilypond on MacosX Leopard

[Hans Aberg]

On 2 Nov 2007, at 02:30, immanuel litzroth wrote:

> I tried to compile lilypond with the help of macports today and I  
> don't
> have much good news.
> 1) The guile in macports didn't seem to compile for me due to some  
> errors related to open64 and such. A downloaded guile had the same  
> problem but I hacked my way around that and got guile to compile.

I tried to compiled latest Guile on Mac OS 10.4.10 some time ago, and  
it failed. I sent in a bug report, but got no reply.

> 2) I added the required other packages from macports with only  
> minor problems.
> 3) Lilypond compiled ok up to a point where it was trying to run  
> sourceforge on a x.pfb in a TTF directory to create a ttf. At that  
> point
> I did have the lilypond executable and could run it only to  
> discover that the guile interpreter was trying to load .so files  
> instead of dylibs.

The filename extension '.so' is for dynamic libraries on computers  
using a Linux like kernels. Mac OS X uses the kernel Mach, and  
dynamic libraries have the ending '.dylib'. As long as the libraries  
you try to call have been created on Mac OS X (I haven't found a way  
to call a Linux dynamic library on a Mac), all you have to do is to  
change the file name extension to .dylib; I think:

The dynamic library functions are named the same on Mac OS X:
   dlclose  dlopen  dlsym
See the 'man' pages or search the Apple developer site.

  Hans Åberg