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

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.

@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

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.

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

@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:
And then try out quicklisp and report any news.

Attached Files

ql-patchfile.txt (883 Bytes, 41 views)

1 members found this post helpful.

@myk267 thank you for coming back on this. I'll come back with the results soonest. Thank you again.

@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:

Many thanks for your help - very much appreciated.