This is the mail archive of the cygwin-apps mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

clisp packaging problem


Reini,

The clisp package has a problem very similar to the libsigsegv problem reported by Corinna (http://cygwin.com/ml/cygwin-apps/2011-05/msg00000.html). I'm starting a new thread because it's a different package, but the basic issue is the same: The build is set up to treat Cygwin as being "like Windows" rather than being a POSIX system.

I recently had occasion to build clisp-2.49 and ran into trouble because the build on Cygwin links against various libraries in /usr/lib/w32api. See

http://tug.org/pipermail/tlbuild/2011q2/001885.html

for details. The problem can be traced to the following in clisp-2.49/modules/syscalls/configure.in:

if test "$ac_cv_header_shlobj_h" = yes ; then
   LIBS=${LIBS}' -luser32 -lole32 -loleaut32 -luuid';
fi

together with the following in clisp-2.49/modules/syscalls/calls.c:

#if defined(WIN32_NATIVE) || defined(UNIX_CYGWIN32)
#include <shlobj.h>

These are only two examples. Here's a third I noticed: The following lines in clisp-2.49/src/encoding.d make the Cygwin build of clisp use DOS line endings:

 #if defined(WIN32) || (defined(UNIX) && (O_BINARY != 0))
  pushSTACK(S(Kdos));           /* :line-terminator */

This one is minor, but I think it indicates a basic misunderstanding of what Cygwin is.

Ken


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]