Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
> > * (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.=20
> Does this happen when you start SBCL directly from the binary, or from
a shortcut, or both?=20
It does it from the binary, and also in the Cygwin shell.
> 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?
Nope, sorry. My first try with this option on the raw .exe produced the
In fact, I manage to reproduce the bug at will: the only thing to do is
to launch sbcl.exe with the [Enter] key, not by a double-click. Isn't it
> SB-EXT:RUN-PROGRAM is still in need of more love for Windows,
Is there something I could do? What kind of 'love' does it need?
> This seems very odd. The installer should create SBCL_HOME. Can you
please provide details of your installation procedure?
Sorry, my fault. I ran sbcl from cygwin and forgot to restart my shell
after installation, so the variable was not in the shell's environment.
And if I didn't say it already: thank you for the Windows port. At last
there's a free alternative to CLISP (and ABCL) on the platform. The
'free' (as in beer) ACL is far too limited in memory to be of any use.
"VAUCHER Laurent" <VAUCHER@...> writes:
> In fact, I manage to reproduce the bug at will: the only thing to do is
> to launch sbcl.exe with the [Enter] key, not by a double-click. Isn't it
I can't reproduce this, but I don't know if I should laugh or cry... however,
since the "* \n" symptom is identical to the shortcut-issue, I very much
hope that fixing it will fix this too.
>> SB-EXT:RUN-PROGRAM is still in need of more love for Windows,
> Is there something I could do? What kind of 'love' does it need?
Tracking down how and why of the hangs, or looking at why the gcc runs
in foreign-stack-alignment.test.sh don't work like they should.
-- Nikodemus Schemer: "Buddha is small, clean, and serious."
Lispnik: "Buddha is big, has hairy armpits, and laughs."