#690 clisp configure fails to locate ffcall libraries.

[Pascal J. Bourguignon]

Problems with ffcall on MacOSX:

• ffcall from cvs (following instructions from configure --with-ffcall), fails to compile on MacOSX (Yosemite, el Capitan, Sierra).

• however, ffcall has been updated or patched by MacPorts, and we can install ffcall with MacPorts on those MacOSX systems. But clisp configure seems incapable of locating the libraries. With the right options, it can locate the header files, but it fails to locate the libraries when testing for __builtin_avcall and trampoline_r_data0:

checking how to link with libavcall... /opt/local/lib/libavcall.a
checking how to link with libcallback... /opt/local/lib/libcallback.a
checking avcall.h usability... yes
checking avcall.h presence... yes
checking for avcall.h... yes
checking callback.h usability... yes
checking callback.h presence... yes
checking for callback.h... yes
checking for library containing __builtin_avcall... no
checking for library containing trampoline_r_data0... no
checking whether libffcall is installed... no

with any combination of:
export CPPFLAGS=-I/opt/local/include
export LDFLAGS=-L/opt/local/lib
export LIBS='/opt/local/lib/libcallback.a /opt/local/lib/libavcall.a'
and
--with-ffcall-prefix=/opt/local

[Pascal J. Bourguignon]

compilation script and log.

[Pascal J. Bourguignon]

Oos, sorry, current clisp from mercurial doesn't compile "out of the box" on macOS Sierra, but seems to have some problem with iconv (libiconv).

Only MacPorts clisp compiles and run (but without FFI).

[Bruno Haible]

Indeed there were several problems with locating the libraries. They were fixed over the last 12 months: in gnulib's lib-prefix.m4, in configure (on 2017-08-24). Locating the libraries should now work in nearly all cases. In the remaining cases you do need to augment CPPFLAGS and LDFLAGS.