Wireshark-dev: Re: [Wireshark-dev] 0.99.6 build problems on Windows
From: "Michael Lum" <[email protected]>
Date: Wed, 10 Oct 2007 03:43:21 +0800
I tried this, the command-line I used to generate the .i file was:

cl -P -DWIN32 -DNULL=0 -D_MT -D_DLL -WX -DHAVE_CONFIG_H /I. /I..
/I../wiretap /IC:\wireshark-win32-lib
s-new\glib\include\glib-2.0
/IC:\wireshark-win32-libs-new\glib\lib\glib-2.0\include
/IC:\wireshark-w
in32-libs-new\zlib123-dll\include
/IC:\wireshark-win32-libs-new\adns-1.0-win32-05\src /IC:\wireshark-w
in32-libs-new\adns-1.0-win32-05\adns_win32
/IC:\wireshark-win32-libs-new\pcre-6.4\include /IC:\wiresha
rk-win32-libs-new\gnutls-1.6.1-1\include /DNOCRYPT
/IC:\wireshark-win32-libs-new\WPdpack\include -D_U_
="" /Zi /W3 /MD -Fd.\ -c filesystem.c

Notice, I use a "non-standard" library directory (to keep 0.99.4 and
0.99.6 separate).

I did update my cygwin installation and I the above versions are from
running
nmake -f Makefile.nmake setup.

When the command above was executed the following error was given:

C:\wireshark-0.99.6\epan>cl -P -DWIN32 -DNULL=0 -D_MT -D_DLL -WX
-DHAVE_CONFIG_H /I. /I.. /I../wiretap
 /IC:\wireshark-win32-libs-new\glib\include\glib-2.0
/IC:\wireshark-win32-libs-new\glib\lib\glib-2.0\
include  /IC:\wireshark-win32-libs-new\zlib123-dll\include
/IC:\wireshark-win32-libs-new\adns-1.0-win3
2-05\src /IC:\wireshark-win32-libs-new\adns-1.0-win32-05\adns_win32
/IC:\wireshark-win32-libs-new\pcre
-6.4\include /IC:\wireshark-win32-libs-new\gnutls-1.6.1-1\include
/DNOCRYPT /IC:\wireshark-win32-libs-
new\WPdpack\include -D_U_="" /Zi /W3 /MD -Fd.\ -c filesystem.c
Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 12.00.8168 for
80x86
Copyright (C) Microsoft Corp 1984-1998. All rights reserved.

filesystem.c
C:\PROGRA~1\MICROS~3\VC98\INCLUDE\exdisp.h(3766) : fatal error C1070:
mismatched #if/#endif pair in fi
le 'C:\PROGRA~1\MICROS~3\VC98\INCLUDE\exdisp.h'

The file date is consistent with all of the other files in the
directory.
24/04/1998 so it hasn't been modified.

The file appears to have a mismatched "#endif" at line 1446.
1446:#endif     /* __FolderItemVerbs_INTERFACE_DEFINED__ */

I think the file is syntactically incorrect but has been this way
forever.

Any ideas what libraries/environment I have would cause a different
conditional compile
compared to everybody else?

Thanks 
 
--
Michael Lum                   Principal Software Engineer
4600 Jacombs Road             +1.604.276.0055
Richmond, B.C.
Canada V6V 3B1
UTStarcom Canada, Inc.
CDMA Division
 

> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of 
> Graham Bloice
> Sent: October 8, 2007 8:46 AM
> To: Developer support list for Wireshark
> Subject: Re: [Wireshark-dev] 0.99.6 build problems on Windows
> 
> Michael Lum wrote:
> > I updated my cygwin installation but that didn't help.
> >
> > I followed the link for the MS Platform SDK but it states VC 6.0 is 
> > not
> > supported:
> >
> > Development Tools. To build the C/C++ samples, you must 
> have a C/C++ 
> > compiler. If you are using Microsoft Visual C/C++(r), run 
> it at least 
> > once before installing the SDK. This will ensure that the 
> environment 
> > variables are correctly configured. To build the Visual 
> Basic samples, 
> > you must have Microsoft Visual Basic(r). This SDK does not support 
> > working with Microsoft Visual C/C++(r), 6.0 as support for 
> VC 6.0 has 
> > ended. The last SDK that will work with VC 6.0 is the February 2003 
> > Edition, you can order a CD on the fulfillment site. Side by side 
> > installations are not supported.
> >
> > So unfortunately I'm still stuck.
> > I have tried, clean, distclean, setup, all, again but to no avail.
> >
> >   
> OK, so we really need some more clues about the compilation 
> errors.  You can try getting the output from the preprocessor 
> to see if that gives any more clues.  Be aware the output is 
> massive, consisting mostly of blank lines, but might help you out.
> 
> 1.  cd into the epan dir and compile filesystem.c on its own 
> with "nmake makefile.nmake filesystem.obj"
> 2.  Copy the compiler invocation emitted by nmake and paste 
> it back into your command prompt, but tack a "-P" on the end 
> 3.  This should produce a filesystem.i for your perusal.  Good luck.
> 
> --
> Regards,
> 
> Graham Bloice
> 
> _______________________________________________
> Wireshark-dev mailing list
> [email protected]
> http://www.wireshark.org/mailman/listinfo/wireshark-dev
>