Search the Community
Showing results for tags 'quicklisp'.
Found 4 results
Dear all, After updating to a recent Opusmodus version 1.3, I ran into some errors when loading code that had been loaded and compiled before, e.g., quicklisp, quicklisp libraries, swank (the interface that allows using Emacs Slime with Opusmodus), and my own Lisp libraries. The errors I saw were rather cryptic, like the following: Error: The value "CL" is not of the expected type list. While executing: (:internal ccl::operation-on-all-specs ccl::%define-package), in process Listener-1(7). After exchanges with Janusz (thanks a lot for your help!) I learnt that the underlying Common Lisp version of Opusmodus had been upgraded to CCL version 1.12, and the format of compiled files (fasl files or dx64fsl files) of this version had changed. So, in case you run into similar problems, these can be fixed simply by deleting all previously compiled files (which Lisp stores if they do not change to speed up the load process), so that the Lisp compiler has to compile them again. In the folder ~/.cache/common-lisp just delete any folders starting with ccl-, so that all compiled files in this directory are compiled again. Best, Torsten
Hi, I know support for quicklisp is not expected of this forum, but in case someone has found a fix, I would appreciate the insight. I installed quicklisp without any problem. But when I try to install "drakma" library (via console), I am getting this error: -------------- ? (ql:quickload "drakma") To load "drakma": Load 1 ASDF system: drakma ; Loading "drakma" Read error between positions 66 and 163 in /Users/Rangarajan/quicklisp/dists/quicklisp/software/usocket-0.6.3.2/backend/openmcl.lisp. > Error: Foreign function not found: x86-darwin64::|gethostname| > While executing: ccl::load-external-function, in process Listener-1(7). > Type cmd-. to abort, cmd-\ for a list of available restarts. > Type :? for other options. --------------- Regards, Rangarajan
Following from this question, I want to use several different Lisp packages through quicklisp, but I can't get the installation to work correctly. After doing some digging, I found out that the path to quicklisp is not defined correctly. This is the content of the ql:*quicklisp-home* global: > ql:*quicklisp-home* #P"/Users/opusmodus/quicklisp/" I realised that changing this manually doesn't fix the issue, and because of this I can't install or use quicklisp correctly. Note that I do not have a user by the name opusmodus and creating that directory with my user's permission does not fix it. I managed to do something by using SBCL as my own user to load and install quicklisp, and then in opusmodus use the following: (load #p"/Users/ajf-/quicklisp/setup.lisp") But it's actually a workaround and it's not very reliable (also gives an error sometimes). Can you please point me in the right direction? Thank you very much
For programmers and developers Install the Quicklisp beta library manager. Evaluate: (load "http://beta.quicklisp.org/quicklisp.lisp") To continue, evaluate: (quicklisp-quickstart:install) Place the attached file 'Quicklisp Start.lisp' file into your ~/Opusmodus/Extensions folder. Edit the file and add the libraries you like to load. Example: (ql:quickload "ieee-floats") (ql:quickload "osc") About Quicklisp Beta Note: Opusmodus has its own init file and is not loading the ccl.init.lisp file at the start. Quicklisp installation and its use is not a part of the Opusmodus support. This post is mainly for programmers and developers that already know how to use the Quicklisp libraries. Additional installation: Post from Bill St. Clair: # In a shell cd mkdir ccl cd ccl svn co http://svn.clozure.com/publicsvn/openmcl//release/1.11/darwin-x86-headers64 Quicklisp Start.lisp