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

At 2.2.8 of this manual http://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html the system encounter the below problem. How to solve it?

nmake -f Makefile.nmake verify_tools Microsoft (R) Program Maintenance Utility Version 10.00.40219.01 Copyright (C) Microsoft Corporation. All rights reserved. tools/win-setup.sh : No such file or directory6: /cygdrive/c/Development/wireshark/tools/win-setup.sh : cannot execute: No such file or directoryve/c/Development/wireshark/tools/win-setup.sh Can't find Qt. This will become a problem at some point. tools/win-setup.sh : No such file or directory6: /cygdrive/c/Development/wireshark/tools/win-setup.sh : cannot execute: No such file or directoryve/c/Development/wireshark/tools/win-setup.sh NMAKE : fatal error U1077: 'C:\cygwin64\bin\bash.EXE' : return code '0x7e' Stop.

asked 09 Jun '14, 11:16

Nazmul's gravatar image

Nazmul
11124
accept rate: 0%

edited 09 Jun '14, 11:48

grahamb's gravatar image

grahamb ♦
19.8k330206


Have you set your environment up properly? What is the output of set WIRE*? What is the output of set PATH?

Also note that the output you have posted above looks to be corrupted, please ensure you cut and paste accurately to prevent confusion.

permanent link

answered 09 Jun '14, 11:55

grahamb's gravatar image

grahamb ♦
19.8k330206
accept rate: 22%

Dear Graham,

I just followed the above indicated manual word by word and nothing else. What path to set and how to set it could you please explain? Thanks for correcting the output format. Below is the output as you asked -

set WIRE*

Environment variable WIRE* not defined

set PATH

Path=C:\Windows\Microsoft.NET\Framework\v4.0.30319;C:\Windows\Microsoft.NET\Framework\v3.5;;C:\Program Files (x86)\Micro soft 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;c:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\Bin\VCPackages;;C:\Prog ram Files\Microsoft SDKs\Windows\v7.1\Bin\NETFX 4.0 Tools;C:\Program Files\Microsoft SDKs\Windows\v7.1\Bin;;%CYGWIN%;C:\ Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\;c:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\BIN ;C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\Tools;c:\Windows\Microsoft.NET\Framework64\v4.0.30319;c:\Wi ndows\Microsoft.NET\Framework64\v3.5;c:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\VCPackages;C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\bin\NETFX 4.0 Tools;C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\bin;C:\Window s\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;c:\Program Files (x86)\Micros oft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files\Microsoft SQL Serv er\100\DTS\Binn\;C:\Program Files\Microsoft Windows Performance Toolkit\;C:\cygwin64\bin\; PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC

