Re: [Chicken-users] Spiffy & OpenSSL in compiled code

[Andy Bennett]

Hi,

> In the compiled case, the binary runs but the following is produced on
> stderr when a connection is attempted:
> 
> -----
> primordial: Connection handshake error: "bad argument type - not a fixnum"
> -----

Peter and I tracked this down to spiffy.scm.
At startup time spiffy.scm tries to load the openssl egg with a (use
openssl) inside an eval. This means that spiffy doesn't have to
unconditionally depend on openssl.

'use' relies on chicken-syntax so (use chicken-syntax) must appear in
the toplevel of the executable otherwise the eval throws an exception.

With the 'csi -s' invocation, chicken-syntax is available by default.


The exception from eval was being caught and processed as if the openssl
egg was not installed. By the time ssl ports were being passed to
'accept-loop' the ssl-port? procedure was wired to return #f and
therefore it was not being converted to a tcp-port.

The workaround is to ensure that (use chicken-syntax) appears in the top
level of your top level scheme file so that it's in the
interaction-environment that gets used by eval.

The long term solution is to fix the autoload egg so that we can use
that: Alaric has a similar requirement for Ugarit so it makes sense to
put that functionality into an egg.






Regards,
@ndy

-- 
address@hidden
http://www.ashurst.eu.org/
0x7EBA75FF