Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cygwin should not use winsock2 #177

Merged
merged 1 commit into from
Mar 25, 2017
Merged

Cygwin should not use winsock2 #177

merged 1 commit into from
Mar 25, 2017

Conversation

billziss-gh
Copy link
Contributor

As per the commit message:

The configure.ac script was erroneously including -lws2_32,
i.e. the winsock2 library. Cygwin is a full POSIX environment
and does not need the winsock2 functionality as it supplies its
own POSIX compatible sockets.

Including -lws2_32 caused getnameinfo to fail with error 10093
(WSANOTINITIALISED). This usually means that the Winsock
WSAStartup function has not been called. Calling WSAStartup is
not necessary for Cygwin programs and in fact should be avoided.

The configure.ac script was erroneously including -lws2_32,
i.e. the winsock2 library. Cygwin is a full POSIX environment
and does not need the winsock2 functionality as it supplies its
own POSIX compatible sockets.

Including -lws2_32 caused getnameinfo to fail with error 10093
(WSANOTINITIALISED). This usually means that the Winsock
WSAStartup function has not been called. Calling WSAStartup is
not necessary for Cygwin programs and in fact should be avoided.
@sahlberg sahlberg merged commit e22538c into sahlberg:master Mar 25, 2017
@sahlberg
Copy link
Owner

Merged. Thanks.

@billziss-gh
Copy link
Contributor Author

Thanks again!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants