[STUMP] Re: Stumpwm-devel Digest, Vol 54, Issue 13

[gzeus]

That's all that make spits out.
If I try with SBCL, it can't find CLX, and gives me options that don't work, or 
wouldn't result in a usable image.
Do you know where those fasls are stored?
/var/cache/common-lisp-controller/* is all asdf and common-lisp-controller.
cleaning those out, and dpkg-reconfigure-ing them to rebuild them didn't help.
I filed a bug against common-lisp-controller, but it might be asdf, but the way 
those work together it could be either with my level of knowledge and the free 
implementations' debuggers...
> Date: Fri, 11 Sep 2009 21:09:56 -0400
> From: Shawn Betts <address@hidden>
> Subject: Re: [STUMP] Re: Make failure
> To: StumpWM-devel <address@hidden>
> Message-ID:
>       <address@hidden>
> Content-Type: text/plain; charset=ISO-8859-1

> On Fri, Sep 11, 2009 at 7:58 PM, gzeus <address@hidden> wrote:
> > Well, all I did was make clean; make and boom, that's what I get.

> I know that much :). What i'd like to see is enough of the surrounding
> text to understand what file or module is being compiled. It looks
> like maybe it's asdf but if you upgraded who knows what it is. The
> whole output from $ make would probably be best.

> Also, because of debian's common-lisp-controller obfuscation, make
> clean probably does nothing because the compiled lisp files are stored
> in /way/the/fuck/over/there/. You may need to clean that dir out.

> -Shawn