Prev: How do I go from a variable name literal to the variable itself?
Next: Lisp packaging and version management..
From: Martin on 26 Jan 2010 16:17
On 01/25/2010 10:24 PM, Martin wrote:
> On 01/24/2010 11:34 PM, Tobias C. Rittweiler wrote:
>> Martin <xtd8865(a)gmail.com> writes:
>>
>>> Hi all,
>>>
>>> I've just started my journey through the land of lisp (clisp) on
>>> Slackware64-current using Emacs + slime. I've got a few basic questions
>>> regarding setting up working environment. The emacs slime-mode starts
>>> without any errors but the key bindings seems not to work.
>>
>> Unrelated commentary to your e-mail: I would suggest to use another
>> implementation in combination with Slime. Clisp's integration into Slime
>> is not really good -- the intersection of people who are familiar with
>> Clisp, and the people who use Slime is pretty much empty.
>>
>> As a newcomer, you should probably do your baby steps on SBCL, CCL, or
>> on a commercial implementation (which tend to provide free evaluation
>> versions for personal use.)
>>
>> -T.
>
> Thank you all for your help. I think I'm going to install sblc.
>
> kindest regards
> martin
>
It's me again. I've downloaded sbcl 1.0.34. When I run ./install.sh as
root, I get the following:

> # ./install.sh
> src/runtime/sbcl not found, aborting installation.

Indeed sbcl is not in src/runtime

Do I need to do anything before it?
regards
martin



--
regards

Martin
From: Cor on 26 Jan 2010 17:24


Some entity, AKA Martin <xtd8865(a)gmail.com>,
wrote this mindboggling stuff:
(selectively-snipped-or-not-p)

>>>> I've just started my journey through the land of lisp (clisp) on
>>>> Slackware64-current using Emacs + slime. I've got a few basic questions
>>>> regarding setting up working environment. The emacs slime-mode starts
>>>> without any errors but the key bindings seems not to work.

>>> As a newcomer, you should probably do your baby steps on SBCL, CCL, or
>>> on a commercial implementation (which tend to provide free evaluation
>>> versions for personal use.)

> It's me again. I've downloaded sbcl 1.0.34. When I run ./install.sh as
> root, I get the following:
>
>> # ./install.sh
>> src/runtime/sbcl not found, aborting installation.

yeps, that is a known gotcha..

But the 1.0.34 is also 32-bits only at the moment.

You should get the 64-bit version 1.0.29.
Get can the binary and install that and then recompile the source of 1.0.29
if you want to have a processor specific implementation, or use clisp
the 'lisp' as stated in the INSTALL file, since sbcl needs a lisp to
compile

I did the the binary-1.0.29 install here first and then recompiled the
source here on my slackware64-13.0 on amd64 without a problem.

Cor


--
I never threathen but merely state the consequences of your choice.
The other cheek is a .40 JHP
http://www.clsnet.nl

From: Martin on 26 Jan 2010 19:49
On 01/26/2010 10:24 PM, Cor wrote:
>
>
> Some entity, AKA Martin <xtd8865(a)gmail.com>,
> wrote this mindboggling stuff:
> (selectively-snipped-or-not-p)
>
>>>>> I've just started my journey through the land of lisp (clisp) on
>>>>> Slackware64-current using Emacs + slime. I've got a few basic questions
>>>>> regarding setting up working environment. The emacs slime-mode starts
>>>>> without any errors but the key bindings seems not to work.
>
>>>> As a newcomer, you should probably do your baby steps on SBCL, CCL, or
>>>> on a commercial implementation (which tend to provide free evaluation
>>>> versions for personal use.)
>
>> It's me again. I've downloaded sbcl 1.0.34. When I run ./install.sh as
>> root, I get the following:
>>
>>> # ./install.sh
>>> src/runtime/sbcl not found, aborting installation.
>
> yeps, that is a known gotcha..
>
> But the 1.0.34 is also 32-bits only at the moment.
>
> You should get the 64-bit version 1.0.29.
> Get can the binary and install that and then recompile the source of 1.0.29
> if you want to have a processor specific implementation, or use clisp
> the 'lisp' as stated in the INSTALL file, since sbcl needs a lisp to
> compile
>
> I did the the binary-1.0.29 install here first and then recompiled the
> source here on my slackware64-13.0 on amd64 without a problem.
>
> Cor
>
>
Thanks, I just issued ./install.sh to install 1.0.29. Is it not good?

Anyway, that's what I get when pressing M-x slime in emacs:


