Joshua Kordani
Joshua Kordani
The latter form does fail for me Clozure Common Lisp Version 1.12-dev (v1.12-dev.5-3-gb5233ade) LinuxX8664 On Mon, Nov 18, 2019 at 5:10 AM metayan wrote: > Did some more digging, and...
with keep-alive and close ommitted, a fin packet is sent out but I still encounter a timeout thrown from within finish-request
to clarify, I get this error when running under slime/swank, as opposed to starting lisp from the command line.
I get this error because ccl is not in my path, and when trying to use ceramic to set up everything, there is no way to pass the ccl path...
I imagine that would work. I guess there isn't anything more to this particular issue.
adding ccl to path solves this problem, but oddly enough, it suggests that the value provided in make LISP is ignored, as ccl is explicitly looked for in the build...
Ok, I see what is going on. when using make, the LISP specified is used only to load the buildapp build code, but once in the build code, the default...
I still have a lot to learn. I've been trying to figure out how to work in the slime debugger to work my way through backtraces like this but i...
I get ccl from svn and track trunk, I usually keep stuff like that in a ~/Source directory, so ~/Source/ccl/. I have slime setup to go into this directly and...
same sw_vers, same steps, including make clean on buildapp, error persists until I place ccl in my path. then building buildapp in lisp and from make both work. It make...