On Fri, Oct 25, 2002 at 09:37:51AM +0100, Alastair Reid wrote:
even if configure has "--enable-ffi", just issuing "make" doesn't build and/or install the ffihugs executable.
furthermore, separately issuing "make ffihugs" is not sufficient either, and that shows up in some surprising places:
You need to configure with --enable-ffi and then 'make install'. (At least, that's what I've been doing.)
Alastair, can I check a couple of things with you: I've changed configure in CVS so that the FFI is enabled by default if one of the header files for dynamic loading is found (the same test you use in machdep.c for defining getDLL() and friends). I'm assuming that that means static imports should be available, though dynamic ones may not be. Is that right? Levent (and Oliver Braun) asked why ffi-using modules are compiled in the install directories (rather than in the build tree and merely copied on install, like everything else). Is that because the alternative doesn't work if your build tree is full of symbolic links, due to path canonicalization?