2012/12/3 cheer_zeng <cheer_z...@163.com> > ** > Hello > My system is 64-bit win7 ,and I follow the "wireshark develop guide > ---Win32 :Step-by-step" ( > http://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html) to set > up the environment .But I fail at the 2.2.10 Build Wireshark ,after i call " > *nmake -f Makefile.nmake all*" ,comes the error message : > > * **link -nologo -debug -incremental:no -opt:ref > -def:win32/zlib.def -dll -i > mplib:zdll.lib -out:zlib1.dll -base:0x5A4C0000 adler32.obj compress.obj > crc32.o > bj deflate.obj gzclose.obj gzlib.obj gzread.obj gzwrite.obj infback.obj > inflate > .obj inftrees.obj trees.obj uncompr.obj zutil.obj inffas32.obj > match686.obj zlib > 1.res > inffas32.obj : fatal error LNK1112: module machine type 'X86' conflicts > with tar > get machine type 'x64' > NMAKE : fatal error U1077: '"c:\Program Files (x86)\Microsoft Visual > Studio 10.0 > \VC\Bin\amd64\link.EXE"' : return code '0x458' > Stop. > NMAKE : fatal error U1077: '"c:\Program Files (x86)\Microsoft Visual > Studio 10.0 > \VC\Bin\amd64\nmake.exe"' : return code '0x2' > Stop.* > ** > I use "setenv /Release /x64 /win7" in the windows SDK 7.1 Command Prompt > to set environment variables for Visual C++ 2010 Express Edition,as i > don;t have vcvars64.bat in the amd64 directory descript in vcvarsall.dll > > Then what should i do to correct the error? > > > as i am not new to this,so hope you all can help me. > Thank you !! >
Hi, if you want to build a 64 bits Wirehshark, you must also change WIRESHARK_TARGET_PLATFORM from win32 to win64 (either by setting an environment variable or by editing config.nmake file). Then you must do nmake -f Makefile.nmake setup once to download the win64 packages (you probably downloaded the 32 bits packages). Regards, Pascal.
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe