Hello.

You are right, CCL was just unable to load the library (It was sufficient for me to jus trun svn update of my CCL 1.7 distro; looks like previously my distribution was somehow incomplete - didn't have cdb files).

Now the CCL 1.7 test results for usocket are exactly like results of CCL 1.6:

3 out of 24 total tests failed: USOCKET-TEST::OPERATION-NOT-PERMITTED-ERROR.1, USOCKET-TEST::UDP-SEND.1, USOCKET-TEST::UDP-SEND.2.

Best regards, - Anton

04.02.2012, 14:45, "Chun Tian (binghe)" binghe.lisp@gmail.com:

Hi, Anton

Today I've verified this issue, I think the issue you met is because you didn't set environment variable CCL_DEFAULT_DIRECTORY for CCL 1.7 properly. USOCKET need to use a Windows system function called "send", and to have this function, CCL will load its definition at runtime (when it's reading the form #_send), by loading a file called "win32-headers/libc/functions.cdb" (or in win64-headers).  If CCL cannot find this file, it will not create the symbol WIN64::|send| at all.

Hope this helps,

Regards,

Chun Tian (binghe)

在 2011-12-29，10:29， Anton Vodonosov 写道：

...

29.12.2011, 03:07, "Anton Vodonosov" avodonosov@yandex.ru:

...

Some of the failures are probably bugs in tests, but other seems to be bugs in usocket itself.  For example CCL on Windows:

Read error between positions 195 and 295 in C:/Users/anton/quicklisp/dists/quicklisp/software/usocket-0.5.4/vendor/ccl-send.lisp.    Unhandled ERROR is signaled: Foreign function not found: WIN64::|send|

BTW, this particular error seems to be a regression on CCL 1.7 Windows.

I just added test results for more CCL versions. You may compare CCL windows version:  1.7 64bit and 32bit have this error, but 1.6 64bit does not.

_______________________________________________  usocket-devel mailing list  usocket-devel@common-lisp.net  http://lists.common-lisp.net/cgi-bin/mailman/listinfo/usocket-devel