Thank you for your patience with my zombielike testing.
I (hopefully) fixed the SBCL failure now (see my reply to rpgoldman).
sbcl:
51 tests passing and 0 failing.
Can you create a directory with pathname "c:/foo/" and call from CLISP (lisp-implementation-version) (ext:probe-pathname* "c:/foo/") (POSIX:file-stat "c:/foo/" nil)
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; dcooper8@seven ~/genworks/cl-engines/windows/clisp/clisp-2.49 $ ./clisp.exe i i i i i i i ooooo o ooooooo ooooo ooooo I I I I I I I 8 8 8 8 8 o 8 8 I \ `+' / I 8 8 8 8 8 8 \ `-+-' / 8 8 8 ooooo 8oooo `-__|__-' 8 8 8 8 8 | 8 o 8 8 o 8 8 ------+------ ooooo 8oooooo ooo8ooo ooooo 8
Welcome to GNU CLISP 2.49 (2010-07-07) http://clisp.cons.org/
Copyright (c) Bruno Haible, Michael Stoll 1992, 1993 Copyright (c) Bruno Haible, Marcus Daniels 1994-1997 Copyright (c) Bruno Haible, Pierpaolo Bernardi, Sam Steingold 1998 Copyright (c) Bruno Haible, Sam Steingold 1999-2000 Copyright (c) Sam Steingold, Bruno Haible 2001-2010
Type :h and hit Enter for context help.
[1]> (lisp-implementation-version)
"2.49 (2010-07-07) (built on STSst063.jenty.by [150.0.0.63])" [2]> (ext:probe-pathname "c:/foo/")
#P"C:\foo\" ; #P"C:\foo\" ; 3602368770 ; 0 [3]> (POSIX:file-stat "c:/foo/" nil)
*** - Win32 error 2 (ERROR_FILE_NOT_FOUND): The system cannot find the file spec ified. The following restarts are available: ABORT :R1 Abort main loop Break 1 [4]> :r1
[5]> ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
If you need to require something before to be able to use the POSIX package, e.g. (require "posix") or (require "POSIX"), that's a good datapoint, too.
Did not need to require anything.
Are you using the latest CLISP? Where did you get it when? Sigh.
2.49. I believe I got it from Sourceforge but not 100% sure anymore.
The other two failures are the run-program issue we've been trying to debug for some time, and unhappily this attempt to trace ext:shell failed because or a package lock. Can you try to (ext:without-package-lock ...) or something around the (trace ...) or (eval '(trace ...)) to make it work? You can run a single test with: make t l=clisp t=test-run-program.script
See here:
https://dl.dropboxusercontent.com/u/19667598/asdf-failures/3.1.0.73/clisp-te...