Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-dev: Re: [Wireshark-dev] Building Wireshark in Windows

From: Graham Bloice <graham.bloice@xxxxxxxxxxxxx>
Date: Tue, 5 Mar 2013 14:19:28 +0000
On 5 March 2013 14:04, Alexander Papakhristos <papakhr@xxxxxxxxx> wrote:

Hello, I’ve tried to build wireshark 1.8.4 in Windows using Wireshark Step by Step guide: http://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html

I’ve installed all required software and passed verify-tools step but when I run nmake for setup stage I have an error:

 

****** gtk2 ******

No HTTP proxy specified (http_proxy and HTTP_PROXY are empty).

Downloading gtk2 into '/cygdrive/c/Program', installing into Files\Wireshark

cygwin warning:

  MS-DOS style path detected: /cygdrive/c/Program/Files\Wireshark

  Preferred POSIX equivalent is: /cygdrive/c/Program/Files/Wireshark

  CYGWIN environment variable option "nodosfilewarning" turns off this warning.

  Consult the user's guide for more details about POSIX paths:

    http://cygwin.com/cygwin-ug-net/using.html#using-pathnames

--2013-03-05 11:41:22--  http://anonsvn.wireshark.org/wireshark-win32-libs/tags/2013-01-04-1.8/packages//gtk2

Resolving anonsvn.wireshark.org (anonsvn.wireshark.org)... 174.137.42.70

Connecting to anonsvn.wireshark.org (anonsvn.wireshark.org)|174.137.42.70|:80... connected.

HTTP request sent, awaiting response... 404 Not Found

2013-03-05 11:41:23 ERROR 404: Not Found.

 

 

ERROR: Can't download http://anonsvn.wireshark.org/wireshark-win32-libs/tags/2013-01-04-1.8/packages//gtk2

 

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

Stop.

 

What’s the problem with that package? Also I don’t understand the message “Downloading gtk2 into '/cygdrive/c/Program', installing into Files\Wireshark” – it creates folder c:\program and with folder Files\Wireshark inside it. The path for wireshark_lib set to c:\Program Files\Wireshark

 

Is it normal behavior?

 



Try building (and putting your wireshark libs) in a path without spaces, e.g. C:\Wireshark.  I use Wireshark\trunk for the sources and Wireshark\libs for the libs.