Hi Shawn, >> ***** Build CLisp from CVS > > Perhaps I'm missing something but why are you building clisp from CVS? > Does this same error occur in the latest release of clisp?
I finally could test this. Here my installation experience with the latest stable release of CLisp... 2.48 (as of July 28th). wget ftp://ftp.gnu.org/pub/gnu/clisp/latest/clisp-2.48.tar.gz tar -xvzf clisp-2.48.tar.gz cd clisp-2.48 Installed a few libraries on which CLISP relies: * Installed libffcall mkdir tools; cd tools wget http://www.haible.de/bruno/gnu/ffcall-1.10.tar.gz tar xfz ffcall-1.10.tar.gz cd ffcall-1.10 ./configure make make check sudo make install cd ../.. * Installed libsigsegv cd tools; prefix=`pwd`/i686-pc-linux-gnu wget http://ftp.gnu.org/pub/gnu/libsigsegv/libsigsegv-2.6.tar.gz tar xfz libsigsegv-2.6.tar.gz cd libsigsegv-2.6 ./configure --prefix=${prefix} && make && make check && make install cd ../.. rm -f src/config.cache Compiled CLisp with new-CLX support: ./configure --with-libsigsegv-prefix=${prefix} --with-module="clx/new-clx" cd src vi config.lisp ulimit -s 16384 # increase default stack size make Error!! configure: loading cache ../../config.cache configure: ** NEW CLX checking for gcc... (cached) gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... (cached) o checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking how to run the C preprocessor... (cached) gcc -E checking build system type... (cached) i686-pc-linux-gnu checking host system type... (cached) i686-pc-linux-gnu checking for grep that handles long lines and -e... (cached) /bin/grep checking for egrep... (cached) /bin/grep -E checking for ANSI C header files... (cached) yes checking for sys/types.h... (cached) yes checking for sys/stat.h... (cached) yes checking for stdlib.h... (cached) yes checking for string.h... (cached) yes checking for memory.h... (cached) yes checking for strings.h... (cached) yes checking for inttypes.h... (cached) yes checking for stdint.h... (cached) yes checking for unistd.h... (cached) yes checking for minix/config.h... (cached) no checking whether it is safe to define __EXTENSIONS__... (cached) yes checking for time.h... (cached) yes checking for sys/time.h... (cached) yes checking whether time.h and sys/time.h may both be included... yes checking sys/socket.h usability... yes checking sys/socket.h presence... yes checking for sys/socket.h... yes checking for netdb.h... (cached) yes checking for netinet/in.h... (cached) yes checking for X... (cached) no configure: error: in `/home/sva/src/clisp-2.48/src/clx/new-clx': configure: error: cannot find X Window System See `config.log' for more details. make: *** [clx/new-clx] Error 1 Compiled, then, CLisp with mit-CLX support: ./configure --with-libsigsegv-prefix=${prefix} --with-module="clx/mit-clx" cd src vi config.lisp ulimit -s 16384 # increase default stack size make make check sudo make install cd ../.. Installed CL-PPCRE from Ubuntu's package manager: sudo aptitude install cl-ppcre Installed StumpWM: git clone git://git.savannah.nongnu.org/stumpwm.git cd stumpwm autoconf sudo apt-get install texinfo ./configure --with-lisp=clisp --with-ppcre=/usr/share/common-lisp/source/cl-ppcre sudo make Error! *** - EVAL: undefined function XLIB::%GCONTEXT-KEY->MASK The following functions were used but not defined: XLIB::%GCONTEXT-KEY->MASK STUMPWM::UNCOLORIFY STUMPWM::LOAD-RC-FILE STUMPWM::RUN-WITH-TIMER STUMPWM::TIMER-P STUMPWM::CANCEL-TIMER 0 errors, 3 warnings make: *** [stumpwm] Error 1 New compilation (even without sudo): make This second make command works... What a weird thing... And I'm using this new StumpWM installation for one day, now. I had troubles with CPU loops (and Emacs very slow), but that was my fault (event notifier scripts that run, but without some tools installed... then looping). Any idea about these installation problems? Seb -- Sébastien Vauban _______________________________________________ Stumpwm-devel mailing list Stumpwm-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/stumpwm-devel