ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-dev: Re: [Wireshark-dev] error encountered during compilation on windows

From: Rahul Rohit <rahul.rohit@xxxxxxxxxxx>
Date: Tue, 11 Feb 2014 15:55:31 +0530

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.

 

<< If you have recently updated your sources have you tried "nmake -f Makefile.nmake distclean" first?>>

Yes, I modified the codes for ranap in asn1 folder and generated the corresponding .c files

 

<< What method did you use obtain your sources?>>

I downloaded the baseline code of wireshark from the website

 

Output of ‘nmake -f Makefile.nmake verify_tools’:

 

 

Microsoft (R) Program Maintenance Utility Version 10.00.30319.01

Copyright (C) Microsoft Corporation.  All rights reserved.

 

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/BIN/link

nmake: /cygdrive/c/Program Files (x86)/Microsoft Visual Studio 10.0/VC/BIN/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

 

Has it got anything to do with the timings in system clock ??

 

Regards

Rahul Rohit

 

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

 

On 11 February 2014 07:41, Rahul Rohit <rahul.rohit@xxxxxxxxxxx> wrote:

Hi,

During the build of wireshark  exe in windows machice(32 bit) we get the following errors.

 

epan\except.h(97) : error C2054: expected '(' to follow 'WS_MSVC_NORETURN'

epan\except.h(97) : error C2085: 'except_rethrow' : not in formal parameter list

epan\except.h(98) : error C2082: redefinition of formal parameter 'WS_MSVC_NORETURN'

epan\except.h(98) : error C2143: syntax error : missing ';' before 'type'

epan\except.h(98) : error C2085: 'except_throw' : not in formal parameter list

epan\except.h(99) : error C2082: redefinition of formal parameter 'WS_MSVC_NORETURN'

epan\except.h(99) : error C2143: syntax error : missing ';' before 'type'

epan\except.h(99) : error C2085: 'except_throwd' : not in formal parameter list

epan\except.h(100) : error C2082: redefinition of formal parameter 'WS_MSVC_NORETURN'

epan\except.h(100) : error C2143: syntax error : missing ';' before 'type'

epan\except.h(100) : error C2085: 'except_throwf' : not in formal parameter list.

 

 

 

Please help me on this issue.

 

 

 

Hi Rahul,

 

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.

 

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?

 

If you have recently updated your sources have you tried "nmake -f Makefile.nmake distclean" first?

 

What method did you use obtain your sources?

 

Finally, if you can't get any further, please attach the entire output of "nmake -f Makefile.nmake verify_tools" and then the complete output of "nmake -f Makefile.nmake".

 

Regards,

 

Graham





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