When I try to build Wireshark on Windows, why does the build fail because of conflicts between winsock.h and winsock2.h?
As of Wireshark 0.9.5, you must install WinPcap 2.3 or later, and the corresponding version of the developer’s pack, in order to be able to compile Wireshark; it will not compile with older versions of the developer’s pack. The symptoms of this failure are conflicts between definitions in winsock.h and in winsock2.h; Wireshark uses winsock2.h, but pre-2.3 versions of the WinPcap developer’s packet use winsock.h. (2.3 uses winsock2.h, so if Wireshark were to use winsock.h, it would not be able to build with current versions of the WinPcap developer’s pack.) Note that the installed version of the developer’s pack should be the same version as the version of WinPcap you have installed. 5.
Related Questions
- Why does the linker fail with a number of "Output line too long." messages followed by linker errors when I try to build Wireshark?
- Why does my build fail with an Unresolved assembly reference error when I try to document a Compact Framework application?
- When I try to build Wireshark on Solaris, why does the link fail complaining that plugin_list is undefined?