Yeah, it's a ported app, and I'm not doing any window specific setup. I'll look deeper into that.


On Tue, Oct 28, 2008 at 4:00 AM, Tor Lillqvist <tml@iki.fi> wrote:
> Included is the apps includes

Showing us that is mostly pointless, as it is obvious that you are
including the right headers if you get the thing to compile;)

> and the connect line

>     /* Connect the TCP socket*/
>     sock=tcp_connect(host,port);

Unfortunately showing us just that line is also mostly pointless, as
we have no idea what this tcp_connect() function does (besides the
obvious implied by its name).

The first thing I can think of that might be wrong is this: Do you
call WSAStartup() before any other WinSock functions? Even if the
WinSock API looks and feels a lot like the normal "BSD" socket API
used on Unixes, there are some like differences, like that you have to
call an initialisation function, WSAStartup(), first.


This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
MinGW-users mailing list

You may change your MinGW Account Options or unsubscribe at: