On Thu, May 07, 2015 at 11:40:40PM -0400, Nick Van Horn wrote:
Thanks for the reply Peter.
This won't help because Spiffy has a run-time dependency on openssl,
which it tries to load via something like this:
(define ssl-port?
(handle-exceptions _ #f (eval `(let () (use ssl)
Then this is probably a bug: it seems that in deploy mode, evaled code
does not use the deployment search path. I've created a ticket to track
this bug: https://bugs.call-cc.org/ticket/1191
Great---thanks for doing this. This bug has derailed my plans to deploy
this application on other
On Fri, May 08, 2015 at 11:52:06AM -0400, Nick Van Horn wrote:
Then this is probably a bug: it seems that in deploy mode, evaled code
does not use the deployment search path. I've created a ticket to track
this bug: https://bugs.call-cc.org/ticket/1191
Great---thanks for doing this. This
Hi Nick,
I've used the following commands for this. The only difference is the
third command, which copies CHICKEN's core libraries into the deployment
directory. I have a hunch as to why this makes the difference, but it's
orthogonal to your problem, so for now can you just try adding
Hello again,
On Fri, May 08, 2015 at 06:48:48PM -0600, Matt Gushee wrote:
In addition to shadowing the builtin write-string, this write-string causes
a segfault when I attempt to use it within 'with-output-to-string' in csi.
Haven't looked into it any further yet, but that doesn't seem very
Hi--
I just installed the specialized-io egg, but the version available via
chicken-install does not match the documentation.
The documentation says the most recent version is 1.3, but the version I
installed, according to the .setup file, is 1.2; also, the documentation
describes a function
