This is the mail archive of the
mailing list for the Cygwin project.
Re: posix functions
- To: stefan <stefan at lkcc dot org>
- Subject: Re: posix functions
- From: Mumit Khan <khan at NanoTech dot Wisc dot EDU>
- Date: Sat, 15 Apr 2000 13:06:44 -0500
- cc: Cygwin Mailing List <cygwin at sourceware dot cygnus dot com>
stefan <firstname.lastname@example.org> writes:
> when posting some software i noticed, that most of the POSIX functions
> have been implemented within the cygwin1.dll. would not have expected...
> the only "problem" where these two symbols:
> does anyone know if i am just using a cygwin1.dll too old, or never ever
> someone used these ?
As far as I can remember, both of these are from BSD 4.3, and is not
part of the POSIX specs. Unfortunately, I don't have the POSIX specs
with me, so correction welcome. Was it added to later revisions of
You can probably use the POSIX ("almost equivalent") setuid, but be
aware that it's stubbed under Cygwin, which means that it'll link but
set errno to ENOSYS when called.
> i got two further question on the socket-api:
> 1) is it neccessary to link againt -lwsock32 using cygwin1.dll ?
Yes, but you need to make sure you're using winsock calls, not Cygwin's
sockets. I believe that you need to define:
*before* including any cygwin's networking includes. And of course you'll
need to link with -lwsock32 or whatever the appropriate libraries are.
> 2) is it neccessary to call WSAStartup() (i am NOT speaking of mingw) ?
If you're going to use Winsock instead of Cygwin networking code, you'll
have to follow Winsock's specifications. Winsock requires that you call
Want to unsubscribe from this list?
Send a message to email@example.com