Re: [Chicken-users] 1.12 on MacOS X

[Felix Winkelmann]

Brian Campbell wrote:
> I have tried compiling Chicken 1.12 on MacOS X 10.2.6, and I get the 
> following error (with context):
>
> /bin/sh ./libtool --mode=link gcc  -O3 -fomit-frame-pointer -Wall 
> -Wno-unused -Wno-uninitialized -fstrict-aliasing    -o 
> libstuffed-chicken.la -rpath /usr/local/lib -version-info=0:0:0 
> -no-undefined -lm extras.lo format.lo match-support.lo lolevel.lo 
> tinyclos.lo script-utils.lo tcp.lo regex.lo posix.lo libchicken.la -lm
> rm -fr .libs/libstuffed-chicken.la .libs/libstuffed-chicken.* 
> .libs/libstuffed-chicken.*
> gcc -r -keep_private_externs -nostdlib -o 
> .libs/libstuffed-chicken.0.0.0.dylib-master.o  extras.lo format.lo 
> match-support.lo lolevel.lo tinyclos.lo script-utils.lo tcp.lo regex.lo 
> posix.lo && gcc -dynamiclib  -o .libs/libstuffed-chicken.0.0.0.dylib 
> .libs/libstuffed-chicken.0.0.0.dylib-master.o  -L./.libs -lchicken -lm 
> -lc -install_name /usr/local/lib/libstuffed-chicken.0.dylib 
> -compatibility_version 1 -current_version 1.0
> ld: Undefined symbols:
> _environ
> /usr/bin/libtool: internal link edit command failed
> make[1]: *** [libstuffed-chicken.la] Error 1
> make: *** [all] Error 2
>
> Can anyone tell me what I need to do to fix this? Am I missing some 
> other required package, or what?

Hi!

Googling around for this, I stumbled over several occurrences of this
problem. Now, I don't have a 100% answer, so I recommend replacing
the line

extern char **environ;

in posix.scm with

char **environ;

You won't be able to use `current-environment', though, but I guess this
is not really crucial. Anyway, this is just a crude hack to get you
going.

Note that I had reports that building the dynamically linked version
of Chicken fails on Jaguar, a couple of months ago. So if this still
doesn't work (depending on OS and libtool version), you should configure
Chicken with "--disable-shared".


cheers,
felix