This is a static archive of our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

Trouble getting started with Windows build

0

Hello, I believe I have followed the instructions to build Wireshark (Windows) but am stuck at the tool verification stage. When I run the following command:

nmake -f Makefile.nmake verify_tools

I get the following output:

C:\DataRoot\Projects\Wireshark>nmake -f Makefile.nmake verify_tools

Microsoft (R) Program Maintenance Utility Version 10.00.40219.01 Copyright (C) Microsoft Corporation. All rights reserved.

"C:/Program Files (x86)/Git/bin/bash.EXE": line 0: "C:/Program Files (x86)/Git/b in/bash.EXE": igncr: invalid option name Can't find Qt. This will become a problem at some point. "C:/Program Files (x86)/Git/bin/bash.EXE": line 0: "C:/Program Files (x86)/Git/b in/bash.EXE": igncr: invalid option name NMAKE : fatal error U1077: '"C:\Program Files (x86)\Git\bin\bash.EXE"' : return code '0x2' Stop.

C:\DataRoot\Projects\Wireshark>

I hope someone can point me in the right direction to fix this. Thanks, Sid.

asked 23 Nov ‘14, 16:11

sid%20Price's gravatar image

sid Price
21226
accept rate: 0%

edited 24 Nov ‘14, 00:53

grahamb's gravatar image

grahamb ♦
19.8k330206


2 Answers:

1

I think the issue is having "C:\Program Files (x86)\Git\bin on your PATH. My command prompt has ...\Git\cmd on the path which gives access to the git.exe which is all the Wireshark build requires, I can't remember if I did that manually, or (more likely) the chocolatey install of git did that.

config.nmake automagically adds ...\cygwin(64)\bin to the path for the build, so you'll just need to exclude ...\Git\bin from the path you use for your build command prompt.

answered 24 Nov '14, 00:52

grahamb's gravatar image

grahamb ♦
19.8k330206
accept rate: 22%

1
"C:/Program Files (x86)/Git/bin/bash.EXE": line 0: "C:/Program Files (x86)/Git/b
in/bash.EXE": igncr: invalid option name

The above indicates that Git bash is being used rather than cygwin bash.

I'm going to assume that you've installed cygwin.

Based upon the above, you'll need to adjust your PATH so that cygwin/bin appears before anything referring to Git.

answered 23 Nov '14, 19:31

Bill%20Meier's gravatar image

Bill Meier ♦♦
3.2k1850
accept rate: 17%

Excellent! For some reason cygwin\bin was not in my path so I added "cygwin64\bin" and now I am much closer. What I now see when I run the verify_tools "makefile" is:

C:\DataRoot\Projects\Wireshark>nmake -f Makefile.nmake verify_tools

Microsoft (R) Program Maintenance Utility Version 10.00.40219.01 Copyright (C) Microsoft Corporation. All rights reserved.

ERROR: The contents of 'C:\Wireshark-win32-libs\current_tag.txt' is (unknown). It should be 2014-10-01.

Can't find Qt. This will become a problem at some point. Checking for required applications: cl: /cygdrive/c/Program Files (x86)/Microsoft Visual Studio 10.0/VC/Bin/ cl link: /cygdrive/c/Program Files (x86)/Microsoft Visual Studio 10.0/VC/Bi n/link nmake: /cygdrive/c/Program Files (x86)/Microsoft Visual Studio 10.0/VC/B in/nmake bash: /usr/bin/bash bison: /usr/bin/bison flex: /usr/bin/flex env: /usr/bin/env grep: /usr/bin/grep /usr/bin/find: /usr/bin/find peflags: /usr/bin/peflags perl: /usr/bin/perl C:\Python27\python.exe: /cygdrive/c/Python27/python.exe sed: /usr/bin/sed unzip: /usr/bin/unzip wget: /usr/bin/wget

Not finding "QT" is probably because I did not set that path in the "config.nmake" file.

I don't know about the error in file "current_tag.txt", both the Wireshark "libs" folders (win32 and win64) are empty. Is htis something I need to fix? Sid.

(24 Nov '14, 07:28) sid Price

As I mentioned in my answer, config.nmake adds cygwin to your path, that's why there is no instruction to add it.

You are seeing the error about "current"tag" as you don't have the current versions of the 3rd party libraries. run nmake -f makefile.nmake setup to download and unpack them. See the Developers Guide 2.2.11 Install Libraries step.

It also helps others if you format code or console output with the "<code>" "</code>" tags to make the content more readable.

(24 Nov '14, 08:08) grahamb ♦

grahamb, Many thanks for your help. running "make -f makefile.mak setup" is mentioned in the Developers' Guide AFTER the verify tools step, a note about the potential error I saw would be useful. So, I ran the "setup" makefile argument and it appeared to be running well until I got the following error:

Extracting '/cygdrive/c/Wireshark-win64-libs/nasm-2.09.08-win32.zip' into '/cygdrive/c/Wireshark-win64-libs/.' Verifying that the DLLs and EXEs in . are executable. 'C:\Program' is not recognized as an internal or external command, operable program or batch file. NMAKE : fatal error U1077: '"C:\Program Files (x86)\Git\bin\echo."' : return code '0x1' Stop.

This looks like a problem with a command in the makefile not being enclosed in quotes or maybe in a script, however I am not sure where to look for it. Sid.

(24 Nov '14, 14:34) sid Price

Nope, looks like a problem with your environment having ..\Git\bin on the PATH before cygwin. The build script is picking up the git version of echo.

(25 Nov '14, 03:09) grahamb ♦

grahamb, Thanks for the response, however that is not the case. Here is a dump of my "path" environmental variable:

PATH=c:\Windows\Microsoft.NET\Framework64\v4.0.30319; C:\Windows\Microsoft.NET\Framework\v4.0.30319;C:\Windows\Microsoft.NET\Framework64\v3.5; C:\Windows\Microsoft.NET\Framework\v3.5; ; C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE; C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\Tools; ; c:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\Bin\amd64; c:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\Bin\VCPackages; ; C:\Program Files\Microsoft SDKs\Windows\v7.1\Bin\NETFX 4.0 Tools\x64; C:\Program Files\Microsoft SDKs\Windows\v7.1\Bin\x64; C:\Program Files\Microsoft SDKs\Windows\v7.1\Bin; ; C:\Python27\; c:\cygwin64\bin; C:\Windows\system32; C:\Windows; C:\Windows\System32\Wbem; C:\Windows\System32\WindowsPowerShell\v1.0\; C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\; C:\Program Files\Microsoft SQL Server\110\Tools\Binn\; C:\Program Files\Microsoft Windows Performance Toolkit\; C:\Windows\System32\WindowsPowerShell\v1.0\; C:\Program Files (x86)\Git\cmd; C:\Program Files (x86)\Git\bin;C:\Chocolatey\bin;C:\Program Files (x86)\Git\cmd;

Note that the "cygwin" path is ahead of the "Git" entry. Since my error output appears to be referring to git there must be some other configuratkon that is wrong. Again, thanks, Sid

(25 Nov '14, 07:15) sid Price

grahamb, so I took your advice from elsewhere in this thread and removed the "git" paths form my PATH variable and the library installation now works. Thanks, Sid.

(25 Nov '14, 07:38) sid Price
showing 5 of 6 show 1 more comments