Re: [Mingw-users] winsock issues

[stefan <stefan@lk...>]

On Sun, 21 Jan 2001, Rob Foehl wrote:

> aim_conn.c:344: warning: implicit declaration of function `fcntl'
> aim_conn.c:344: `F_SETFL' undeclared (first use in this function)
> aim_conn.c:344: (Each undeclared identifier is reported only once
> aim_conn.c:344: for each function it appears in.)
> aim_conn.c:344: `O_NONBLOCK' undeclared (first use in this function)
> 
> This code is actually part of libfaim.. I know the E* errors can be fixed
> by defining those constants to the appropriate WSAE* constants.. but how
> do I get around the fcntl stuff? Basically it's doing a SETFL to make the
> socket nonblocking..

ioctlsocket () is your friend.

stefan@...

[Mingw-users] winsock issues

[Rob Foehl <rob@lo...>]

I'm currently working on a port of gaim over to win32 (I hate AOL's client
with a livid passion, especially the blinky ads).. I'm having a little
trouble getting everything ported over to mingw though.. Can anybody
recommend a fix for this:

aim_conn.c: In function `aim_proxyconnect':
aim_conn.c:344: warning: implicit declaration of function `fcntl'
aim_conn.c:344: `F_SETFL' undeclared (first use in this function)
aim_conn.c:344: (Each undeclared identifier is reported only once
aim_conn.c:344: for each function it appears in.)
aim_conn.c:344: `O_NONBLOCK' undeclared (first use in this function)
aim_conn.c:348: `EINPROGRESS' undeclared (first use in this function)
aim_conn.c: In function `aim_conn_completeconnect':
aim_conn.c:755: `ETIMEDOUT' undeclared (first use in this function)
aim_conn.c:784: warning: passing arg 4 of `getsockopt' from incompatible 
pointer type
aim_conn.c:794: `F_SETFL' undeclared (first use in this function)
make: *** [aim_conn.o] Error 1

This code is actually part of libfaim.. I know the E* errors can be fixed
by defining those constants to the appropriate WSAE* constants.. but how
do I get around the fcntl stuff? Basically it's doing a SETFL to make the
socket nonblocking..

Thanks :)

-Rob

Re: [Mingw-users] winsock issues

[stefan <stefan@lk...>]

On Sun, 21 Jan 2001, Rob Foehl wrote:

> aim_conn.c:344: warning: implicit declaration of function `fcntl'
> aim_conn.c:344: `F_SETFL' undeclared (first use in this function)
> aim_conn.c:344: (Each undeclared identifier is reported only once
> aim_conn.c:344: for each function it appears in.)
> aim_conn.c:344: `O_NONBLOCK' undeclared (first use in this function)
> 
> This code is actually part of libfaim.. I know the E* errors can be fixed
> by defining those constants to the appropriate WSAE* constants.. but how
> do I get around the fcntl stuff? Basically it's doing a SETFL to make the
> socket nonblocking..

ioctlsocket () is your friend.

stefan@...

Re: [Mingw-users] winsock issues

[Rob Foehl <rob@lo...>]

Ok.. is there any specific documentation for it anywhere? :)

On Sun, 21 Jan 2001, stefan wrote:

> On Sun, 21 Jan 2001, Rob Foehl wrote:
> 
> > aim_conn.c:344: warning: implicit declaration of function `fcntl'
> > aim_conn.c:344: `F_SETFL' undeclared (first use in this function)
> > aim_conn.c:344: (Each undeclared identifier is reported only once
> > aim_conn.c:344: for each function it appears in.)
> > aim_conn.c:344: `O_NONBLOCK' undeclared (first use in this function)
> > 
> > This code is actually part of libfaim.. I know the E* errors can be fixed
> > by defining those constants to the appropriate WSAE* constants.. but how
> > do I get around the fcntl stuff? Basically it's doing a SETFL to make the
> > socket nonblocking..
> 
> ioctlsocket () is your friend.
> 
> stefan@...
> 
> 
> _______________________________________________
> MinGW-users mailing list
> MinGW-users@...
> 
> You may change your MinGW Account Options at:
> http://lists.sourceforge.net/lists/listinfo/mingw-users
>