Re: [Chicken-users] Problems with Chicken 2.732 on Mac OS X

[felix winkelmann]

On Dec 25, 2007 2:21 AM, Ivan Raikov <address@hidden> wrote:
>
> Greetings,
>
>   Has anybody had success with running Chicken 2.732 on Mac OS X? When
> I compile and install Chicken 2.732 on Mac OS (with MacPorts
> installed), I get the following error upon trying to load any library:
>

The problem is that extensions do not get the absolute runtime linker
path compiled in (like the executables do - you can verify this yourself
by calling "otool -L" on chicken executables and compiled extensions).
Calling chicken, csi or chicken-setup will pick up the right
libchicken, regardless
of DYLD_LIBRARY_PATH, but loading an extensions with libchicken not being
in a standard library path will fail, which in turn will make "load" think thatt
this is not a proper binary file, which in turn will make "load" try
to load it as
source code. Binary-file detection is implemented for elf, but not yet for
windows(mz/pe) and mac(mach-o).

The solution is to use "install_name_tool" on the compiled extension. I'll
try to get that fixed soon.


cheers,
felix