From: Peter Szabo
Subject: a try to use  clisp-2.34  on Windows
Date: 
Message-ID: <1124269899.415311@slbhw0>
Hello,
I've downloaded clisp-2.34 and installed exactly as clisp-2.33 before
(which is working fine). But now after 'M-x' slime:


in buffer *inferior-lisp*:

c:\myhome>C:\emacs\emacs-21.3\site-lisp\clisp-2.34\full\lisp.exe -M 
C:\emacs\emacs-21.3\site-lisp\clisp-2.34\full\lispinit.mem -B 
C:\emacs\emacs-21.3\site-lisp\clisp-2.34\full\

logo appears, than copyright, than
.......... some compiling and loading .....
........ than

;; Compiling file C:\emacs-21.3\slime-1.2.1\swank-clisp.lisp ...
WARNING: DEFMETHOD: redefining method (LISP-IMPLEMENTATION-TYPE-NAME NIL) in
          C:\emacs-21.3\slime-1.2.1\swank-clisp.lisp, was defined in
          C:\emacs-21.3\slime-1.2.1\swank-backend.lisp
WARNING: DEFMETHOD: redefining method (UNPROFILE-ALL NIL) in
          C:\emacs-21.3\slime-1.2.1\swank-clisp.lisp, was defined in
          C:\emacs-21.3\slime-1.2.1\swank-backend.lisp
;; Wrote file C:\myhome\.slime\fasl\clisp-2.34-win32-pc386\swank-clisp.fas
;;  Loading file 
C:\myhome\.slime\fasl\clisp-2.34-win32-pc386\swank-clisp.fas ...
WARNING: Replacing method #<STANDARD-METHOD (#<BUILT-IN-CLASS T>)> in
           #<STANDARD-GENERIC-FUNCTION CALL-WITHOUT-INTERRUPTS>

WARNING: Replacing method #<STANDARD-METHOD NIL> in
           #<STANDARD-GENERIC-FUNCTION LISP-IMPLEMENTATION-TYPE-NAME>

WARNING: Replacing method #<STANDARD-METHOD (#<BUILT-IN-CLASS T>)> in
           #<STANDARD-GENERIC-FUNCTION SET-DEFAULT-DIRECTORY>

WARNING: Replacing method #<STANDARD-METHOD (#<BUILT-IN-CLASS T>)> in
           #<STANDARD-GENERIC-FUNCTION ARGLIST>

WARNING: Replacing method #<STANDARD-METHOD NIL> in
           #<STANDARD-GENERIC-FUNCTION UNPROFILE-ALL>

WARNING: DEFUN/DEFMACRO: redefining function BREAK in 
C:\myhome\.slime\fasl\clisp-2.34-win32-pc386\swank-clisp.fas,
          was defined in D:\gnu\clisp\current\build-O-mingw\condition.fas
;;  Loaded file C:\myhome\.slime\fasl\clisp-2.34-win32-pc386\swank-clisp.fas
;; Compiling file C:\emacs\emacs-21.3\slime-1.2.1\swank-gray.lisp ...
;; Wrote file C:\myhome\.slime\fasl\clisp-2.34-win32-pc386\swank-gray.fas
;;  Loading file 
C:\myhome\.slime\fasl\clisp-2.34-win32-pc386\swank-gray.fas ...
WARNING: The generic function #<STANDARD-GENERIC-FUNCTION 
STREAM-LINE-COLUMN>
          is being modified, but has already been called.
WARNING: The generic function #<STANDARD-GENERIC-FUNCTION 
STREAM-FORCE-OUTPUT>
          is being modified, but has already been called.
WARNING: The generic function #<STANDARD-GENERIC-FUNCTION 
STREAM-LINE-COLUMN>
          is being modified, but has already been called.
;;  Loaded file C:\myhome\.slime\fasl\clisp-2.34-win32-pc386\swank-gray.fas
;; Compiling file C:\emacs\emacs-21.3\slime-1.2.1\swank.lisp ...
;; Wrote file C:\myhome\.slime\fasl\clisp-2.34-win32-pc386\swank.fas
;;  Loading file C:\myhome\.slime\fasl\clisp-2.34-win32-pc386\swank.fas ...
;;  Loaded file C:\myhome\.slime\fasl\clisp-2.34-win32-pc386\swank.fas
The following functions were used but are deprecated:

  SET - This function name is anachronistic. Use SETF SYMBOL-VALUE instead.
