Skip to main content

Building Wireshark on Win32

It was a tedious process, but here's how I got it done. I first tried to follow the:
http://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html

However, it's not as straightforward as it seems. Here's the lowdown on how I got the source to build:

First, I tried building using the following environment:
- Microsoft Visual Studio .NET 2003
- Cygwin 1.6 with unzip, bison, flex, perl, patch, wget
- Python 3.1
- Subversion 1.6.6-4
- TortoiseSVN 1.6.6

One of the source files, epan/dissectors/packet-dcerpc-netlogon.c, uses a variadic macro, which is only supported in MSVC 2005 and later. Wasn't interested in commenting out the code only to find more problems, so I abandoned this idea.

I then tried to come up with an environment that was probably more supported by Wireshark:
- Microsoft Visual Studio C++ 2008 Express Edition
- Cygwin 1.7 with unzip, bison, flex, perl, patch, wget
- Python 2.6.4
- Subversion 1.6.6-4
- TortoiseSVN 1.6.6

Things went well except a couple things:
- libssp0 needs to be installed in cygwin. Maybe it's because Cygwin 1.7 is so new and the Wireshark documentation has yet to be updated, but this is needed for the latest version of perl in cygwin.
- I cannot run the finished executable without the msvcr71.dll somewhere on the system, despite the fact that I built it against the VC 2008EE compiler. I am completely baffled.

Update: I found out that the current unstable version links to the MIT Kerberos build, which relies on MSVC .NET 2003 (msvcr71.dll), which appears to be the problem. I logged a bug on Wireshark's bugzilla, but I'll probably move forward with a stable branch to be productive.
Labels:

Comments

  1. AnonymousMarch 4, 2022 at 6:50 PM

    Slot Machine Casino Games - Dr.MCD
    Slot Machines Play the best online slots 광주광역 출장안마 with Dr.MCD, the award-winning game studio 청주 출장마사지 with 경상남도 출장안마 cutting-edge 익산 출장안마 technology. 삼척 출장안마 Discover thousands of other slot

    ReplyDelete

Post a Comment

Popular posts from this blog

C++ Development Environment

Trolling through some forums today, I found some great resources for C++, so I expanded on it and inserted some annotations. Categories are Integrated Development Environment (IDE), UML Interface, Team Collaboration, Coding Standards, Bug Tracking, Version Control, Unit Test Library, and Performance Testing. A bracket sits next to the resource which contains a W for Windows support, L for Linux, and M for Mac. A $ indicates that a standard version of the software will require a purchased license. IDE: Eclipse CDT ( eclipse.org ) [WLM] Visual SlickEdit ( slickedit.com ) [WLM$] UML: Eclipse MDT ( eclipse.org ) [WLM] Team Collaboration: Skype [WLM] Zoho [WLM] Sharepoint [W$] SourceForge [WLM] Coding Standards (Platform Agnostic): The Lockheed Martin Joint Strike Fighter C++ coding standards ( att.com ) The MISRA C++ coding standards [$] ( misra-cpp.org ) Bug Tracking: Bugzilla ( bugzilla.org ) [WLM] Unfuddle ( unfuddle.com ) [WLM] Version Control: mercurial subversion mercurial git cvs ...
Post a Comment
Read more

Software Design Principles - SOLID

The SOLID software design principles weren't called SOLID while I was in grad school, but the concepts were there in my Object Oriented Design course. They're worth mentioning here, primarily because I think once you start coding and become dangerous, it's one of the best ways to stay organized once you incorporate it into your daily coding routines, and it even changes your way of thinking for the better: https://en.wikipedia.org/wiki/SOLID
3 comments
Read more

The TL;DR guide to git

While in the past I've held a pretty high opinion to using mercurial for version control, the majority of version control these days seems to done in git.  Here were the commands I found most useful to get productive with git right away. # Clone a repository from an origin, i.e. my github MaskingUtils repository git clone git@github.com:caelumvox/masking-utils.git # Add a file after it's been updated to stage it for commit, or add a new file git add filename # Commit the file to local repo git commit # Push the file to the origin so the rest of the team can see it git push # List all locally tracked branches git branch git branch --list # Get a list of all branches from the remote git branch -r # Create branch locally git branch develop # Push the branch to the origin repository to make sure it is tracked there git push --set-upstream origin develop # Pulls latest from all local branches tracked from origin; won't pull non-tracked branches git pull --all # Fetch the branch ...
Post a Comment
Read more