Hi, some questions/remarks/bugs 1. Why is ffi disabled by default (./configure --enable-ffi is needed)? 2. If you install without ffi, there will be some header files in $(hugsdir)/libraries/. If you install with ffi, they will be removed. See install_libraries_ffi target in src/MkInstal.in. 3. ffi and ffi libs will be built by a install* target and not by a "build" target. IMO, it's much nicer to build everything by the default and ffi "build" target and install only by the install* targets. BTW, I am no auto{conf|make|...} crack, but on FreeBSD HAVE_LIMITS_H is not defined, but limits.h has to be included for building ffihugs without errors. I use something like s/#ifdef HAVE_LIMITS_H/#if defined(__FreeBSD__)/ for the FreeBSD port, but maybe there will be a better solution (a config.h file for FreeBSD or something) Regards, Olli -- {- IST & IIS _ INF _ UniBwM :: obraun@informatik.unibw-muenchen.de -} {- Tele-Consulting GmbH :: obraun@Tele-Consulting.com -} {- FreeBSD Commmitter :: obraun@FreeBSD.org -}
On Wed, Oct 23, 2002 at 03:19:57PM +0200, Oliver Braun wrote:
BTW, I am no auto{conf|make|...} crack, but on FreeBSD HAVE_LIMITS_H is not defined, but limits.h has to be included for building ffihugs without errors. I use something like s/#ifdef HAVE_LIMITS_H/#if defined(__FreeBSD__)/ for the FreeBSD port, but maybe there will be a better solution (a config.h file for FreeBSD or something)
This one is already fixed in CVS: limits.h is missing from the list of header files in AC_CHECK_HEADERS in src/unix/configure.in -- the fix is to add it and rerun autoheader and autoconf. Unfortunately configure.in doesn't work with newer versions of autoheader (2.50+); if that's all you have, you'll have to add /* Define if you have the <limits.h> header file. */ #undef HAVE_LIMITS_H to src/config.in by hand. Autoconf should be fine, though.
1. Why is ffi disabled by default (./configure --enable-ffi is needed)?
The ffi hasn't been ported to all platforms and turning it off by default was an easy way to avoid bug reports. Ideally though, people would contribute patches to the ffi code. The main platform we lack a port for is the Alpha (though support for HP boxes and StrongArms would be nice). The original calls for porting and testing help are at: http://reid-consulting-uk.ltd.uk/projects/ffi/ The request for help http://haskell.org/pipermail/hugs-bugs/2002-July/000813.html provides instructions on how to test and port the ffi code. -- Alastair Reid alastair@reid-consulting-uk.ltd.uk Reid Consulting (UK) Limited http://www.reid-consulting-uk.ltd.uk/alastair/
participants (3)
-
Alastair Reid -
Oliver Braun -
Ross Paterson