Wireshark-dev: Re: [Wireshark-dev] error encountered during compilation on windows
From: Rahul Rohit <rahul.rohit@xxxxxxxxxxx>
Date: Tue, 11 Feb 2014 17:45:21 +0530

Hi,

 

<<So you haven’t managed to build vanilla Wireshark without *any* modifications?>>

Yes. I am using Wireshark baseline code  but I am unable to make the build . I am getting the errors that I mentioned in my last mail

 

 

What I observed during the compilation is that at each compilation command(nmake –f Makefile.nmake all) all the files are getting compiled over and over again. I wonder if it has got something to do

With the system time ?

 

Regards

Rahul Rohit

 

 

 

 

From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Anders Broman
Sent: Tuesday, February 11, 2014 5:12 PM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] error encountered during compilation on windows

 

 

 

From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Rahul Rohit
Sent: den 11 februari 2014 11:26
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] error encountered during compilation on windows

 

Hello,

 

<<< If this is the first time you have tried to build Wireshark, then the usual advice is to go back and read the Developers Guide again and make sure you are following the prescribed method exactly as written because it does work for many people.>>

 

<No, this is not the first time, I often make builds.

 

<<< If you have done that, or you have previously built Wireshark successfully, is your copy of the sources modified in any way?  If so can you compile an unmodified version without the changes? >>

 

<In all the previous cases , after getting the error when I commented  'WS_MSVC_NORETURN'(in except.h) before ‘except_throwd', 'except_throwf', 'except_rethrow’, 'except_throwf’ functions it worked.

 

 

So you haven’t managed to build vanilla Wireshark without *any* modifications?

 

Regards

Anders





===============================================================================
Please refer to http://www.aricent.com/legal/email_disclaimer.html
for important disclosures regarding this electronic communication.
===============================================================================