Closed gjsjohnmurray closed 8 years ago
I had the TCP stuff working on cygwin/windows 10 using VistA's RPC broker. i'll see if i can dig up the examples i used
It works, but GT.M uses IPv6 by default. But somehow we can't convince Windows applications to talk to IPV6.
Set gtm_ipv4_only=1 in env before starting the sockets. That will fix it.
On Monday, May 16, 2016, Christopher Edwards notifications@github.com wrote:
I had the TCP stuff working on cygwin/windows 10 using VistA's RPC broker. i'll see if i can dig up the examples i used
— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub https://github.com/shabiel/fis-gtm/issues/10#issuecomment-219419739
Sam Habiel, Pharm.D. VISTA Expertise Network
how could i forget this (headbang), Sam is correct, windows always uses ipv6 by default.
That was the trick I needed. Thanks! Closing this issue.
I installed your Cygwin build on a test machine (64-bit Windows 10) and am trying unsuccessfully to run an application that makes use of TCP socket devices. I also want to get our Serenji debugger/editor working with this GT.M instance, and that uses TCP socket devices to communicate with its client UI.
So I consulted http://tinco.pair.com/bhaskar/gtm/doc/books/pg/UNIX_manual/ch09s08.html#socket_device_examples, downloaded sockexamplemulti31.m from http://tinco.pair.com/bhaskar/gtm/doc/books/pg/UNIX_manual/sockexamplemulti31.m and tried running it:
Unlike in the comments at the top of the routine (where there were only 12 "waiting" lines over a period of 33 seconds) this continued until I aborted the server job:
Then the output completed:
Am I doing something wrong, or isn't the TCP socket device stuff working in the Cygwin port yet?