LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 04-10-2018, 08:50 AM   #1
badbetty
Member
 
Registered: Jan 2014
Posts: 141

Rep: Reputation: Disabled
Follow on re: CLISP re-build using current - does CLISP on current work with quicklisp ?


Previous question which I suppose this follows on from:
https://www.linuxquestions.org/quest...lt-4175627295/


Following drmozes' helpful contribution, I did indeed build clisp from the link provided.

Although once installed it started up, it seemed to struggle with 'quicklisp', which was already installed against the previous clisp, by throwing a few errors about missing items - I can attach the messages if required, but see my question below please.

I removed that updated clisp and quicklisp and anything connected and reinstalled the updated clisp. Then I tried to load quicklisp against it following the instructions, but again there were errors of missing symbols.

Going back to the original clisp as packaged in slackware, everything worked fine with regard to quicklisp.

My question is, for those that have worked with/amended the clisp package on 'current' (32 or 64 bit), has anyone or is anyone running clisp with quicklisp without issue ?

Thank you for an indication on the above as a starter for me.
Habs
 
Old 04-10-2018, 09:56 AM   #2
elcore
Member
 
Registered: Sep 2014
Distribution: Slackware
Posts: 668

Rep: Reputation: Disabled
Not using any of these here, but your broken package most certainly is linked to the old version of the package you upgraded.
So you may want to recompile the broken package, after upgrading the package it depends on.
 
Old 04-11-2018, 04:09 AM   #3
badbetty
Member
 
Registered: Jan 2014
Posts: 141

Original Poster
Rep: Reputation: Disabled
@elcore - as mentioned in my OP, I thought I had removed all references and started 'clean' as such - or as best I can tell.

It did not make any difference. I suspect it is a 'quicklisp' [compatibility with CLISP] error (not sure).

From a running clisp built from 'current' (and following download of quicklisp.lisp), evaluating '(load "quicklisp.lisp")' and then '(quicklisp-quickstart:install)', eventually delivers the following:

DEFPACKAGE QL-CLISP: There is no symbol EXT:ELETE-DIR .

If you continue (by typing 'continue'): This symbol will be created.
The following restarts are also available:
RETRY :R1 Retry compiling #<CL-SOURCE-FILE "quicklisp" "impl">.
ACCEPT :R2 Continue, treating compiling #<CL-SOURCE-FILE "quicklisp" "impl"> as having been successful.
SKIP :R3 skip (LET # #)
RETRY :R4 retry (LET # #)
STOP :R5 stop loading file /home/bch-slack142/quicklisp/setup.lisp
ABORT :R6 Abort main loop
Break 1 QL-IMPL[3]> continue

That's why I was wanting to know if anyone building/maintaining/using clisp from current and using quicklisp was doing so without any issues.

I'm just a beginner with lisp/clisp, so I'm going to be a bit unhelpful to start with. I will refer the error to the quicklisp discussion group for ideas as it looks like a quicklisp compatibility [to CLISP] related error, in my ignorance.

Of course, if I revert pack to the packaged clisp version (rather than using 'current'), all this seems to go away :-)

Thank you.
Habs
 
Old 04-11-2018, 06:46 AM   #4
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 7,101

Rep: Reputation: 4772Reputation: 4772Reputation: 4772Reputation: 4772Reputation: 4772Reputation: 4772Reputation: 4772Reputation: 4772Reputation: 4772Reputation: 4772Reputation: 4772
It looks like quicklisp was last released in 2010, so it is very possible it is just too old to run on this newer version of clisp.
 
Old 04-11-2018, 10:56 AM   #5
Myk267
Member
 
Registered: Apr 2012
Location: California
Posts: 422
Blog Entries: 16

Rep: Reputation: Disabled
I fixed it. Now all you have to do is hop on over and use my computer.

Last edited by Myk267; 04-11-2018 at 10:59 AM.
 
Old 04-11-2018, 11:09 AM   #6
badbetty
Member
 
Registered: Jan 2014
Posts: 141

Original Poster
Rep: Reputation: Disabled
@myk267 - if you have, there doesn't appear to be any useful detail of what you did - unless that was deliberate :-)
 
Old 04-11-2018, 11:47 AM   #7
Myk267
Member
 
Registered: Apr 2012
Location: California
Posts: 422
Blog Entries: 16

Rep: Reputation: Disabled
Quote:
Originally Posted by badbetty View Post
@myk267 - if you have, there doesn't appear to be any useful detail of what you did - unless that was deliberate :-)
Sorry, my brain is still booting up.

Here's what to do:
Type "continue" each time quicklisp warns about the missing symbols and install it like normal.
cd to your quicklisp directory, probably $HOME/quicklisp
Download this patchfile I've atttached, then use patch, ex:
Code:
patch -p1 < ~/path/to/ql-patchfile.txt
And then try out quicklisp and report any news.
Attached Files
File Type: txt ql-patchfile.txt (883 Bytes, 34 views)
 
1 members found this post helpful.
Old 04-11-2018, 12:39 PM   #8
badbetty
Member
 
Registered: Jan 2014
Posts: 141

Original Poster
Rep: Reputation: Disabled
@myk267 thank you for coming back on this. I'll come back with the results soonest. Thank you again.
 
Old 04-11-2018, 01:36 PM   #9
badbetty
Member
 
Registered: Jan 2014
Posts: 141

Original Poster
Rep: Reputation: Disabled
@myk267 - That seems to have removed errors. The patch changes some exported functions (if I'm correct) in the respective quicklisp files.

Do you know the cause of requiring a manual patch ?

e.g. is it just down to things moving on as such and function names getting changed.

Regards
Habs
 
Old 04-11-2018, 02:42 PM   #10
Myk267
Member
 
Registered: Apr 2012
Location: California
Posts: 422
Blog Entries: 16

Rep: Reputation: Disabled
Quote:
Originally Posted by badbetty View Post
@myk267 - That seems to have removed errors. The patch changes some exported functions (if I'm correct) in the respective quicklisp files.

Do you know the cause of requiring a manual patch ?

e.g. is it just down to things moving on as such and function names getting changed.

Regards
Habs
It looks like they finally removed some deprecated functions.

You can read about all the changes in:
/usr/doc/clisp-2.49.20180203.ca011c249da5/NEWS
But here's the relevant text, anyway:
Quote:
* Some old functions that have been deprecated for 10+ years have been removed:
SOCKET-SERVER-PORT: use SERVICE instead,
TYPE-EXPAND-1: use TYPE-EXPAND instead,
FOREIGN-ADDRESS-NULL: use NULL instead,
DELETE-DIR: use DELETE-DIRECTORY instead,
MAKE-DIR: use MAKE-DIRECTORY instead,
RENAME-DIR: use RENAME-DIRECTORY instead.
 
Old 04-11-2018, 02:47 PM   #11
badbetty
Member
 
Registered: Jan 2014
Posts: 141

Original Poster
Rep: Reputation: Disabled
Many thanks for your help - very much appreciated.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Clisp, Clojure or haskell. jokar.mohsen Programming 1 04-05-2013 11:21 AM
Installing clisp from source Jeff91 Linux - General 14 01-10-2010 04:40 PM
Trying out CLISP. zaxonus Programming 2 08-06-2008 12:17 AM
clisp and libsigsegv trainee Slackware 0 12-24-2005 10:52 AM
A Clisp probelm keyboard Programming 7 12-01-2005 06:15 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 04:05 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration