> configure: warning: not using libffi. stubs are necessary and will > be created for native methods. Hm, not sure if Japhar currently will work without libffi. Neither of us has tested that part for a long time. :-) > checking for _ prefix in compiled symbols... yes This must be wrong... the default when the test fails must be bogus. I think it uses nm to look in libm.a for some symbol... > checking dynamic linker characteristics... Win32 ld.exe > checking if libtool supports shared libraries... yes This is good. :-) The headerfile checking seems to lack a test for windows.h. > checking for _beginthreadex... no I expected this to be "yes" on Win32. Which thread interface do cygwin supply? > checking for dlopen in -ldl... no > checking for dlopen... yes > checking for dlclose... no > checking for dlsym... yes > checking for dlerror... yes This is strange. I've ported DLL handling to use the Win32 native functions. It is unhandled when dlopen() is present and dlclose() is missing... I move this discussion to the mailing list, as I think more people are needed to help you with our problems. :-) > Hope that will help. Can you please tell me what I should do to > compile it with VC++, if Cygwin continue not to work ? What did you do, Chris? -- ##> Petter Reinholdtsen <## | [EMAIL PROTECTED] O- <SCRIPT Language="Javascript">window.close()</SCRIPT> http://www.hungry.com/~pere/ | Go Mozilla, go! Go!
