[Ecls-list] ECL on Windows 32-bit with msys/mingw

[Gabriel Dos Reis]

Juan Jose Garcia-Ripoll <juanjose.garciaripoll at googlemail.com> writes:

| On Wed, Aug 18, 2010 at 11:15 PM, Juan Jose Garcia-Ripoll <
| juanjose.garciaripoll at googlemail.com> wrote:
| 
|     On Wed, Aug 18, 2010 at 6:37 PM, Gabriel Dos Reis <gdr at cs.tamu.edu> wrote:
| 
|         libeclmin.a(ffi.o): In function `si_make_dynamic_callback':
|         c:/Docume~1/gdr/Desktop/ecl.cvs/src/c/ffi.d:976: undefined reference to
|         `ffi_prep_closure'
| 
|         libeclmin.a(ffi.o): In function `si_call_cfun':
|         c:/Docume~1/gdr/Desktop/ecl.cvs/src/c/ffi.d:925: undefined reference to
|         `ffi_call'
| 
| 
|     This code should not be compiled and I can guarantee I do not see this in
|     my copy of mingw. Is there a library called libffi in your system, or did
|     ECL detect it at configuration time? It should appear in the log or by a
|     definition HAVE_LIBFFI in ecl/config.h If so you could you try using
|     --without-dffi
| 
| 
| I have seen this precise error when building with a recent version of cygwin
| (see http://ecls.sourceforge.net/logs/cygwin32) which comes with a -lffi
| library. ECL detects it and tries to use it, but it fails because it seems it
| is not the actual libffi or it has some other API. I just wonder why you saw
| the same error in pure Mingw (while I don't http://ecls.sourceforge.net/logs/
| mingw32)

Hi Juanjo,

  Indeed there is a libffi.a installed with my copy of MinGW.  It comes
with the precompiled GNU's Java front-end gcj (which uses it).  If I
understand correctly, there might be two libffi floating around: one
that ECL wants, and one that comes with GNU Compiler suite.  Yet, they
may not be the same.  In that case, I think it ought to be the case that
ECL has a definite idea about which libffi it wants and test for it at
configuration time.  Until your message, I was completely puzzled by
these link failures.  Indeed, configuring with --without-dffi, the build
is OK.

What is the relation between --enable-shared and --with-dffi?

-- Gaby