How can I compile Wireshark 1.2.9 successfully?
In Windows XP, I executed nmake -f Makefile.nmake all
, but I get the following errors:
packet-ipmi-bridge.c
packet-ipmi-chassis.c
packet-ipmi-picmg.c
packet-ipmi-se.c
packet-ipmi-storage.c
packet-ipmi-transport.c
Generating Code...
Compiling...
packet-ipmi-pps.c
packet-ipmi-update.c
packet-dcerpc-nt.c
Generating Code...
NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio\VC98\bin\c
l.exe"' : return code '0x2'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio\VC98\bin\N
MAKE.EXE"' : return code '0x2'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio\VC98\bin\N
MAKE.EXE"' : return code '0x2'
Stop.
asked 10 Sep '11, 02:17
ylda_ljm0620
31●10●10●13
accept rate: 0%
edited 11 Sep '11, 13:05
helloworld
3.1k●4●20●41
You'll need to provide the output from prior to the above for us to provide any help..
At some point prior to the above messages there was a compile error which eventually caused a delayed exit with the messages shown above.
P.S. Why Wireshark 1.2.9 ? That version is old and not actuallysupported anymore.
because wireshark1.2.9 just satisfy our needs, when tshark convert pcap to text, SMV remain original hex, we hope ourselves to dissect the SMV for higher efficiency. but wireshark1.2.9(as any vertion), it's tshark can not dissect mms when mms is not begining with initiate. so we try to develop wireshark1.2.9.
now, I compile wireshark1.2.9 in windows XP, My complier is Visual studio 6.0.
After nmake -f Makefile verify_tools, what appears as follows:
finally, nmake -f Makefile.nmake all, errors as follws:
It seems the error must have occurred even before the text posted.
In any case, you’re using VC6 to do the build.
VC6 certainly isn’t supported for building Wireshark 1.2.9. (I suppose that it’s possible to fix whatever is causing the problem when using VC6 but it isn’t worth the effort). :)
I suggest downloading/installing Microsoft VC2008EE (free); that’s the VC version used to build Windows Wireshark 1.2.9.
I’m not sure I understand your reason for using 1.2.9. Building with the the latest 1.4 or 1.6 source, will make it easier for us to help with any problems you may encounter,
Tanks very much. I have downloaded VS2008EE and installed, but new errors happened.
finally, nmake -f Makefile.nmake all, errors appears as follows:
in addition, I will tell you the reason to use wireshark1.2.9.
first, wireshark of any vertion can not dissect mms what is not begining with Initiate, so i try to develop the wireshark to solve the problem. not like mms-ethereal, even mms-ethereal start after Initiate(you known, just as Initiate-request, Initiate-response) ,It can dissect the mms. but the wireshark show “dissctor is not available” near by ASN1.type.
second, I think to dissect the 61850 SMV by myself for higher Efficiency. the tshark(covert pcap to text) of wireshark1.2.9 just remain 61850 SMV hex in text file. but the tshark(covert pcap to text) of wireshark 1.6 have dissected the 61850 SM.
which vertion wireshark can solve the problem?
in addition, i whill farther explain why i use wireshark1.2.9 to develop.
It is that we have used thark of wireshark1.2.9 to convert pcap to text, and we read the text and further dissect the text to other application.
different vertion of wireshark thark to text, the 61850SMV and 61850GOOSE int text have different format. so we had better not to change wireshark vertion.
Bill Meier, Thanks.
I am very anxious and will waiting for your answer online. Please help me.
Re: cl.EXE"’ : return code ‘0xc0000135’
A Google search suggests this is caused by some type of setup problem.
Are you following the instructions (exactly) in the Wireshark Developer’s Guide section: Win32: Step-by-Step Guide? http://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html
What is your PATH ? Are you doing call “c:Program FilesMicrosoft Visual Studio 9.0VCbinvcvars32.bat” as described in the Guide ?
re: the questions about issues with dissecting mms and 61850 SMV and asking “which vertion wireshark can solve the problem?"
I’ve no knowledge of these protocols.
I suggest posting this question on the wireshark-dev mailing list: See: http://www.wireshark.org/lists/
ask.wireshark.org is not really intended for extended discussions so I also suggest posting (separately) on wireshark-dev any further issues about building Wireshark. (You can link to this ask.wireshark.org question if needed).
Thanks
Thanks. it compiled successfully.
the reason of compiling is that i called the vcvar32.bat and nmake in two different cmd-window.
if calling them in the same cmd-window, and firstly calling vcvar32.bat, then calling nmake, it will success.