(09 Jun '14, 12:12) Nazmul

Do you have the file c:/Development/wireshark/tools/win-setup.sh? or whats the path to ~/wireshark/tools/win-setup.sh

(09 Jun '14, 12:38) Anders ♦
1

Apart from your post still containing cut and paste errors (extra spaces) that make diagnosing issues much harder, I've taken your path, split it at the ";" and sorted it. The resulting path is then:

%CYGWIN% C:\ Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\ C:\cygwin64\bin\ C:\Prog ram Files\Microsoft SDKs\Windows\v7.1\Bin\NETFX 4.0 Tools C:\Program Files (x86)\Micro soft Visual Studio 10.0\Common7\IDE c:\Program Files (x86)\Micros oft SQL Server\100\Tools\Binn\ C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\bin C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\bin\NETFX 4.0 Tools C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\Tools C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\Tools c:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\Bin c:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\BIN c:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\Bin\VCPackages c:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\VCPackages C:\Program Files\Microsoft SDKs\Windows\v7.1\Bin c:\Program Files\Microsoft SQL Serv er\100\DTS\Binn\ c:\Program Files\Microsoft SQL Server\100\Tools\Binn\ C:\Program Files\Microsoft Windows Performance Toolkit\ c:\Wi ndows\Microsoft.NET\Framework64\v3.5 C:\Window s\system32 C:\Windows C:\Windows\Microsoft.NET\Framework\v3.5 c:\Windows\Microsoft.NET\Framework64\v4.0.30319 C:\Windows\System32\Wbem C:\Windows\System32\WindowsPowerShell\v1.0\ C:\Windows\Microsoft.NET\Framework\v4.0.30319

Ignoring the obvious extra spaces, there are some duplications, multiple references to different SDK installations and an odd %CYGWIN% .

Try removing the %CYGWIN% from your path.

(10 Jun '14, 02:28) grahamb ♦

Dear Graham,

If I remove the "C:\cygwin64\bin\" from PATH then following happens -

nmake -f Makefile.nmake verify_tools

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

'bash' is not recognized as an internal or external command, operable program or batch file.

Can't find Qt. This will become a problem at some point.

'bash' is not recognized as an internal or external command, operable program or batch file.

NMAKE : fatal error U1077: 'bash' : return code '0x1' Stop.

(11 Jun '14, 15:08) Nazmul

Dear Anders,

Yes, I have the file but for some strange reason it can't find the file.

pwd

/cygdrive/c/Development/wireshark/tools

ls -l | grep win

-rwxrwxrwx+ 1 naz None 7465 Jun 11 17:39 win-setup.sh

----------+ 1 naz None 7465 May 23 11:48 win-setup.txt

-rwxrwxrwx+ 1 naz None 169 May 23 11:27 win32-setup.sh

----------+ 1 naz None 150 May 23 11:17 win32-setup.sh.bak

----------+ 1 naz None 1081 Jun 11 17:28 win64-setup.sh

(11 Jun '14, 15:13) Nazmul
1

You do not need cygwin on your path. Config.nmake adds the cygwin bin directory to the path in the correct place for the build, however it expects it to be C:\Cygwin\bin, if this is not the case, i.e. you have installed cygwin elsewhere, then you must modify config.nmake and adjust the setting of CYGWIN_PATH accordingly.

Make these changes and run nmake -f Makefile.nmake verify_tools again.

(12 Jun '14, 02:58) grahamb ♦

Dear Graham,

C:\Cygwin\bin indeed was the issue. Cygwin was installed under C:\Cygwin64. Changing it to C:\Cygwin solved the problem.

However, I ran into another trouble (almost there) at [2.2.10 Building Wireshark]. When I issued the command - " nmake -f Makefile.nmake all " I got the below output.

//////////MANY LINES OF OUTPUT HERE - TRUNCATED (LOOKS ALL SUCCESSFUL)//////////////

1 File(s) copied

    xcopy ".\manuf" wireshark-gtk2 /d

.\manuf

1 File(s) copied

    xcopy ".\services" wireshark-gtk2 /d

.\services

1 File(s) copied

    xcopy ".\pdml2html.xsl" wireshark-gtk2 /d

.\pdml2html.xsl

1 File(s) copied

    bash -o igncr tools/textify.sh "./COPYING" wireshark-gtk2

tools/textify.sh: line 68: u2d: command not found

NMAKE : fatal error U1077: 'c:\cygwin\bin\bash.EXE' : return code '0x7f'

Stop.

(15 Jun '14, 16:08) Nazmul
showing 5 of 7 show 2 more comments

I have followed below instruction as per Graham which resolved the issue -

  1. Changed directory name C:\Cygwin64 to C:\Cygwin
  2. Install bison, flex, unzip and wget packages in Cygwin(Click cygwin installer, after selecting a mirror for download, in the search box type the package names you are looking for (e.g. bison) and install them one by one.
  3. Got - /usr/bin/bison: m4 subprocess failed - error message. 'm4' package was not installed, again I follow the step 2 above to install m4.
  4. Installed QT (Note: it's a large download and will occupy ~5.00 GB of your hard drive).
  5. Got - tools/textify.sh: line 50: u2d: command not found - error message. dos2unix package was not installed, again I followed step 2 above to install dos2unix.

Finally all went well. I persisted on trying for last 7 days without getting stressed. What it seemed like will never happen, finally it's done. If a novice like me can do it you can too!

THANKS TO GRAHAM

Cheers!

permanent link

answered 15 Jun '14, 16:36

Nazmul's gravatar image

Nazmul
11124
accept rate: 0%

edited 15 Jun '14, 16:38

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×158
×52
×36

question asked: 09 Jun '14, 11:16

question was seen: 4,173 times

last updated: 15 Jun '14, 16:38

p​o​w​e​r​e​d by O​S​Q​A