"VAUCHER Laurent" <VAUCHER@...> writes:
> I've just downloaded the installer for sbcl-0.9.18 on Windows, run it
> and tried to play with it.
Thanks for the report!
> * (require :asdf-install)
> which seems to work, except on random occasions when it tells me :
> ; compilation unit aborted
> ; caught 1 fatal ERROR condition
> and then repeats the prompt line ('* \n') until I hit Ctrl-c.
Does this happen when you start SBCL directly from the binary,
or from a shortcut, or both?
This behaviour is a "known mystery" on my box at least, when starting
SBCL from a shortcut; a seeming workaround is to set the "Disable
Advanced Input Options" option in the shortcut properties.
Does this workaround work for you?
> * (asdf-install:install "C:/tmp/download/cl-ppcre.tar.gz")
> asdf-install politely asks me where I want to install, to which I
> answers politely also.
> It tells me that it is installing the package in the chosen location,
> but then hangs.
> It seems that tar.exe (from my cygwin installation) is running but not
> doing much (0% CPU). Maybe it's waiting from some input.
> Oh, I forgot to say that before the local file install, I tried the
> HTTP install (directly from Edi Weitz's site for CL-PPCRE) and it hang
> similarly, after having told me it had downloaded the file. The only
> difference was that that time it was gpg that was doing nothing. My
> command was:
> * (asdf-install:install "http://weitz.de/files/cl-ppcre.tar.gz")
SB-EXT:RUN-PROGRAM is still in need of more love for Windows, unfortunately.
> BTW, I had to manually define the environment variable SBCL_HOME for
> sbcl to find its core file. By default, it tried /usr/local/lib/sbcl,
> which is not quite right.
This seems very odd. The installer should create SBCL_HOME. Can you
please provide details of your installation procedure?
-- Nikodemus Schemer: "Buddha is small, clean, and serious."
Lispnik: "Buddha is big, has hairy armpits, and laughs."