>
> ; (SWANK-RPC::HANDLER-BIND
> ; ((SWANK-RPC::ERROR (SWANK-RPC::LAMBDA (SWANK-RPC::C) (SWANK-RPC::ERROR #))))
> ; (SWANK-RPC::LET
> ; ((SWANK-RPC::PACKET (SWANK-RPC:READ-PACKET SWANK-RPC::STREAM)))
> ; (SWANK-RPC::HANDLER-CASE
> ; (SWANK-RPC::VALUES (SWANK-RPC:READ-FORM SWANK-RPC::PACKET) SWANK-RPC::NIL)
> ; (SWANK-RPC::READER-ERROR (SWANK-RPC::C)
> ; `(:READER-ERROR ,SWANK-RPC::PACKET ,SWANK-RPC::C)))))
> ;
> ; note: The first argument never returns a value.
>
> ; (SWANK-RPC:READ-FORM SWANK-RPC::PACKET)
> ; ==>
> ; SWANK-RPC::PACKET
> ;
> ; note: deleting unreachable code
>
> ; in: DEFUN READ-PACKET
> ; ((SWANK-RPC::HEADER (SWANK-RPC:READ-CHUNK SWANK-RPC::STREAM 6))
> ; (SWANK-RPC::LENGTH (SWANK-RPC::PARSE-INTEGER SWANK-RPC::HEADER :RADIX 16))
> ; (SWANK-RPC::PAYLOAD
> ; (SWANK-RPC:READ-CHUNK SWANK-RPC::STREAM SWANK-RPC::LENGTH)))
> ;
> ; caught COMMON-LISP:ERROR:
> ; illegal function call
>
> ; (SWANK-RPC::LET*
> ; ((SWANK-RPC::HEADER (SWANK-RPC:READ-CHUNK SWANK-RPC::STREAM 6))
> ; (SWANK-RPC::LENGTH (SWANK-RPC::PARSE-INTEGER SWANK-RPC::HEADER :RADIX 16))
> ; (SWANK-RPC::PAYLOAD
> ; (SWANK-RPC:READ-CHUNK SWANK-RPC::STREAM SWANK-RPC::LENGTH)))
> ; (SWANK-RPC:LOG-EVENT "READ: ~S~%" SWANK-RPC::PAYLOAD) SWANK-RPC::PAYLOAD)
> ;
> ; note: The first argument never returns a value.
>
> ; (SWANK-RPC:LOG-EVENT "READ: ~S~%" SWANK-RPC::PAYLOAD)
> ; ==>
> ; "READ: ~S~%"
> ;
> ; note: deleting unreachable code
>
> ; in: DEFUN READ-CHUNK
> ; ((SWANK-RPC::BUFFER (SWANK-RPC::MAKE-STRING SWANK-RPC::LENGTH))
> ; (SWANK-RPC::COUNT
> ; (SWANK-RPC::READ-SEQUENCE SWANK-RPC::BUFFER SWANK-RPC::STREAM)))
> ;
> ; caught COMMON-LISP:ERROR:
> ; illegal function call
>
> ; (SWANK-RPC::LET*
> ; ((SWANK-RPC::BUFFER (SWANK-RPC::MAKE-STRING SWANK-RPC::LENGTH))
> ; (SWANK-RPC::COUNT
> ; (SWANK-RPC::READ-SEQUENCE SWANK-RPC::BUFFER SWANK-RPC::STREAM)))
> ; (SWANK-RPC::ASSERT (SWANK-RPC::= SWANK-RPC::COUNT SWANK-RPC::LENGTH) NIL
> ; "Short read: length=~D count=~D" SWANK-RPC::LENGTH SWANK-RPC::COUNT)
> ; SWANK-RPC::BUFFER)
> ;
> ; note: The first argument never returns a value.
>
> ; (SWANK-RPC::= SWANK-RPC::COUNT SWANK-RPC::LENGTH)
> ; ==>
> ; SWANK-RPC::COUNT
> ;
> ; note: deleting unreachable code
>
> ; in: DEFVAR *SWANK-IO-PACKAGE*
> ; ((SWANK-RPC::PACKAGE (SWANK-RPC::MAKE-PACKAGE :SWANK-IO-PACKAGE :USE 'NIL)))
> ;
> ; caught COMMON-LISP:ERROR:
> ; illegal function call
>
> ; (SWANK-RPC::LET
> ; ((SWANK-RPC::PACKAGE (SWANK-RPC::MAKE-PACKAGE :SWANK-IO-PACKAGE :USE 'NIL)))
> ; (SWANK-RPC::IMPORT '(SWANK-RPC::NIL SWANK-RPC::T SWANK-RPC::QUOTE)
> ; SWANK-RPC::PACKAGE)
> ; SWANK-RPC::PACKAGE)
> ;
> ; note: The first argument never returns a value.
>
> ; '(SWANK-RPC::NIL SWANK-RPC::T SWANK-RPC::QUOTE)
> ;
> ; note: deleting unreachable code
>
> ; in: DEFUN READ-FORM
> ; ((SWANK-RPC::*PACKAGE* SWANK-RPC:*SWANK-IO-PACKAGE*))
> ;
> ; caught COMMON-LISP:ERROR:
> ; illegal function call
>
> ; (SWANK-RPC::LET ((SWANK-RPC::*PACKAGE* SWANK-RPC:*SWANK-IO-PACKAGE*))
> ; (SWANK-RPC::IF SWANK-RPC::*VALIDATE-INPUT*
> ; (SWANK-RPC::WITH-INPUT-FROM-STRING
> ; (SWANK-RPC::*STANDARD-INPUT* SWANK-RPC::STRING) (SWANK-RPC::SIMPLE-READ))
> ; (SWANK-RPC::READ-FROM-STRING SWANK-RPC::STRING)))
> ;
> ; note: The first argument never returns a value.
>
> ; (SWANK-RPC::IF SWANK-RPC::*VALIDATE-INPUT*
> ; (SWANK-RPC::WITH-INPUT-FROM-STRING
> ; (SWANK-RPC::*STANDARD-INPUT* SWANK-RPC::STRING) (SWANK-RPC::SIMPLE-READ))
> ; (SWANK-RPC::READ-FROM-STRING SWANK-RPC::STRING))
> ; ==>
> ; SWANK-RPC::*VALIDATE-INPUT*
> ;
> ; note: deleting unreachable code
>
> ; in: DEFUN ENCODE-MESSAGE
> ; ((SWANK-RPC::ERROR
> ; (SWANK-RPC::LAMBDA (SWANK-RPC::C)
> ; (SWANK-RPC::ERROR (SWANK-RPC:MAKE-SWANK-PROTOCOL-ERROR SWANK-RPC::C)))))
> ;
> ; caught COMMON-LISP:ERROR:
> ; illegal function call
>
> ; ((SWANK-RPC::STRING (SWANK-RPC:PRIN1-TO-STRING-FOR-EMACS SWANK-RPC::MESSAGE))
> ; (SWANK-RPC::LENGTH (SWANK-RPC::LENGTH SWANK-RPC::STRING)))
> ;
> ; caught COMMON-LISP:ERROR:
> ; illegal function call
>
> ; ((SWANK-RPC::*PRINT-PRETTY* SWANK-RPC::NIL))
> ;
> ; caught COMMON-LISP:ERROR:
> ; illegal function call
>
> ; (SWANK-RPC::LET ((SWANK-RPC::*PRINT-PRETTY* SWANK-RPC::NIL))
> ; (SWANK-RPC::FORMAT SWANK-RPC::STREAM "~6,'0x" SWANK-RPC::LENGTH))
> ;
> ; note: The first argument never returns a value.
>
> ; (SWANK-RPC::LET*
> ; ((SWANK-RPC::STRING
> ; (SWANK-RPC:PRIN1-TO-STRING-FOR-EMACS SWANK-RPC::MESSAGE))
> ; (SWANK-RPC::LENGTH (SWANK-RPC::LENGTH SWANK-RPC::STRING)))
> ; (SWANK-RPC:LOG-EVENT "WRITE: ~A~%" SWANK-RPC::STRING)
> ; (SWANK-RPC::LET ((SWANK-RPC::*PRINT-PRETTY* SWANK-RPC::NIL))
> ; (SWANK-RPC::FORMAT SWANK-RPC::STREAM "~6,'0x" SWANK-RPC::LENGTH))
> ; (SWANK-RPC::WRITE-STRING SWANK-RPC::STRING SWANK-RPC::STREAM)
> ; (SWANK-RPC::FINISH-OUTPUT SWANK-RPC::STREAM))
> ;
> ; note: The first argument never returns a value.
>
> ; (SWANK-RPC::HANDLER-BIND
> ; ((SWANK-RPC::ERROR (SWANK-RPC::LAMBDA (SWANK-RPC::C) (SWANK-RPC::ERROR #))))
> ; (SWANK-RPC::LET*
> ; ((SWANK-RPC::STRING
> ; (SWANK-RPC:PRIN1-TO-STRING-FOR-EMACS SWANK-RPC::MESSAGE))
> ; (SWANK-RPC::LENGTH (SWANK-RPC::LENGTH SWANK-RPC::STRING)))
> ; (SWANK-RPC:LOG-EVENT "WRITE: ~A~%" SWANK-RPC::STRING)
> ; (SWANK-RPC::LET ((SWANK-RPC::*PRINT-PRETTY* SWANK-RPC::NIL))
> ; (SWANK-RPC::FORMAT SWANK-RPC::STREAM "~6,'0x" SWANK-RPC::LENGTH))
> ; (SWANK-RPC::WRITE-STRING SWANK-RPC::STRING SWANK-RPC::STREAM)
> ; (SWANK-RPC::FINISH-OUTPUT SWANK-RPC::STREAM)))
> ;
> ; note: The first argument never returns a value.
>
> ; (SWANK-RPC::FORMAT SWANK-RPC::STREAM "~6,'0x" SWANK-RPC::LENGTH)
> ; ==>
> ; SWANK-RPC::STREAM
> ;
> ; note: deleting unreachable code
>
> ; (SWANK-RPC:LOG-EVENT "WRITE: ~A~%" SWANK-RPC::STRING)
> ; ==>
> ; "WRITE: ~A~%"
> ;
> ; note: deleting unreachable code
>
> ; in: DEFUN PRIN1-TO-STRING-FOR-EMACS
> ; ((SWANK-RPC::*PRINT-CASE* :DOWNCASE)
> ; (SWANK-RPC::*PRINT-READABLY* SWANK-RPC::NIL)
> ; (SWANK-RPC::*PRINT-PRETTY* SWANK-RPC::NIL)
> ; (SWANK-RPC::*PACKAGE* SWANK-RPC:*SWANK-IO-PACKAGE*))
> ;
> ; caught COMMON-LISP:ERROR:
> ; illegal function call
>
> ; (SWANK-RPC::LET
> ; ((SWANK-RPC::*PRINT-CASE* :DOWNCASE)
> ; (SWANK-RPC::*PRINT-READABLY* SWANK-RPC::NIL)
> ; (SWANK-RPC::*PRINT-PRETTY* SWANK-RPC::NIL)
> ; (SWANK-RPC::*PACKAGE* SWANK-RPC:*SWANK-IO-PACKAGE*))
> ; (SWANK-RPC::PRIN1-TO-STRING SWANK-RPC::OBJECT))
> ;
> ; note: The first argument never returns a value.
>
> ; (SWANK-RPC::PRIN1-TO-STRING SWANK-RPC::OBJECT)
> ; ==>
> ; SWANK-RPC::OBJECT
> ;
> ; note: deleting unreachable code
>
> ; in: DEFMACRO DESTRUCTURE-CASE
> ; ((SWANK-RPC::OPERATOR (SWANK-RPC::GENSYM "op-"))
> ; (SWANK-RPC::OPERANDS (SWANK-RPC::GENSYM "rand-"))
> ; (SWANK-RPC::TMP (SWANK-RPC::GENSYM "tmp-")))
> ;
> ; caught COMMON-LISP:ERROR:
> ; illegal function call
> ;
> ; compilation unit aborted
> ; caught 1 fatal ERROR condition
> ; caught 18 ERROR conditions
> ; printed 27 notes
> ; compilation aborted after 0:00:00.133
> ;;
> ;; Error while loading: /home/martin/.slime/fasl/2010-01-14/sbcl-1.0.29-linux-x86-64/swank-rpc.fasl
> ;; Condition: The value SWANK-RPC::BODY is not of type LIST.
> ;; Aborting.
> ;; *



--
regards

Martin
From: Cor on 26 Jan 2010 21:26
Some entity, AKA Martin <xtd8865(a)gmail.com>,
wrote this mindboggling stuff:
(selectively-snipped-or-not-p)

> On 01/26/2010 10:24 PM, Cor wrote:
>>
>>
>> Some entity, AKA Martin <xtd8865(a)gmail.com>,
>> wrote this mindboggling stuff:
>> (selectively-snipped-or-not-p)
>>
>>>>>> I've just started my journey through the land of lisp (clisp) on
>>>>>> Slackware64-current using Emacs + slime. I've got a few basic questions
>>>>>> regarding setting up working environment. The emacs slime-mode starts
>>>>>> without any errors but the key bindings seems not to work.
>>
>>>>> As a newcomer, you should probably do your baby steps on SBCL, CCL, or
>>>>> on a commercial implementation (which tend to provide free evaluation
>>>>> versions for personal use.)
>>
>>> It's me again. I've downloaded sbcl 1.0.34. When I run ./install.sh as
>>> root, I get the following:
>>>
>>>> # ./install.sh
>>>> src/runtime/sbcl not found, aborting installation.
>>
>> yeps, that is a known gotcha..
>>
>> But the 1.0.34 is also 32-bits only at the moment.
>>
>> You should get the 64-bit version 1.0.29.
>> Get can the binary and install that and then recompile the source of 1.0.29
>> if you want to have a processor specific implementation, or use clisp
>> the 'lisp' as stated in the INSTALL file, since sbcl needs a lisp to
>> compile
>>
>> I did the the binary-1.0.29 install here first and then recompiled the
>> source here on my slackware64-13.0 on amd64 without a problem.
>>
>> Cor
>>
>>
> Thanks, I just issued ./install.sh to install 1.0.29. Is it not good?
>
> Anyway, that's what I get when pressing M-x slime in emacs:
>
>
>>
>> ; (SWANK-RPC::HANDLER-BIND
>> ; ((SWANK-RPC::ERROR (SWANK-RPC::LAMBDA (SWANK-RPC::C) (SWANK-RPC::ERROR #))))
[ snipped ]
>> ;; Error while loading: /home/martin/.slime/fasl/2010-01-14/sbcl-1.0.29-linux-x86-64/swank-rpc.fasl
>> ;; Condition: The value SWANK-RPC::BODY is not of type LIST.
>> ;; Aborting.
>> ;; *


I think it's the slime version I use the snapshot version jan 19 2010,
which has a refactored rpc module in slime.lisp

which was not yet done in the jan 14 2010 version of slime cfm the Changelog.


Cor


--
I never threathen but merely state the consequences of your choice.
The other cheek is a .40 JHP
http://www.clsnet.nl

From: Martin on 27 Jan 2010 14:21
On 01/27/2010 02:26 AM, Cor wrote:
> Some entity, AKA Martin <xtd8865(a)gmail.com>,
> wrote this mindboggling stuff:
> (selectively-snipped-or-not-p)
>
>> On 01/26/2010 10:24 PM, Cor wrote:
>>>
>>>
>>> Some entity, AKA Martin <xtd8865(a)gmail.com>,
>>> wrote this mindboggling stuff:
>>> (selectively-snipped-or-not-p)
>>>
>>>>>>> I've just started my journey through the land of lisp (clisp) on
>>>>>>> Slackware64-current using Emacs + slime. I've got a few basic questions
>>>>>>> regarding setting up working environment. The emacs slime-mode starts
>>>>>>> without any errors but the key bindings seems not to work.
>>>
>>>>>> As a newcomer, you should probably do your baby steps on SBCL, CCL, or
>>>>>> on a commercial implementation (which tend to provide free evaluation
>>>>>> versions for personal use.)
>>>
>>>> It's me again. I've downloaded sbcl 1.0.34. When I run ./install.sh as
>>>> root, I get the following:
>>>>
>>>>> # ./install.sh
>>>>> src/runtime/sbcl not found, aborting installation.
>>>
>>> yeps, that is a known gotcha..
>>>
>>> But the 1.0.34 is also 32-bits only at the moment.
>>>
>>> You should get the 64-bit version 1.0.29.
>>> Get can the binary and install that and then recompile the source of 1.0.29
>>> if you want to have a processor specific implementation, or use clisp
>>> the 'lisp' as stated in the INSTALL file, since sbcl needs a lisp to
>>> compile
>>>
>>> I did the the binary-1.0.29 install here first and then recompiled the
>>> source here on my slackware64-13.0 on amd64 without a problem.
>>>
>>> Cor
>>>
>>>
>> Thanks, I just issued ./install.sh to install 1.0.29. Is it not good?
>>
>> Anyway, that's what I get when pressing M-x slime in emacs:
>>
>>
>>>
>>> ; (SWANK-RPC::HANDLER-BIND
>>> ; ((SWANK-RPC::ERROR (SWANK-RPC::LAMBDA (SWANK-RPC::C) (SWANK-RPC::ERROR #))))
> [ snipped ]
>>> ;; Error while loading: /home/martin/.slime/fasl/2010-01-14/sbcl-1.0.29-linux-x86-64/swank-rpc.fasl
>>> ;; Condition: The value SWANK-RPC::BODY is not of type LIST.
>>> ;; Aborting.
>>> ;; *
>
>
> I think it's the slime version I use the snapshot version jan 19 2010,
> which has a refactored rpc module in slime.lisp
>
> which was not yet done in the jan 14 2010 version of slime cfm the Changelog.
>
>
> Cor
>
>
Yeah, that was slime. I updated it and it loads nicely
thanks
regards
martin

--
regards

Martin
First  |  Prev  | 
Pages: 1 2 3 4 5
Prev: How do I go from a variable name literal to the variable itself?
Next: Lisp packaging and version management..