Re: [STUMP] [OT] How do you compile clisp correctly ?

[Xavier Maillard]

Xavier Maillard <maillaxa <at> gmail.com> writes:

> So how do you compile clisp to fit stumpwm requirement ?

For information, here is the clisp --version as shipped with slackware:

bash-3.1# clisp --version
GNU CLISP 2.41 (2006-10-13) (built on tree.slackware.lan [127.0.0.1])
Software: GNU C 4.1.1 
gcc -g -O2 -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type
-Wmissing-declarations -Wno-sign-compare -O2 -fexpensive-optimizations
-falign-functions=4 -DUNICODE -DDYNAMIC_FFI -I. -x none libcharset.a libavcall.a
libcallback.a /usr/lib/libreadline.so -lncurses -ldl   -L/usr/lib -lsigsegv
-L/usr/lib -lc 
SAFETY=0 HEAPCODES LINUX_NOEXEC_HEAPCODES GENERATIONAL_GC SPVW_BLOCKS SPVW_MIXED
TRIVIALMAP_MEMORY
libsigsegv 2.4
libreadline 5.2
Features: 
(READLINE REGEXP SYSCALLS I18N LOOP COMPILER CLOS MOP CLISP ANSI-CL COMMON-LISP
 LISP=CL INTERPRETER SOCKETS GENERIC-STREAMS LOGICAL-PATHNAMES SCREEN FFI
 GETTEXT UNICODE BASE-CHAR=CHARACTER PC386 UNIX)
C Modules: (clisp i18n syscalls regexp readline)
Installation directory: /usr/lib/clisp/
User language: ENGLISH
Machine: I686 (I686) localhost [127.0.0.1]

When compiling stumpwm, it says it can't find PPCRE module.

Xavier