i've been working with FPC 2.6.0 (release) and synapse for a short while... currently we're using synapse-trunk (release40)... on windows synapse works well for what i've done with it... however, i need these tools on OS/2 so tomas hajny has been helping me by porting synapse so that it will compile on OS/2... http connections work fine but https result only in
>testhttp https://www.google.com/ ERROR 500 we're using the testhttp.pas and have added ssl_openssl to the uses clause... we've tried both EMX and GCC compiles of the openssl dlls... in gdb, i can see them getting loaded and there's no errors reported... well, nothing other than the above which doesn't say too much :? i've even added http.Resultstring to the output and it is also blank... it appears that http codes are used for many things but there's no way to tell where the failures come from... for example, you get the same error report if you use an invalid domain... so is it a DNS lookup failure or something else?? how do you find out what? >testhttp http://www.google.invalid/ ERROR 500 the dlls work fine with other applications needing ssl and even specifically https... tomas told me to make sure that i let you know that we're using the winsock 1.1 code... he also started with the sswin32.inc file (copied to another name more os/2 related) because starting with sslinux.inc brought other dependencies which in FPC are not yet supported on OS/2... below are his words on this aspect... [quote="tomas hajny"] Well, I started with the Unix implementation first (since TCP/IP support in OS/2 is based on the one for IBM AIX which is in turn based on BSD sockets implementation) but there are quite a few additional dependencies (e.g. unit netdb from fcl-net which isn't supported under OS/2 either at the moment and it would require quite a few changes) and it also accesses Unix-specific stuff quite a lot; I'm sure that it's possible to sort it out, but considering my limited knowledge of the respective functionality, it's anything but easy for me. That's why I decided to choose the other route and chose the implementation for MS Windows which is based on Winsock. This is due to the fact that OS/2 (and also FPC RTL for OS/2) provides support for both the traditional Unix sockets (implemented mostly in so32.dll) and also compatibility layer for the Winsock library designed by Microsoft for MS Windows (originally already for the 16-bit MS Windows 3.11 as far as I know). The only issue is the fact that OS/2 supports only the older version of the Winsock interface (Winsock 1.1), whereas current Win32/Win64 use newer version of Winsock. Fortunately, Synapse features support for not only the latest Winsock but also the older Winsock version (available through a conditional define in Synapse sources), although this support (in Synapse) may not be fully up to date and tested so well in current Synapse versions (which in turn may be one of possible reasons of your current issue). [/quote] so with all that out of the way, can anyone help? these tools are pure text console mode only... absolutely no GUI at all... i cannot use synadbg because fpc 2.6.0 throws the following error... synadbg.pas(63,21) Error: Identifier not found "class" synadbg.pas(64,5) Error: Error in type definition synadbg.pas(64,5) Fatal: Syntax error, ";" expected but "identifier CLASS" found help... please? ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ synalist-public mailing list synalist-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synalist-public
