several loosely related topics:
- I got today digest Vol 1 #1059 containing
> 1. write-byte-sequence :no-hang (Don Cohen)
> Date: Thu, 18 Sep 2003 21:05:02 -0700
> From: don-sourceforge@... (Don Cohen)
> To: clisp-devel@...
> Subject: write-byte-sequence :no-hang
> [oops, sent this to clisp-list by mistake]
I'm a bit confused as to why I'm getting this one out of order.
I'm even more worried that others will be confused and think this
contains the latest diffs. It doesn't. The latest looks like
Hoehle, Joerg-Cyril writes:
> It's not enough to modify sequence.d.
> You must update subr.d and esp. subrkw.d
Thank you! Current diffs below. In (extremely) limited testing
- I mentioned earlier that my latest build of 2.31 fails the test
suite as follows:
(IF *NO-ICONV-P* "AZ" (CONVERT-STRING-FROM-BYTES '#(255 254 65 0 13) (MAKE-ENCODING :CHARSET "utf-16" :INPUT-ERROR-ACTION #\Z)))
*** - Character #\uFEFF cannot be represented in the character set CHARSET:ISO-8859-1
I'm still hoping for some suggestions. Since then I've noticed that
it works on another machine, and that on this machine after I install
libsigsegv it still fails at the same place.
- Speaking of libsigsegv, I notice that earlier versions seem to
contain libsigsegv. This seems much better than building without
it or requiring people to get and install it separately. Is there
some reason not to distribute clisp (both source and binary) with
- Another problem I noticed was that after installing libsigsegv I
tried to redo ./config and failed:
../src/lndir: destination already exists: /root/clisp/clisp-2.31/src/bindings
I think this should at least tell you what to do if you want to
reconfigure. How are you supposed to do it?
From: Sam Steingold <sds@gn...> - 2003-09-24 20:49:34
> * Don Cohen <qba-fbheprsbetr@...> [2003-09-19 19:10:22 -0700]:
> - Speaking of libsigsegv, I notice that earlier versions seem to
> contain libsigsegv. This seems much better than building without it
> or requiring people to get and install it separately. Is there some
> reason not to distribute clisp (both source and binary) with
libsigsegv is linked statically, so it is always in the binary
it is not in the source distribution because it is a totally separate
project and is a configure-time dependency of CLISP.
Actually, ffcall is _also_ a configure-time dependency, and this is why
I hope that come day it will be a separate package too.
> - Another problem I noticed was that after installing libsigsegv I
> tried to redo ./config and failed:
> ../src/lndir: destination already exists: /root/clisp/clisp-2.31/src/bindings
> I think this should at least tell you what to do if you want to
> reconfigure. How are you supposed to do it?
you are supposed to _always_ build in a separate directory.
do "cd src; make distclean", or, better yet,
and "rm -rf build-dir" before reconfiguring.
PS. I am flattered by your trust in CLISP - you are building it as
Sam Steingold (http://www.podval.org/~sds) running w2k
<http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/>
The early bird may get the worm, but the second mouse gets the cheese.