0 errors, 0 warnings
WARNING: These Swank interfaces are unimplemented:
          (ACTIVATE-STEPPING ADD-FD-HANDLER ADD-SIGIO-HANDLER ALL-THREADS
          CALLS-WHO
          DISASSEMBLE-FRAME FIND-THREAD GETPID INSPECT-FOR-EMACS
          INTERRUPT-THREAD
          RECEIVE REMOVE-FD-HANDLERS REMOVE-SIGIO-HANDLERS SEND
          SLDB-BREAK-AT-START
          SLDB-BREAK-ON-RETURN SPAWN THREAD-ID TOGGLE-TRACE WHO-MACROEXPANDS
          WHO-SPECIALIZES)
;; Loaded file C:\emacs-21.3\slime-1.2.1\swank-loader.lisp
T
[2]>
;; Swank started at port: 1636.
---------------------------------------------------------------------------
and in buffer *sldb nil/0*:

FUNCALL: undefined function NIL

    [Condition of type SYSTEM::SIMPLE-UNDEFINED-FUNCTION]

Restarts:
   0: [USE-VALUE] You may input a value to be used instead of 
(FDEFINITION 'NIL).
   1: [RETRY] Retry
   2: [STORE-VALUE] You may input a new value for (FDEFINITION 'NIL).
   3: [ABORT] Abort handling SLIME request.
   4: [ABORT] ABORT

Backtrace:
   0: frame binding variables (~ = dynamically):
   | ~ SYSTEM::*FASOUTPUT-STREAM* <--> NIL

   1: EVAL frame for form (SWANK:CONNECTION-INFO)

   2: EVAL frame for form (SWANK:START-SERVER 
"c:/MYHOME/LOCALS~1/Temp/slime.2008" :EXTERNAL-FORMAT :ISO-LATIN-1-UNIX)

   3: EVAL frame for form (SWANK:START-SERVER 
"c:/MYHOME/LOCALS~1/Temp/slime.2008" :EXTERNAL-FORMAT :ISO-LATIN-1-UNIX)
-----------------------------------------------------------------------------

What is different to clisp-2.33? SLIME is the same (slime-1.2.1)
Many thanks in advance!
peter

From: joesb
Subject: Re: a try to use clisp-2.34 on Windows
Date: 
Message-ID: <1124275496.948825.198700@g47g2000cwa.googlegroups.com>
Did you try getting the SLIME CVS HEAD version yet?

Usually fix things.
From: Peter Szabo
Subject: Re: a try to use clisp-2.34 on Windows
Date: 
Message-ID: <1124279129.85356@slbhw0>
joesb wrote:

> Did you try getting the SLIME CVS HEAD version yet?
> 
> Usually fix things.
> 
I'm behind a firewall (and more). No access to CVS.
But thank you for the hint. I'll try from home.

Peter
From: Dan Schmidt
Subject: Re: a try to use clisp-2.34 on Windows
Date: 
Message-ID: <uvf24ljhz.fsf@turangalila.harmonixmusic.com>
Peter Szabo <···········@alcatel.de> writes:

| joesb wrote:
|
|| Did you try getting the SLIME CVS HEAD version yet?
|| Usually fix things.
||
| I'm behind a firewall (and more). No access to CVS.
| But thank you for the hint. I'll try from home.

FWIW, I had the same problem and getting the CVS head of SLIME fixed
it.  That was a few weeks ago, though, so it's always possible
something has broken in the meantime.
From: Peter Szabo
Subject: Re: a try to use clisp-2.34 on Windows
Date: 
Message-ID: <1124351251.815572@slbhw0>
Dan Schmidt wrote:
> Peter Szabo <···········@alcatel.de> writes:
> 
> | joesb wrote:
> |
> || Did you try getting the SLIME CVS HEAD version yet?
> || Usually fix things.
> ||
> | I'm behind a firewall (and more). No access to CVS.
> | But thank you for the hint. I'll try from home.
> 
> FWIW, I had the same problem and getting the CVS head of SLIME fixed
> it.  That was a few weeks ago, though, so it's always possible
> something has broken in the meantime.
The checkout from CVS didn't worked for me. But than I got this source:
    http://common-lisp.net/cgi-bin/viewcvs.cgi/slime/?cvsroot=slime
and the problem is fixed.
Peter
From: fba_free
Subject: Re: a try to use clisp-2.34 on Windows
Date: 
Message-ID: <1124353088.151847.281670@g14g2000cwa.googlegroups.com>
Hi,

I had similar problems as I used the FULL linkkit of CLISP 2.34.
I investigated a bit and found it was a PNAME problem in the
file swank-clisp.lisp in the SLIME software.
When the WIN32 package is defined, you get into trouble because
of the GetCurrentProcessId function, whose PNAME is actually
"gETcURRENTpROCESSiD" and not "GetCurrentProcessId".
So you have to hack the code a little bit and replace the faulty
pname in getpid:
in line 89 of swank-clisp.lisp, one should have:
#+win32
(defmethod getpid ()
  (cond ((find-package :win32)
	 (funcall (find-symbol "gETcURRENTpROCESSiD" :win32)))
	(t
	 (system::getenv "PID"))))

Have fun with SLIME and CLISP.

Yours,

Frédéric Bastenaire
From: Sam Steingold
Subject: Re: a try to use clisp-2.34 on Windows
Date: 
Message-ID: <ud5obxsuq.fsf@gnu.org>
> * fba_free <···@serr.se> [2005-08-18 01:18:08 -0700]:
>
> 	 (funcall (find-symbol "gETcURRENTpROCESSiD" :win32)))

this is much better:
(cs-cl:find-symbol "GetCurrentProcessId" :win32)

OTOH, why not just use

(os:process-id)??

it works on all operating systems and it is present in the base linkset too.
see <http://clisp.cons.org/impnotes/syscalls.html#process-id>

-- 
Sam Steingold (http://www.podval.org/~sds) running w2k
<http://www.dhimmi.com/> <http://www.savegushkatif.org> <http://pmw.org.il/>
<http://www.mideasttruth.com/> <http://truepeace.org> <http://www.camera.org>
There are no answers, only cross references.
From: Peter Szabo
Subject: Re: a try to use clisp-2.34 on Windows
Date: 
Message-ID: <1124378858.758276@slbhw0>
Sam Steingold wrote:

>>* fba_free <···@serr.se> [2005-08-18 01:18:08 -0700]:
>>
>>	 (funcall (find-symbol "gETcURRENTpROCESSiD" :win32)))
> 
> 
> this is much better:
> (cs-cl:find-symbol "GetCurrentProcessId" :win32)
> 
> OTOH, why not just use
> 
> (os:process-id)??
> 
> it works on all operating systems and it is present in the base linkset too.
> see <http://clisp.cons.org/impnotes/syscalls.html#process-id>
> 
cool! I replaced in swank-clisp.lisp the expression

(let ((getpid (or (find-symbol "PROCESS-ID" :system)
		  old name prior to 2005-03-01, clisp <= 2.33.2
		  (find-symbol "PROGRAM-ID" :system)
		  #+win32 ; integrated into the above since 2005-02-24
		  (and (find-package :win32) ; optional modules/win32
		       (find-symbol "gETcURRENTpROCESSiD" :win32)))))
   (defimplementation getpid ()		; a required interface
     (cond
      (getpid (funcall getpid))
      #+win32 ((ext:getenv "PID"))	; where does that come from?
      (t -1))))

by

(defimplementation getpid ()
   (OS:PROCESS-ID))

and it works!(on my system)
One refinement for the next revision?
Peter
From: Peter Szabo
Subject: Re: a try to use clisp-2.34 on Windows
Date: 
Message-ID: <1124360670.815012@slbhw0>
fba_free wrote:
> Hi,
> 
> I had similar problems as I used the FULL linkkit of CLISP 2.34.
> I investigated a bit and found it was a PNAME problem in the
> file swank-clisp.lisp in the SLIME software.
> When the WIN32 package is defined, you get into trouble because
> of the GetCurrentProcessId function, whose PNAME is actually
> "gETcURRENTpROCESSiD" and not "GetCurrentProcessId".
> So you have to hack the code a little bit and replace the faulty
> pname in getpid:
> in line 89 of swank-clisp.lisp, one should have:
> #+win32
> (defmethod getpid ()
>   (cond ((find-package :win32)
> 	 (funcall (find-symbol "gETcURRENTpROCESSiD" :win32)))
> 	(t
> 	 (system::getenv "PID"))))
> 
> Have fun with SLIME and CLISP.
> 
> Yours,
> 
> Fr�d�ric Bastenaire
> 
Fine. Thank you.
In Rev. 1.53 of swank-clisp.lisp is "gETcURRENTpROCESSiD"
notyet contained.
Peter
From: Peter Szabo
Subject: Re: a try to use clisp-2.34 on Windows
Date: 
Message-ID: <1124284486.927940@slbhw0>
Peter Szabo wrote:

> joesb wrote:
> 
>> Did you try getting the SLIME CVS HEAD version yet?
>>
>> Usually fix things.
>>

Now I leard more: The URL
  				       http://common-lisp.net/cgi-bin/viewcvs.cgi/slime/?cvsroot=slime

allows me to download files with recent versions.
That helped!  Thank you!

> I'm behind a firewall (and more). No access to CVS.
> But thank you for the hint. I'll try from home.
> 
> Peter