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] 0.99.6 build problems on Windows

From: Graham Bloice <graham.bloice@xxxxxxxxxxxxx>
Date: Thu, 04 Oct 2007 17:08:15 +0100
Michael Lum wrote:
> Hi,
>
> I'm having a problem trying to build Wireshark 0.99.6 source on Windows.
> I've searched on Google, etc. but can't find anything that helps.
>
> Everything looks good until it comes to compiling 'filesystem.c':
>
>   ...
>
> filesystem.c
> C:\PROGRA~1\MICROS~3\VC98\INCLUDE\exdisp.h(1423) : error C2032:
> '<Unknown>' : function cannot be membe r of struct 'IWebBrowserAppVtbl'
> C:\PROGRA~1\MICROS~3\VC98\INCLUDE\exdisp.h(1430) : error C2032:
> '<Unknown>' : function cannot be membe r of struct 'IWebBrowserAppVtbl'
> C:\PROGRA~1\MICROS~3\VC98\INCLUDE\exdisp.h(1435) : error C2032:
> '<Unknown>' : function cannot be membe r of struct 'IWebBrowserAppVtbl'
> C:\PROGRA~1\MICROS~3\VC98\INCLUDE\exdisp.h(1442) : error C2032:
> '<Unknown>' : function cannot be membe r of struct 'IWebBrowserAppVtbl'
> C:\PROGRA~1\MICROS~3\VC98\INCLUDE\exdisp.h(1461) : error C2071:
> '<Unknown>' : illegal storage class
>
>   ...
>
> C:\PROGRA~1\MICROS~3\VC98\INCLUDE\exdisp.h(3067) : error C2020: 'lpVtbl'
> : 'struct' member redefinitio n
> C:\PROGRA~1\MICROS~3\VC98\INCLUDE\exdisp.h(3067) : fatal error C1003:
> error count exceeds 100; stoppin g compilation follow.c
>
> I used the following steps:
>
> 1.  get source from SVN
> 2.  make -f Makefile.nmake distclean
> 3.  make -f Makefile.nmake setup
> 4.  make -f Makefile.nmake all
>
> I've built many versions of the Ethereal and Wireshark before and I can
> build 0.99.4 (using a different library directory).
>
> I have set:
>
> WIRESHARK_LIBS=C:\wireshark-win32-libs-new
>
> I'm using MS Visual C++ 6.0 on Windows XP with cygwin.
>
>   
I would suspect a path issue possibly related to the Platform SDK
headers.  The headers in the error message are the standard VC 6 ones.

What is the value of path in your build environment?

-- 
Regards,

Graham Bloice