'clisp -C' causes "LOAD: A file with name ASDF does not exist" error

[Mikey]

Hello,

I use clisp 2.49 on Slackware Linux 13.37. Executing 'clisp -C' (this
option enables 'compile when loading' feature) causes following error:

;; Loading file /home/mikey/.clisprc.lisp ...
;; Loading file /home/mikey/quicklisp/setup.lisp ...
*** - LOAD: A file with name ASDF does not exist
The following restarts are available:
SKIP :R1 skip (DEFUN ENSURE-ASDF-LOADED NIL ...)
RETRY :R2 retry (DEFUN ENSURE-ASDF-LOADED NIL ...)
STOP :R3 stop loading file /home/mikey/quicklisp/
setup.lisp
SKIP :R4 skip (LET # #)
RETRY :R5 retry (LET # #)
STOP :R6 stop loading file /home/mikey/.clisprc.lisp

The problem doesn't occur with 'clisp' i.e. clisp without any command
line options. What's more interesting 'clisp' and 'clisp -C' on my
Windows Vista SP1 works fine too. Any ideas?

[Zach Beane]

That's interesting, I get the same error too.

I think this is a bug in CLISP. First, create a file named
"clisptest.lisp" with this in it:

(require 'asdf)

If you (compile-file "clisptest.lisp"), you get an error, but you
shouldn't get that kind of error at compile time; CL:REQUIRE is a
function, and should only have an effect at load time.

I'll report this on the CLISP bug tracker today.

Zach

[Zach Beane]

I reported the bug
(https://sourceforge.net/tracker/?func=detail&aid=3525509&group_id=1355&atid=101355)
but then I read the manual and saw that this behavior is specified
there.

I think your only option, if you continue to use CLISP, will be to omit
"-C".

Zach

[Mikey]

Thank you for explanation. It seems I will have to settle for (load
"filename" :compiling T) instead of 'clisp -C'.

[Pascal J. Bourguignon]

Mikey <smiec...@gmail.com> writes:

> Thank you for explanation. It seems I will have to settle for (load
> "filename" :compiling T) instead of 'clisp -C'.

The standard way is:

(load (compile-file "file.lisp"))

Why use a non-standard extension when there's a perfectly good standard
way to do it?

--
__Pascal Bourguignon__ http://www.informatimago.com/
A bad day in () is better than a good day in {}.

[Mikey]

Pascal J. Bourguignon wrote:
> The standard way is:
>
> (load (compile-file "file.lisp"))
>
> Why use a non-standard extension when there's a perfectly good standard
> way to do it?

To avoid creating useless (in this specific case) .fas file.

[Mikey]

Zach Beane wrote:
> I reported the bug
> (https://sourceforge.net/tracker/?func=detail&aid=3525509&group_id=1355&atid=101355)
> but then I read the manual and saw that this behavior is specified
> there.

One thing was haunting me. Why 'clisp -C' causes error on Linux but
not on Windows, since described behaviour is specified in
documentation? Finally I found the answer: Windows filesystem isn't
case sensitive. I've changed the name of ~/quicklisp/asdf.lisp file to
~/quicklisp/ASDF.lisp and now everything works fine.