From: Chris H. <ha...@ve...> - 2004-05-24 13:05:25
|
I'm running Debian Woody, kernel 2.2.25 and have just spent waaaay too many hours on a Sunday trying to build some version, any version, of clisp. I need to use regexes, and the default clisp install on Debian doesn't seem to support them, when invoked either by 'clisp' *or* 'clisp -K full' it doesn't show up in *features*. (BTW, the same goes for the FreeBSD 4.9 clisp). If I try to use one of the functions, I get an error. So, I downloaded the latest source, libsigsegv, etc., followed directions, and got a SIGSEGV error during the build (something about 0x10a not in [...]). Searched Google and got 14 results - none useful to me at all, but I *did* notice the clisp 'help wanted' page asking for help on this issue. Sorry folks - that is way, _way_ over my head. Tried building w/o libsigsegv, but just got a totally different fatal SIGSEGV error again during the build. 'K - let's try another version. Next I downloaded 2.29, configure, makemake, edit, etc., etc., etc. I got the error below, so I hit Google, the Gmane general list and a few years of the Sourceforge mailing lists - all I found was a hint of a related Debian problem in a January 2004 message from Luke Gorrie on the Sourceforge list, but no resolution. Fiddled around some more, changed some things, rm-rf'ed, unpacked, re-configured and built a few more times trying different things, finally tried building as root, all to no avail. Everytime, it is sooooo close - 'make check' works just fine, but su over to root and 'make install' bombs (see below). Hmmmm. OK, so I get the Debian stable source package (now we are at version 2.27) and start looking through diffs figuring 'hey, they got it built somehow', because I can 'apt-get install' the default-but-insufficient-for-my-purposes build. Sure enough, way deep in the (rather large) Debian diffs is a reference to Debian not handling the symbolic links in the way the Makefile seems to expect. To be honest, at this point, I don't spend the time to figure out exactly what Debian did, or why - it has by now been a long day and I just want to get to work on my regexes (I'm using guile and gawk until I can port to clisp). So I apply the diffs, they work fine, configure, makemake, edit, make check. Builds fine, as it did all the other times for 2.29 and earlier. But when I try to install, same *exact* error. I must either be doing something really silly (or maybe there is something missing from my Debian?) - surely a GNU lisp shouldn't be so difficult to build on Debian GNU/Linux? If it is any help, I *can* build and install the latest GCL, no problem - I have done so several times recently. I've also successfully built and installed recent Python and Postgres, and a few other things - all without a problem. Does anybody have any suggestions or ideas, maybe a link or two? Thanks, g'nite, +Chris P.S. For some reason directories linkkit, base, full, and clisp-link do *not* seem to exist anywhere in the build tree. How did we get this far in the build without what appear to be the output directories? All I can think of is that an error somehow went undetected/unhandled by make. ----------------( /usr/local/lib/clisp *after* naia:~/lisp/clisp-2.27/src# ls -lR /usr/local/lib/clisp/ /usr/local/lib/clisp/: total 16 drwxr-sr-x 2 root staff 4096 May 24 01:19 base drwxr-sr-x 2 root staff 4096 May 24 01:19 data drwxr-sr-x 2 root staff 4096 May 24 01:19 full drwxr-sr-x 2 root staff 4096 May 24 00:33 linkkit /usr/local/lib/clisp/base: total 0 /usr/local/lib/clisp/data: total 1160 -rw-r--r-- 1 root staff 1134578 May 24 01:19 UnicodeData.txt -rw-r--r-- 1 root staff 45476 May 24 01:19 clhs.txt /usr/local/lib/clisp/full: total 0 /usr/local/lib/clisp/linkkit: total 92 -rw-r--r-- 1 root staff 81913 May 24 00:33 clisp.h -rw-r--r-- 1 root staff 1983 May 24 00:33 modules.c -rw-r--r-- 1 root staff 1943 May 24 00:33 modules.d ----------------( 'make install' output naia:~/lisp/clisp-2.27/src# make install if [ ! -d /usr/local ] ; then mkdir /usr/local ; fi if [ ! -d /usr/local ] ; then mkdir /usr/local ; fi if [ ! -d /usr/local/lib ] ; then mkdir /usr/local/lib ; fi if [ ! -d /usr/local/lib/clisp ] ; then mkdir /usr/local/lib/clisp ; fi if [ ! -d /usr/local/lib/clisp/data ] ; then mkdir /usr/local/lib/clisp/data ; fi /usr/bin/install -c -m 644 data/UnicodeData.txt /usr/local/lib/clisp/data/UnicodeData.txt /usr/bin/install -c -m 644 data/clhs.txt /usr/local/lib/clisp/data/clhs.txt if [ ! -d /usr/local/lib/clisp/linkkit ] ; then mkdir /usr/local/lib/clisp/linkkit ; fi (cd /usr/local/lib/clisp && rm -rf base full) mkdir /usr/local/lib/clisp/base mkdir /usr/local/lib/clisp/full for f in clisp-link linkkit/modules.d linkkit/modules.c linkkit/clisp.h base/* full/*; do \ case $f in \ */lisp.run) /usr/bin/install -c $f /usr/local/lib/clisp/$f;; \ *) /usr/bin/install -c -m 644 $f /usr/local/lib/clisp/$f;; \ esac; \ done /usr/bin/install: cannot stat `clisp-link': No such file or directory /usr/bin/install: cannot stat `linkkit/modules.d': No such file or directory /usr/bin/install: cannot stat `linkkit/modules.c': No such file or directory /usr/bin/install: cannot stat `linkkit/clisp.h': No such file or directory /usr/bin/install: cannot stat `base/*': No such file or directory /usr/bin/install: cannot stat `full/*': No such file or directory make: *** [install-bin] Error 1 -- What is life? It is the flash of a firefly in the night. It is the breath of a buffalo in the wintertime. It is the little shadow which runs across the grass and loses itself in the sunset. --- Crowfoot's last words (1890), Blackfoot warrior and orator. |