This is the mail archive of the
mailing list for the Cygwin project.
Re: Updated: clisp-2.44-1 for cygwin
- From: Mark Harig <idirectscm at aim dot com>
- To: The Cygwin Mailing List <cygwin at cygwin dot com>
- Date: Wed, 06 Feb 2008 12:12:21 -0500
- Subject: Re: Updated: clisp-2.44-1 for cygwin
- References: <47A799BA.firstname.lastname@example.org>
Reini Urban wrote:
I've released the new upstream clisp-2.44 plus subpackages -clx, -gtk2
and -gdi for cygwin.
7 - Major bugfixes
./configure --fsstnd=redhat --with-dynamic-ffi \
--with-module=rawsock --with-module=dirkey \
--with-module=bindings/win32 --with-module=berkeley-db \
--with-module=pcre --with-module=postgresql \
--with-module=fastcgi --with-module=zlib \
--with-module=gdbm --with-module=libsvm \
--prefix=/usr --build build
User visible changes
* CLISP does not come with GNU libffcall anymore.
This is now a separate package and should be installed separately.
Pass --with-libffcall-prefix to the top-level configure if it is not
installed in a standard place.
Option --with-dynamic-ffi is now replaced with --with-ffcall.
There appears to be a contradiction between the Cygwin announcement
and the upstream clisp announcement. The upstream announcement states
that the configuration option '--with-dynamic-ffi' has been replaced by
the option '--with-ffcall', but the Cygwin announcement states that the
no-longer-supported '--with-dynamic-ffi' configuration option was used.
Does the Cygwin announcement merely contain a typo (i.e., the new
option was, in fact, used, but not described correctly), or was the
Cygwin clisp package configured incorrectly, using the old option?
If it is the latter, then this might explain the fact that 'cygcheck'
that it cannot find 'cygfcgi-0.dll' for
[version] is either 2.43 or 2.44).
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html