2011/5/10 José María García Pérez <josemaria.alkala@...>:
(Moving to sbcl-help.)
> I am trying to produce a package for StumpWM for TinyCoreLinux. So please,
> bear in mind I am not a Lisp user. To compile it, I first need to have
> "sbcl" working in the distribution. I have tried the existing "sbcl" package
> which doesn't seem to work. I have created a new one based on the binary
> Then I tried to download the "clx" package by executing:
> $ sbcl
> * (require 'asdf)
> * (asdf:oos 'asdf:load-op :asdf-install)
> * (asdf-install:install 'clx)
> But there seem to be lot of problems when I execute: (asdf:oos 'asdf:load-op
> Could somebody help me to find what I am doing wrong?
Without any more details as to what goes wrong it's hard to say.
However, ASDF-INSTALL as an installation mechanism leaves a lot to be
desired. (It's defects are too numerous to fit into this metaphorical
margin, and besides the point.)
You might have better luck using Quicklisp -- which is pretty much the
successor of CLX.
sbcl --load quicklisp.lisp
# follow prompts, then new a new SBCL session
2011/5/11 José María García Pérez <josemaria.alkala@...>:
> tc@...:/tmp$ sbcl --load quicklisp.lisp > build.log
> ASDF could not load sb-bsd-sockets because failed to find the TRUENAME of
> No such file or directory.
I'm betting the same happens if you do just
Something is messed up in the environment or the installation: all
sb-bsd-sockets related files should be built by make.sh and installed
into /usr/local/lib/sbcl/.. by install.sh.
>From the error it looks like that has happened, but something is causing
the system to think they need to be recompiled ... and badness happens.
My first thought is that something is funny about the timestamps.
return? The numbers should be in increasing order.