From: Brian E. <be...@me...> - 2007-07-29 10:40:11
|
Hi In order to make xindy (http://xindy.sourceforge.net/) work on windows xp I am trying to compile clisp. I tried 2.33 and 2.38 (with the instructions on http://www.frank-buss.de/lisp/clisp.html) with no luck, but after taking the most recent win32.lisp and calls.c on cvs I am able to compile 2.41. However, I have a few problems: 1: makemake output has several lines looking like: ./makemake: [: argument expected which I had to remove to make. 2: make check gives me an error. It gives me streams.erg: Form: (LET ((F "foo.bar") FWD SIZE DIR DECODED) (UNWIND-PROTECT (PROGN (WITH-OPEN-FILE (S F :DIRECTION :OUTPUT) (WRITE S :STREAM S) (SETQ SIZE (FILE-LENGTH S))) (WITH-OPEN-FILE (S F :DIRECTION :PROBE) (SETQ FWD (FILE-WRITE-DATE S))) (SETQ DIR (FIRST (DIRECTORY F :FULL T)) DECODED (SUBSEQ (MULTIPLE-VALUE-LIST (DECODE-UNIVERSAL-TIME FWD)) 0 6)) (LIST (OR (EQUAL (THIRD DIR) DECODED) (LIST DIR FWD DECODED)) (OR (= (FOURTH DIR) SIZE) (LIST DIR SIZE)))) (DELETE-FILE F))) CORRECT: (T T) CLISP : (((#1=#P"C:\\xindy\\clisp-2.41.tar\\clisp-2.41\\src\\tests\\foo.bar" #1# (13 56 9 29 7 2007) 52) 3394684573 (13 56 6 29 7 2007)) T) Differ at position 0: T vs ((#1=#P"C:\\xindy\\clisp-2.41.tar\\clisp-2.41\\src\\tests\\foo.bar" #1# (13 56 9 29 7 2007) 52) 3394684573 (13 56 6 29 7 2007)) CORRECT: (T T) CLISP : (((#1=#P"C:\\xindy\\clisp-2.41.tar\\clisp-2.41\\src\\tests\\foo.bar" #1# (13 56 9 29 7 2007) 52) 3394684573 (13 56 6 29 7 2007)) T) 3: The xindy compilation instructions says that I should get lisp.run and lispinit.mem as the actual xindy program. I only see lispinit.mem in my compiled clisp. I guess it is because lisp.run is named lisp.exe on windows. Am I right? tia, -- Brian (remove the sport for mail) http://www.et.web.mek.dtu.dk/Staff/be/be.html http://www.rugbyklubben-speed.dk |
From: Brian E. <be...@me...> - 2007-07-29 14:48:30
|
Brian Elmegaard <be...@me...> writes: > I only see lispinit.mem in my compiled clisp. I guess it is because > lisp.run is named lisp.exe on windows. Am I right? This was easy. I am right. I have lisp.exe and lispinit.mem. According to the instructions on xindy installation I now should cp clisp-2.33.2/src/full/lisp.run binaries/xindy.run cp clisp-2.33.2/src/full/lispinit.mem binaries/base.mem When I try to run the lisp.exe renamed to xindy.exe I get: $ .\xindy module 'syscalls' requires package OS. Do I need to move something to make a renamed lisp.exe find the modules that have been included during compile? I can make the lisp.exe in the original location run. Regards, -- Brian (remove the sport for mail) http://www.et.web.mek.dtu.dk/Staff/be/be.html http://www.rugbyklubben-speed.dk |
From: Jack U. <jd...@gm...> - 2007-07-29 15:57:10
|
On 7/29/07, Brian Elmegaard <be...@me...> wrote: > > [...] > > When I try to run the lisp.exe renamed to xindy.exe I get: > $ .\xindy > module 'syscalls' requires package OS. > > Do I need to move something to make a renamed lisp.exe find the > modules that have been included during compile? There are several command-line args that you need to pass: -B lisp-lib-dir -K linking-set -M mem-file See http://www.podval.org/~sds/clisp/impnotes/clisp.html for more information. >From your previous email: > I tried 2.33 and 2.38 (with the instructions on > http://www.frank-buss.de/lisp/clisp.html) with no luck, but after > taking the most recent win32.lisp and calls.c on cvs I am able to > compile 2.41. You could also compile the latest from CVS in its entirety, just so that you have all the fixes and enhancements checked in since 2.41 was released. > 1: makemake output has several lines looking like: > ./makemake: [: argument expected > which I had to remove to make. I have seen those warnings but in my experience they don't result in build failure. It's not high enough priority for me to spend time investigating right now. > 2: make check gives me an error. It gives me streams.erg: > [snip snip] That particular test failure was reported and fixed in December 2005, see http://article.gmane.org/gmane.lisp.clisp.devel/15067 whereas 2.41 was released in October 2006. Now, my memory may be faulty, but I don't recall seeing that test failure when compiling 2.41 with MinGW. Since you've apparently tried to build at least one other prior release from source, I'd recommend double-checking that you really are building 2.41 source. Or as I said above, build the latest from CVS. -- Jack Unrue |
From: Brian E. <be...@me...> - 2007-08-08 06:10:58
|
"Jack Unrue" <jd...@gm...> writes: > build at least one other prior release from source, I'd recommend > double-checking that you really are building 2.41 source. I am pretty sure aout that. > Or as I said above, build the latest from CVS. How do I get it? It is not clear for me from the sourceforge cvs page. -- Brian (remove the sport for mail) http://www.et.web.mek.dtu.dk/Staff/be/be.html http://www.rugbyklubben-speed.dk |
From: Jack U. <jd...@gm...> - 2007-08-09 01:29:16
|
On 8/8/07, Brian Elmegaard <be...@me...> wrote: > I wrote: > > Or as I said above, build the latest from CVS. > > How do I get it? It is not clear for me from the sourceforge cvs > page. Is this the page you're looking at? http://sourceforge.net/cvs/?group_id=1355 Just follow the anonymous CVS access instructions provided there -- the module name to use is clisp -- Jack Unrue |
From: Brian E. <be...@me...> - 2007-08-09 08:15:16
|
"Jack Unrue" <jd...@gm...> writes: > Is this the page you're looking at? Yes. It is obviously easy enough when you get a cvs client. Sorry. -- Brian (remove the sport for mail) http://www.et.web.mek.dtu.dk/Staff/be/be.html http://www.rugbyklubben-speed.dk |
From: Brian E. <be...@me...> - 2007-08-09 11:29:00
|
"Jack Unrue" <jd...@gm...> writes: > build at least one other prior release from source, I'd recommend > double-checking that you really are building 2.41 source. Or as > I said above, build the latest from CVS. I did now and I have the same test failure. -- Brian (remove the sport for mail) http://www.et.web.mek.dtu.dk/Staff/be/be.html http://www.rugbyklubben-speed.dk |