From: Mehul S. <meh...@gm...> - 2013-07-03 18:47:21
|
Debian no longer provides a full linkset. Most things are provided as modules in separate directories under /usr/lib/clisp-2.49. How do I get the modules, like clx/new-clx to load ? Would it be easier to make a linkset ? How do I go about doing that ? cheers, mehul -- Mehul N. Sanghvi email: meh...@gm... |
From: Pascal J. B. <pj...@in...> - 2013-07-04 18:58:23
|
Mehul Sanghvi <meh...@gm...> writes: > Debian no longer provides a full linkset. Most things are provided as > modules in separate directories under /usr/lib/clisp-2.49. > > > How do I get the modules, like clx/new-clx to load ? Would it be easier > to make a linkset ? How do I go about doing that ? That's clisp-2.49. Now all the modules are dynamically loadable. So you just (require "clx") to get it. Be sure to install all the modules: apt-get install $(apt-cache search clisp|sed -e 's/ - .*//') -- __Pascal Bourguignon__ http://www.informatimago.com/ A bad day in () is better than a good day in {}. You know you've been lisping too long when you see a recent picture of George Lucas and think "Wait, I thought John McCarthy was dead!" -- Dalek_Baldwin |
From: Mehul S. <meh...@gm...> - 2013-07-04 19:47:24
|
On Thu, Jul 4, 2013 at 2:57 PM, Pascal J. Bourguignon <pj...@in... > wrote: > Mehul Sanghvi <meh...@gm...> writes: > > > Debian no longer provides a full linkset. Most things are provided as > > modules in separate directories under /usr/lib/clisp-2.49. > > > > > > How do I get the modules, like clx/new-clx to load ? Would it be > easier > > to make a linkset ? How do I go about doing that ? > > That's clisp-2.49. Now all the modules are dynamically loadable. So you > just (require "clx") to get it. > > Be sure to install all the modules: > > apt-get install $(apt-cache search clisp|sed -e 's/ - .*//') > > That is what I've done for stumpwm. In the make-image.lisp file, I've put (require "clx") for clisp. But it doesn't seem to be having any effect. I still get an error when building stumpwm: ;; Compiling file /usr/local/src/stumpwm/primitives.lisp ... *** - READ from #<INPUT BUFFERED FILE-STREAM CHARACTER #P"/usr/local/src/stumpwm/primitives.lisp" @645>: there is no package with name "XLIB" Here is how it is being invoked: /usr/bin/clisp -K full -on-error exit < ./make-image.lisp and in make-image.lisp: #+clisp (require "clx") (ext:saveinitmem "stumpwm" :init-function (lambda () (stumpwm:stumpwm) (ext:quit)) :executable t :keep-global-handlers t :norc t :documentation "The StumpWM Executable") Any thoughts or suggestions ? -- Mehul N. Sanghvi email: meh...@gm... |
From: Pascal J. B. <pj...@in...> - 2013-07-04 20:23:00
|
Mehul Sanghvi <meh...@gm...> writes: > That is what I've done for stumpwm. In the make-image.lisp file, I've > put (require "clx") > for clisp. But it doesn't seem to be having any effect. I still get > an error when building > stumpwm: > > > ;; Compiling file /usr/local/src/stumpwm/primitives.lisp ... > *** - READ from #<INPUT BUFFERED FILE-STREAM CHARACTER > #P"/usr/local/src/stumpwm/primitives.lisp" @645>: there is no package > with name "XLIB" > > > > Here is how it is being invoked: > > /usr/bin/clisp -K full -on-error exit < ./make-image.lisp > > > and in make-image.lisp: > > #+clisp > (require "clx") > (ext:saveinitmem "stumpwm" :init-function (lambda () When compiling, perhaps: (eval-when (:compile-toplevel :load-toplevel :execute) (require "clx")) ? -- __Pascal Bourguignon__ http://www.informatimago.com/ A bad day in () is better than a good day in {}. You know you've been lisping too long when you see a recent picture of George Lucas and think "Wait, I thought John McCarthy was dead!" -- Dalek_Baldwin |