Re: [Chicken-users] How to compile with openssl?

[Kristian Lein-Mathisen]

Hi Sascha,

which CHICKEN version are you using?

There is a bug in some older versions where you need to specify (use chicken-syntax) for it work in compiled modules. Does that help?

K.

On Tue, Oct 7, 2014 at 2:25 PM, Arthur Maciel <address@hidden> wrote:

Sascha, putting (use openssl) in your code makes any difference?

Best wishes,
Arthur

2014-10-07 9:16 GMT-03:00 Sascha Ziemann <address@hidden>:

2014-10-07 13:48 GMT+02:00 Peter Bex <address@hidden>:

You'll need to ensure that openssl is available to the application.
Like the error message says, all you need to do is ensure that it's
installed and it'll work.  If you're using -deploy, make sure that you
add the egg to your application bundle.  If you're using a custom egg
repository, ensure that openssl is in there.

I run the interpreted and compiled version on the same system. How can the egg not being there for the compiled version, if it is there for the interpreted version?

I tried strace on the interpreted and the compiled version. The funny thing is, that the compiled version opens libssl and after that reports the error that openssl is not available.

$ strace ./domrobot 127.0.0.1 2>&1|grep ssl

stat64("/var/lib//chicken/6/openssl.so", {st_mode=S_IFREG|0755, st_size=251089, ...}) = 0
stat64("/var/lib//chicken/6/openssl", 0xbff9239c) = -1 ENOENT (No such file or directory)
stat64("/var/lib//chicken/6/openssl.so", {st_mode=S_IFREG|0755, st_size=251089, ...}) = 0
open("/var/lib//chicken/6/openssl.so", O_RDONLY) = 3
open("/usr/lib/i586/libssl.so.1.0.0", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/lib/libssl.so.1.0.0", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/lib/i586/libssl.so.1.0.0", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/lib/libssl.so.1.0.0", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/lib/i386-linux-gnu/i586/libssl.so.1.0.0", O_RDONLY) = 3
write(2, "(ssl-connect) Unable to connect "..., 94(ssl-connect) Unable to connect over HTTPS. To fix this, install the openssl egg and try again) = 94

csi opens just the same lib:

$ grep /usr/lib/i386-linux-gnu/i586/libssl.so.1.0.0 *.trace
csc.trace:open("/usr/lib/i386-linux-gnu/i586/libssl.so.1.0.0", O_RDONLY) = 3
csi.trace:open("/usr/lib/i386-linux-gnu/i586/libssl.so.1.0.0", O_RDONLY) = 4

I do not think that my system installation is broken. I think csi and csc do different things with libssl.

Regards,
Sascha

_______________________________________________
Chicken-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/chicken-users

_______________________________________________
Chicken-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/chicken-users