sagar Guledagudda skrev 2011-08-03 06:59:
What are those local changes i suppose to do ???
Packages: zlib125ws.zip
Location: http://www.gzip.org/zlib/
Description: The zlib compression library (source and DLL versions)
License: zlib/libpng
Local changes:
From http://www.apachehaus.com/forum/index.php?action=printpage;topic=143.0
First problem: ZLIB build must be fixed for x64, otherwise there will be
one unresolved external symbol later.
Quick fix is to open build\win32\build_zlib.bat and insert this at line 51:
set ASM_OPTS=AS=ml64 LOC="-DASMV -DASMINF" OBJA="inffasx64.obj
gvmat64.obj inffas8664.obj"
(info found in zlib\win32\Makefile.msc) and then open
zlib\contrib\masmx64\inffas8664.c and prepend "../../" to four includes
at the beginning
On Mon, Aug 1, 2011 at 12:55 PM, Anders Broman
<anders.bro...@ericsson.com <mailto:anders.bro...@ericsson.com>> wrote:
Hi,
Did you download the suport libraries? We have local changes to
Zlib I think. If you did try forcing rebuild of zlib by deleteing
the temp build dir for zlib.
Regards
Anders
------------------------------------------------------------------------
*From:* wireshark-dev-boun...@wireshark.org
<mailto:wireshark-dev-boun...@wireshark.org>
[mailto:wireshark-dev-boun...@wireshark.org
<mailto:wireshark-dev-boun...@wireshark.org>] *On Behalf Of *sagar
Guledagudda
*Sent:* den 1 augusti 2011 09:12
*To:* Developer support list for Wireshark
*Subject:* Re: [Wireshark-dev] wireshark on 64 bit
i have done all those things. after that i am getting that linker
error "unresolved external inflate_fast"
On Mon, Aug 1, 2011 at 12:12 PM, Anders Broman
<anders.bro...@ericsson.com <mailto:anders.bro...@ericsson.com>>
wrote:
See
http://wiki.wireshark.org/Development/Win64
more specificly:
echo Setting up Visual Studio environment...
call "c:\Program Files\Microsoft Visual Studio
9.0\VC\vcvarsall.bat" x86_amd64
Regards
Anders
------------------------------------------------------------------------
*From:* wireshark-dev-boun...@wireshark.org
<mailto:wireshark-dev-boun...@wireshark.org>
[mailto:wireshark-dev-boun...@wireshark.org
<mailto:wireshark-dev-boun...@wireshark.org>] *On Behalf Of
*sagar Guledagudda
*Sent:* den 1 augusti 2011 07:35
*To:* Developer support list for Wireshark
*Subject:* Re: [Wireshark-dev] wireshark on 64 bit
Yes i did that. i think this might be the problem with the
gtk library . i am using the gtk
package*gtk+-bundle_2.16.6-20100208_win6*4 . Is that a right
one or we need to use any other version specifically for 64 bit.?
Thanks
Sags
On Sat, Jul 30, 2011 at 1:15 AM, wsgd <w...@free.fr
<mailto:w...@free.fr>> wrote:
Did you specify a parameter to say you want to produce 64
bits when calling vcvarsall.bat ?
For VC++ 2008 EE on 64 bits windows, I use :
"C:\Program Files (x86)\Microsoft Visual Studio
9.0\VC\bin\vcvars64.bat"
Olivier
Le 29/07/2011 09:40, sagar Guledagudda a écrit :
hi,
I am trying to compile the wireshark for target platform
for 64 bit.
When i do *nmake makefile.nmake *i get fallowing errror
file_util.obj : fatal error LNK1112: module machine type
'X86' conflicts with ta
rget machine type 'x64'
NMAKE : fatal error U1077: '"c:\Program Files\Microsoft
Visual Studio 8\VC\BIN\x
86_amd64\link.EXE"' : return code '0x458'
i am using microsoft visual studio 2005.
I have changed WIRESHARK_TARGET_PLATFORM to win64.
and ran the batch file c:\Program Files\Microsoft Visual
Studio 8\VC\vcvarsall.bat before doing any operation on
wireshark.
can any body help me to solve this issue ???
Is that problem with visual studio i am using ???
___________________________________________________________________________
Sent via: Wireshark-dev mailing list<wireshark-dev@wireshark.org>
<mailto: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
--
Wireshark Generic Dissectorhttp://wsgd.free.fr <http://wsgd.free.fr/>
___________________________________________________________________________
Sent via: Wireshark-dev mailing list
<wireshark-dev@wireshark.org
<mailto: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
<mailto:wireshark-dev-requ...@wireshark.org>?subject=unsubscribe
___________________________________________________________________________
Sent via: Wireshark-dev mailing list
<wireshark-dev@wireshark.org <mailto: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
<mailto:wireshark-dev-requ...@wireshark.org>?subject=unsubscribe
___________________________________________________________________________
Sent via: Wireshark-dev mailing list
<wireshark-dev@wireshark.org <mailto: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
<mailto:wireshark-dev-requ...@wireshark.org>?subject=unsubscribe
___________________________________________________________________________
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
___________________________________________________________________________
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
