[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [STUMP] Building with CLISP
From: |
Dirk Sondermann |
Subject: |
Re: [STUMP] Building with CLISP |
Date: |
Sun, 07 Aug 2011 02:45:37 +0200 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110709 Lightning/1.0b3pre Thunderbird/3.1.10 |
On 08/06/11 04:08, Aidan Gauland wrote:
> On 31/07/11 23:31, Dirk Sondermann wrote:
>> The problem is that ASDF tries to store compiled fasl files in the
>> same directories where it has found the lisp sources. Since you
>> don't have write permissions on those directories, compiling the first
>> lisp file in /usr/share/common-lisp/source/cl-ppcre leads to an error.
>> There are several ways to avoid this problem. You could, for example,
>> use debian's ASDF infrastructure instead of the asdf.lisp that is
>> included in stumpwm.
>
> How do I tell the build system to use Debian's ASDF package instead of
> the bundles version?
As I'm not a Debian user, I'm probably not the right person to answer
this question.
I suppose that the Common Lisp Controler is the recommended tool to be
used (http://pkg-common-lisp.alioth.debian.org/clid/clid.html), but for
our purposes it should suffice to replace the asdf.lisp file included in
stumpwm with a link to /usr/share/common-lisp/source/cl-asdf/asdf.lisp
(which is part of the package cl-asdf).
As long as no particular mapping rules have been defined, ASDF now saves
fasl files under ~/.cache/common-lisp, where you have write permissions.
--
Dirk