ASDF could not load sb-bsd-sockets because

[TonyT...@yahoo.com]

Hey,

I am completly new to CL so please bear with me.
I have many machines which I would like to keep in sync with an up-to-
date QuickLisp installation. To do so, I created the following script:

#!/bin/bash
set -e
if [ ! -f /usr/local/src/quicklisp/quicklisp.lisp ]
then
mkdir -p /usr/local/src/quicklisp
wget -O - http://beta.quicklisp.org/quicklisp.lisp > /usr/local/src/
quicklisp/quicklisp.lisp
fi
echo '(quicklisp-quickstart:install :path ".quicklisp/")
(ql:update-client)
(ql:add-to-init-file)
(ql:update-all-dists)
(quit)' | sbcl --noinform --load /usr/local/src/quicklisp/
quicklisp.lisp

That should install/update quicklisp, shouldn't it?

Unfortunately I get a strange error whenever I run the script:

(/usr/local/pkg/sbcl-1.0.55/lib/sbcl/sb-bsd-sockets/constants.lisp
/home/tony/.cache/common-lisp/sbcl-1.0.55-linux-x64/usr/local/pkg/
sbcl-1.0.55/lib/sbcl/sb-bsd-sockets/constants.fasl
/home/tony/.cache/common-lisp/sbcl-1.0.55-linux-x64/usr/local/pkg/
sbcl-1.0.55/lib/sbcl/sb-bsd-sockets/constants.fasl
/home/tony/.cache/common-lisp/sbcl-1.0.55-linux-x64/usr/local/pkg/
sbcl-1.0.55/lib/sbcl/sb-bsd-sockets/foo.c
/home/tony/.cache/common-lisp/sbcl-1.0.55-linux-x64/usr/local/pkg/
sbcl-1.0.55/lib/sbcl/sb-bsd-sockets/a.out
/home/tony/.cache/common-lisp/sbcl-1.0.55-linux-x64/usr/local/pkg/
sbcl-1.0.55/lib/sbcl/sb-bsd-sockets/constants.lisp-temp)
ASDF could not load sb-bsd-sockets because
failed to find the TRUENAME of /home/tony/.cache/common-lisp/
sbcl-1.0.55-linux-x64/usr/local/pkg/sbcl-1.0.55/lib/sbcl/sb-bsd-
sockets/constants.lisp-temp:
No such file or directory.

debugger invoked on a SB-INT:SIMPLE-FILE-ERROR in thread
#<THREAD "initial thread" RUNNING {10029616A3}>:
failed to find the TRUENAME of /home/tony/.cache/common-lisp/
sbcl-1.0.55-linux-x64/usr/local/pkg/sbcl-1.0.55/lib/sbcl/sb-bsd-
sockets/constants.lisp-temp:
No such file or directory

Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.

restarts (invokable by number or by possibly-abbreviated name):
0: [RETRY ] Retry
compiling #<GROVEL-CONSTANTS-FILE "sb-bsd-sockets"
"constants">.
1: [ACCEPT ] Continue, treating
compiling #<GROVEL-CONSTANTS-FILE "sb-bsd-sockets"
"constants">
as having been successful.
2: [RETRY ] Retry EVAL of current toplevel form.
3: [CONTINUE] Ignore error and continue loading file "/usr/local/src/
quicklisp/quicklisp.lisp".
4: [ABORT ] Abort loading file "/usr/local/src/quicklisp/
quicklisp.lisp".
5: Ignore runtime option --load "/usr/local/src/quicklisp/
quicklisp.lisp".
6: Skip rest of --eval and --load options.
7: Skip to toplevel READ/EVAL/PRINT loop.
8: [QUIT ] Quit SBCL (calling #'QUIT, killing the process).

(SB-IMPL::SIMPLE-FILE-PERROR
"failed to find the TRUENAME of ~A"
#P"/home/tony/.cache/common-lisp/sbcl-1.0.55-linux-x64/usr/local/pkg/
sbcl-1.0.55/lib/sbcl/sb-bsd-sockets/constants.lisp-temp"
2)
0]

What did I do wrong?

[Zach Beane]

TonyT...@yahoo.com writes:

[snip]

>
> That should install/update quicklisp, shouldn't it?

The script looks ok to me.

> Unfortunately I get a strange error whenever I run the script:
>
> (/usr/local/pkg/sbcl-1.0.55/lib/sbcl/sb-bsd-sockets/constants.lisp

[snip]

What created that unusual directory structure? Normally sbcl goes in
something like /usr/local/bin/sbcl, /usr/local/lib/sbcl/, etc.

If you run sbcl from the command line, can you (require 'sb-bsd-sockets)
without an error?

Zach

[TonyT...@yahoo.com]

On Feb 13, 6:49 pm, Zach Beane <x...@xach.com> wrote:

> TonyTLip...75@yahoo.com writes:
>
> [snip]
>
>
>
> > That should install/update quicklisp, shouldn't it?
>
> The script looks ok to me.
>
> > Unfortunately I get a strange error whenever I run the script:
>
> > (/usr/local/pkg/sbcl-1.0.55/lib/sbcl/sb-bsd-sockets/constants.lisp
>
> [snip]
>
> What created that unusual directory structure? Normally sbcl goes in
> something like /usr/local/bin/sbcl, /usr/local/lib/sbcl/, etc.

I always install packages in the pkg-subdir of /usr/local . A script
automatically symlinks all files to /usr/local/xxx . That way I can
easily uninstall a package by deleting the directory in /usr/local/pkg
and delete all symlinks with no valid targets. So far every package I
built (emacs, gcc, gdb, etc.) worked fine this way :\

> If you run sbcl from the command line, can you (require 'sb-bsd-sockets)
> without an error?

Arg, no, I cannot. Same error.

[Zach Beane]

TonyT...@yahoo.com writes:

> I always install packages in the pkg-subdir of /usr/local . A script
> automatically symlinks all files to /usr/local/xxx . That way I can
> easily uninstall a package by deleting the directory in /usr/local/pkg
> and delete all symlinks with no valid targets. So far every package I
> built (emacs, gcc, gdb, etc.) worked fine this way :\
>
>> If you run sbcl from the command line, can you (require 'sb-bsd-sockets)
>> without an error?
>
> Arg, no, I cannot. Same error.

That's a tip that SBCL is incompletely installed in some way, but I'm
afraid I'm not sure how you can fix it, sorry.

Zach

[TonyT...@yahoo.com]

On Feb 13, 7:00 pm, Zach Beane <x...@xach.com> wrote:

I did not export SBCL_HOME. I think it is working fine :)

Thank you so much for your Help!