From: Trastabuga
Subject: fasl files generated by SBCL
Date: Sat, 19 Apr 2008 13:22:26 +0000
Message-ID: <d9ac42e4-151e-49e0-bf9e-db563e240606@t54g2000hsg.googlegroups.com>

I used to have sblc 1.0.6 which comes with the installation package on
Ubuntu.
When I was using it somehow it didn't generate the *.fasl file after
the compilation.
Now that I compiled the lates 1.0.15, I started to get those fasl
files all over the place.
I wonder why I didn't have them with 1.0.6 and is there a way to not
have them with 1.0.15?

Thank you!

• Re: fasl files generated by SBCL ···············@gmail.com
  • Re: fasl files generated by SBCL Matthias Benkard

From: ···············@gmail.com
Subject: Re: fasl files generated by SBCL
Date: Sat, 19 Apr 2008 14:28:51 +0000
Message-ID: <256547b7-3bfe-4f54-a7d0-2cd727c48fc5@d45g2000hsc.googlegroups.com>

On Apr 19, 2:22 pm, Trastabuga <·········@gmail.com> wrote:
> I used to have sblc 1.0.6 which comes with the installation package on
> Ubuntu.
> When I was using it somehow it didn't generate the *.fasl file after
> the compilation.
> Now that I compiled the lates 1.0.15, I started to get those fasl
> files all over the place.
> I wonder why I didn't have them with 1.0.6 and is there a way to not
> have them with 1.0.15?
>
> Thank you!

The official Ubuntu one is probably using COMMON-LISP-CONTROLLER which
will be putting the fasl files somewhere under a sub-directory of /var/
cache/common-lisp-controller/. But the one you've downloaded yourself
will not be using this and creating the fasl files locally.

--
Phil
http://phil.nullable.eu/

From: Matthias Benkard
Subject: Re: fasl files generated by SBCL
Date: Sat, 19 Apr 2008 15:41:55 +0000
Message-ID: <42f568a4-d2fb-4e00-966a-cdf1e20a6432@c58g2000hsc.googlegroups.com>

On 19 Apr., 16:28, ···············@gmail.com wrote:
> The official Ubuntu one is probably using COMMON-LISP-CONTROLLER which
> will be putting the fasl files somewhere under a sub-directory of /var/
> cache/common-lisp-controller/. But the one you've downloaded yourself
> will not be using this and creating the fasl files locally.

Right.

If you want to use the CLC from within a locally installed version of
SBCL, you can put something like the following into your .sbclrc:

  (load "/usr/share/common-lisp/source/common-lisp-controller/common-
lisp-controller.lisp")
  (load "/usr/share/common-lisp/source/common-lisp-controller/post-
sysdef-install.lisp")
  (funcall (intern "INIT-COMMON-LISP-CONTROLLER-V5"
                   (find-package '#:common-lisp-controller))
           "sbcl")

Something similar works for lots of Lisp implementations, even some of
the ones that aren't Debian-packaged in any way.  (For others, you may
need to define CLC::GET-UID before calling CLC::INIT-COMMON-LISP-
CONTROLLER-V5.  If someone's interested, I can post my ad-hoc
definitions for LispWorks and ECL here.)

As an alternative, there's ASDF-Binary-Locations, which I use on all
my non-Debian systems: http://common-lisp.net/project/cl-containers/asdf-binary-locations/

~ Matthias