Re: [Wireshark-dev] packet-mpeg-pes.c. compiling fail on win32
Hi, This is due to a bug in the sourcecode of the MPEG-PES dissector. It originates in r26328, which added a bugfix to the generated code with the use of 'illegal' characters in the comment block. Currently the bugfix is dropped since it was never added to the ASN.1 dissector template, hence has been lost with the new generation of this code. Anders, could you: 1. Make the appropriate changes to the dissectors ASN1 template. 2. Remove the illegal quote characters from the comment block. 3. Add the changes to template and generated code to the 1.0.8 roadmap. Patrick, you can fix this by removing the illegal characters from start of line 853 and end of line 855 in packet-mpeg-pes.c. Thanx, Jaap Yan, Patrick (NSN - CN/Beijing) wrote: Hi all, OS is windows XP, wireshark source code is last version of wireshark-1.0.7. Checking for required applications: cl: /cygdrive/c/Program Files/Microsoft Visual Studio 9.0/VC/BIN/cl link: /cygdrive/c/Program Files/Microsoft Visual Studio 9.0/VC/BIN/link nmake: /cygdrive/c/Program Files/Microsoft Visual Studio 9.0/VC/BIN/nmake bash: /usr/bin/bash bison: /usr/bin/bison flex: /usr/bin/flex env: /usr/bin/env grep: /usr/bin/grep /usr/bin/find: /usr/bin/find perl: /usr/bin/perl C:\Python26\python.exe: /cygdrive/c/Python26/python.exe sed: /usr/bin/sed unzip: /usr/bin/unzip wget: /usr/bin/wget During compiling, some problem met. Anyone can help to resolve this problem. Thanks. Generating Code... Compiling... packet-h460.c packet-h501.c packet-inap.c packet-ldap.c packet-logotypecertextn.c packet-mms.c packet-mpeg-audio.c packet-mpeg-pes.c packet-mpeg-pes-template.c(300) : error C2220: warning treated as error - no 'ob ject' file generated packet-mpeg-pes-template.c(300) : warning C4819: The file contains a character t hat cannot be represented in the current code page (936). Save the file in Unico de format to prevent data loss packet-nbap.c packet-ns_cert_exts.c packet-ocsp.c packet-p7.c packet-pcap.c packet-pkcs12.c packet-pkcs1.c packet-pkinit.c packet-pkix1explicit.c packet-pkix1implicit.c packet-pkixproxy.c packet-pkixqualified.c Generating Code... Compiling... packet-pkixtsp.c packet-pres.c packet-q932.c packet-q932-ros.c packet-qsig.c packet-ranap.c packet-rnsap.c packet-ros.c packet-rrlp.c packet-rtse.c packet-s1ap.c packet-s4406.c packet-sabp.c packet-smrse.c packet-snmp.c packet-spnego.c packet-t125.c packet-tcap.c packet-ulp.c packet-wlancertextn.c Generating Code... Compiling... packet-x2ap.c packet-x224.c packet-x411.c packet-x420.c packet-x509af.c packet-x509ce.c packet-x509if.c packet-x509sat.c packet-dcerpc-nt.c Generating Code... NMAKE : fatal error U1077: 'C:\Program Files\Microsoft Visual Studio 9.0\VC\BIN \cl.EXE' : return code '0x2' Stop. NMAKE : fatal error U1077: 'C:\Program Files\Microsoft Visual Studio 9.0\VC\BIN \nmake.exe' : return code '0x2' Stop. NMAKE : fatal error U1077: 'C:\Program Files\Microsoft Visual Studio 9.0\VC\BIN \nmake.exe' : return code '0x2' Stop. Best Regards Patrick ___ 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
Re: [Wireshark-dev] packet-mpeg-pes.c. compiling fail on win32
Hi Gurus, It works! Thanks! After compiling, I met other question. When I run wireshark.exe, the output messages is; This application has failed to start because wiretap-0.3.1.dll was not found. Re-installing the application may fix this problem Can I copy a wiretap-0.3.1.dll to wireshark directory? Br-Patrick -Original Message- From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of ext Jaap Keuter Sent: Thursday, April 30, 2009 3:41 PM To: Developer support list for Wireshark; Anders Broman Subject: Re: [Wireshark-dev] packet-mpeg-pes.c. compiling fail on win32 Hi, This is due to a bug in the sourcecode of the MPEG-PES dissector. It originates in r26328, which added a bugfix to the generated code with the use of 'illegal' characters in the comment block. Currently the bugfix is dropped since it was never added to the ASN.1 dissector template, hence has been lost with the new generation of this code. Anders, could you: 1. Make the appropriate changes to the dissectors ASN1 template. 2. Remove the illegal quote characters from the comment block. 3. Add the changes to template and generated code to the 1.0.8 roadmap. Patrick, you can fix this by removing the illegal characters from start of line 853 and end of line 855 in packet-mpeg-pes.c. Thanx, Jaap Yan, Patrick (NSN - CN/Beijing) wrote: Hi all, OS is windows XP, wireshark source code is last version of wireshark-1.0.7. Checking for required applications: cl: /cygdrive/c/Program Files/Microsoft Visual Studio 9.0/VC/BIN/cl link: /cygdrive/c/Program Files/Microsoft Visual Studio 9.0/VC/BIN/link nmake: /cygdrive/c/Program Files/Microsoft Visual Studio 9.0/VC/BIN/nmake bash: /usr/bin/bash bison: /usr/bin/bison flex: /usr/bin/flex env: /usr/bin/env grep: /usr/bin/grep /usr/bin/find: /usr/bin/find perl: /usr/bin/perl C:\Python26\python.exe: /cygdrive/c/Python26/python.exe sed: /usr/bin/sed unzip: /usr/bin/unzip wget: /usr/bin/wget During compiling, some problem met. Anyone can help to resolve this problem. Thanks. Generating Code... Compiling... packet-h460.c packet-h501.c packet-inap.c packet-ldap.c packet-logotypecertextn.c packet-mms.c packet-mpeg-audio.c packet-mpeg-pes.c packet-mpeg-pes-template.c(300) : error C2220: warning treated as error - no 'ob ject' file generated packet-mpeg-pes-template.c(300) : warning C4819: The file contains a character t hat cannot be represented in the current code page (936). Save the file in Unico de format to prevent data loss packet-nbap.c packet-ns_cert_exts.c packet-ocsp.c packet-p7.c packet-pcap.c packet-pkcs12.c packet-pkcs1.c packet-pkinit.c packet-pkix1explicit.c packet-pkix1implicit.c packet-pkixproxy.c packet-pkixqualified.c Generating Code... Compiling... packet-pkixtsp.c packet-pres.c packet-q932.c packet-q932-ros.c packet-qsig.c packet-ranap.c packet-rnsap.c packet-ros.c packet-rrlp.c packet-rtse.c packet-s1ap.c packet-s4406.c packet-sabp.c packet-smrse.c packet-snmp.c packet-spnego.c packet-t125.c packet-tcap.c packet-ulp.c packet-wlancertextn.c Generating Code... Compiling... packet-x2ap.c packet-x224.c packet-x411.c packet-x420.c packet-x509af.c packet-x509ce.c packet-x509if.c packet-x509sat.c packet-dcerpc-nt.c Generating Code... NMAKE : fatal error U1077: 'C:\Program Files\Microsoft Visual Studio 9.0\VC\BIN \cl.EXE' : return code '0x2' Stop. NMAKE : fatal error U1077: 'C:\Program Files\Microsoft Visual Studio 9.0\VC\BIN \nmake.exe' : return code '0x2' Stop. NMAKE : fatal error U1077: 'C:\Program Files\Microsoft Visual Studio 9.0\VC\BIN \nmake.exe' : return code '0x2' Stop. Best Regards Patrick ___ 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
[Wireshark-dev] Include or makefile problems
Hi all, I'm working on a project since a month which aims to auto-select a packet in a second Wireshark instance depending on the packet selected in the first instance and on some abbrev given (like tcp.dstport, ip.id ...) I added a .h and a .c in /gtk and referenced them in gtk/Makefile.common. Those files contains some functions for the dialog box used and a function which read in a named pipe informations sent from the first instance of Wireshark. (let's call them file1.h and file1.c) At the moment, when I select a row in the first Wireshark instance, the same row number is automatically selected in the second Wireshark instance. Here is my problem : In the function which read the pipe, I need to get the length of a ftype using 'int ftype_length(ftenum_t ftype)' declared in epan/ftypes/ftypes.h When I simply include epan/ftypes/ftypes.h in file1.h or file.c, it compile everything but fails when linking wireshark.exe. If I add ftypes.h (../epan/ftypes/ftypes.h) and .c in gtk/Makefile.common I get the same error : Linking wireshark.exe link @C:\DOCUME~1\redkite\LOCALS~1\Temp\nm124.tmp libui.lib(pcapd_dlg.obj) : error LNK2019: unresolved external symbol _ftype_leng th referenced in function _read_pipe_cb wireshark.exe : fatal error LNK1120: 1 unresolved externals I saw that in gtk/io_stat.c, they are using function from ftypes.h too but even with all same include it doesn't work.(stupid reaction,but I was going crazy :-s) It is the first time I work on a so wide project (it's an internship work) and I don't know how I m supposed to make it recognized. I've read most of dev posts since I started this project, I know you could help me :-) Thanks in advance for your replies, -Gauthier ___ 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
Re: [Wireshark-dev] Compilation errors while building the Wireshark sources
No luck so far. I've re-downloaded the sources using TortoiseSVN and compilation again fails in the exact same place. Any suggestions? On Wed, Apr 29, 2009 at 9:14 AM, Jaap Keuter jaap.keu...@xs4all.nl wrote: Hi, Well, he's building the 1.1.4 development version, so 2008 should be fine. It seems that you've a botched tarball or working copy, since little has changed in this area for a long time. Try downloading a new tarball or revert changes in the working copy and start from the current head of development. Thanx, Jaap Rohan Solanki wrote: hi, I think you should try building wireshark with visual studio 2005. Also Make appropriate changes in the config.nmake file. I also had problems with visual studio 2008. I have successfully build and running wireshark 1.0.5 with visual studio 2005. Rohan. On Tue, Apr 28, 2009 at 7:19 PM, Anonymous Anonymous a.master.blas...@gmail.com mailto:a.master.blas...@gmail.com wrote: Hi everyone, I'm new to the Wireshark development process and I'm having some building issues I hope you will be able to solve. Ok, so here it comes. I've followed the developers manual step-by-step and everything worked out fine until I had to issue the command name Makefile.namke all. For some unknown reason this command seems to fail over and over again. The relevant output lines I managed to extract from the console are as follows: /*dissectors.lib(packet-ncp-sss.obj) : error LNK2001: unresolved external symbol _ ett_nds libwireshark.dll : fatal error LNK1120: 1 unresolved externals NMAKE : fatal error U1077: 'C:\Program Files\Microsoft Visual Studio 9.0\VC\BIN \link.EXE' : return code '0x460' Stop. NMAKE : fatal error U1077: 'C:\Program Files\Microsoft Visual Studio 9.0\VC\BIN \nmake.exe' : return code '0x2' Stop. */The same output also appears when I'm trying to build the .sln file provided is the sources using VC++ 2008 Express Edition. Can someone point out what the problem is? Thanks in advance. Any help will be deeply appreciated. My building environment specs: OS - Microsoft Windows XP SP3 IDE - Microsoft Visual C++ 2008 Express Edition SVN - TortoiseSVN Wireshark version - 1.1.4.0 (version info was taken from the config.nmake file) ___ 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
Re: [Wireshark-dev] Include or makefile problems
Hi, Add ftype_length to epan/libwireshark.def. It's a Windows thing which it needs to export functions from the DLL to other libraries. Thanx, Jaap Gauthier Brion wrote: Hi all, I'm working on a project since a month which aims to auto-select a packet in a second Wireshark instance depending on the packet selected in the first instance and on some abbrev given (like tcp.dstport, ip.id http://ip.id ...) I added a .h and a .c in /gtk and referenced them in gtk/Makefile.common. Those files contains some functions for the dialog box used and a function which read in a named pipe informations sent from the first instance of Wireshark. (let's call them file1.h and file1.c) At the moment, when I select a row in the first Wireshark instance, the same row number is automatically selected in the second Wireshark instance. Here is my problem : In the function which read the pipe, I need to get the length of a ftype using 'int ftype_length(ftenum_t ftype)' declared in epan/ftypes/ftypes.h When I simply include epan/ftypes/ftypes.h in file1.h or file.c, it compile everything but fails when linking wireshark.exe. If I add ftypes.h (../epan/ftypes/ftypes.h) and .c in gtk/Makefile.common I get the same error : Linking wireshark.exe link @C:\DOCUME~1\redkite\LOCALS~1\Temp\nm124.tmp libui.lib(pcapd_dlg.obj) : error LNK2019: unresolved external symbol _ftype_leng th referenced in function _read_pipe_cb wireshark.exe : fatal error LNK1120: 1 unresolved externals I saw that in gtk/io_stat.c, they are using function from ftypes.h too but even with all same include it doesn't work.(stupid reaction,but I was going crazy :-s) It is the first time I work on a so wide project (it's an internship work) and I don't know how I m supposed to make it recognized. I've read most of dev posts since I started this project, I know you could help me :-) Thanks in advance for your replies, -Gauthier ___ 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
Re: [Wireshark-dev] Compilation errors while building the Wireshark sources
Did you try nmake -f makefile.nmake distclean nmake -f makefile.nmake all This has often worked for me in similar situations. On Thu, Apr 30, 2009 at 3:08 PM, Anonymous Anonymous a.master.blas...@gmail.com wrote: No luck so far. I've re-downloaded the sources using TortoiseSVN and compilation again fails in the exact same place. Any suggestions? On Wed, Apr 29, 2009 at 9:14 AM, Jaap Keuter jaap.keu...@xs4all.nlwrote: Hi, Well, he's building the 1.1.4 development version, so 2008 should be fine. It seems that you've a botched tarball or working copy, since little has changed in this area for a long time. Try downloading a new tarball or revert changes in the working copy and start from the current head of development. Thanx, Jaap Rohan Solanki wrote: hi, I think you should try building wireshark with visual studio 2005. Also Make appropriate changes in the config.nmake file. I also had problems with visual studio 2008. I have successfully build and running wireshark 1.0.5 with visual studio 2005. Rohan. On Tue, Apr 28, 2009 at 7:19 PM, Anonymous Anonymous a.master.blas...@gmail.com mailto:a.master.blas...@gmail.com wrote: Hi everyone, I'm new to the Wireshark development process and I'm having some building issues I hope you will be able to solve. Ok, so here it comes. I've followed the developers manual step-by-step and everything worked out fine until I had to issue the command name Makefile.namke all. For some unknown reason this command seems to fail over and over again. The relevant output lines I managed to extract from the console are as follows: /*dissectors.lib(packet-ncp-sss.obj) : error LNK2001: unresolved external symbol _ ett_nds libwireshark.dll : fatal error LNK1120: 1 unresolved externals NMAKE : fatal error U1077: 'C:\Program Files\Microsoft Visual Studio 9.0\VC\BIN \link.EXE' : return code '0x460' Stop. NMAKE : fatal error U1077: 'C:\Program Files\Microsoft Visual Studio 9.0\VC\BIN \nmake.exe' : return code '0x2' Stop. */The same output also appears when I'm trying to build the .sln file provided is the sources using VC++ 2008 Express Edition. Can someone point out what the problem is? Thanks in advance. Any help will be deeply appreciated. My building environment specs: OS - Microsoft Windows XP SP3 IDE - Microsoft Visual C++ 2008 Express Edition SVN - TortoiseSVN Wireshark version - 1.1.4.0 (version info was taken from the config.nmake file) ___ 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 ___ 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
Re: [Wireshark-dev] Include or makefile problems
Thanks a lot Jaap, it works ! I never noticed those file .def, it will resolve some of my troubles. Thanks again, -Gauthier -Original Message- From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Jaap Keuter Sent: 2009-04-30 12:59 To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] Include or makefile problems Hi, Add ftype_length to epan/libwireshark.def. It's a Windows thing which it needs to export functions from the DLL to other libraries. Thanx, Jaap Gauthier Brion wrote: Hi all, I'm working on a project since a month which aims to auto-select a packet in a second Wireshark instance depending on the packet selected in the first instance and on some abbrev given (like tcp.dstport, ip.id http://ip.id ...) I added a .h and a .c in /gtk and referenced them in gtk/Makefile.common. Those files contains some functions for the dialog box used and a function which read in a named pipe informations sent from the first instance of Wireshark. (let's call them file1.h and file1.c) At the moment, when I select a row in the first Wireshark instance, the same row number is automatically selected in the second Wireshark instance. Here is my problem : In the function which read the pipe, I need to get the length of a ftype using 'int ftype_length(ftenum_t ftype)' declared in epan/ftypes/ftypes.h When I simply include epan/ftypes/ftypes.h in file1.h or file.c, it compile everything but fails when linking wireshark.exe. If I add ftypes.h (../epan/ftypes/ftypes.h) and .c in gtk/Makefile.common I get the same error : Linking wireshark.exe link @C:\DOCUME~1\redkite\LOCALS~1\Temp\nm124.tmp libui.lib(pcapd_dlg.obj) : error LNK2019: unresolved external symbol _ftype_leng th referenced in function _read_pipe_cb wireshark.exe : fatal error LNK1120: 1 unresolved externals I saw that in gtk/io_stat.c, they are using function from ftypes.h too but even with all same include it doesn't work.(stupid reaction,but I was going crazy :-s) It is the first time I work on a so wide project (it's an internship work) and I don't know how I m supposed to make it recognized. I've read most of dev posts since I started this project, I know you could help me :-) Thanks in advance for your replies, -Gauthier ___ 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
Re: [Wireshark-dev] packet-mpeg-pes.c. compiling fail on win32
Hi, Thanks again;) Br-Patrick -Original Message- From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of ext Jaap Keuter Sent: Thursday, April 30, 2009 4:58 PM To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] packet-mpeg-pes.c. compiling fail on win32 Hi, When you want to run it from the build environment you'll have to go into the gtk2 build directory and run from there. Thanx, Jaap Yan, Patrick (NSN - CN/Beijing) wrote: Hi Gurus, It works! Thanks! After compiling, I met other question. When I run wireshark.exe, the output messages is; This application has failed to start because wiretap-0.3.1.dll was not found. Re-installing the application may fix this problem Can I copy a wiretap-0.3.1.dll to wireshark directory? Br-Patrick -Original Message- From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of ext Jaap Keuter Sent: Thursday, April 30, 2009 3:41 PM To: Developer support list for Wireshark; Anders Broman Subject: Re: [Wireshark-dev] packet-mpeg-pes.c. compiling fail on win32 Hi, This is due to a bug in the sourcecode of the MPEG-PES dissector. It originates in r26328, which added a bugfix to the generated code with the use of 'illegal' characters in the comment block. Currently the bugfix is dropped since it was never added to the ASN.1 dissector template, hence has been lost with the new generation of this code. Anders, could you: 1. Make the appropriate changes to the dissectors ASN1 template. 2. Remove the illegal quote characters from the comment block. 3. Add the changes to template and generated code to the 1.0.8 roadmap. Patrick, you can fix this by removing the illegal characters from start of line 853 and end of line 855 in packet-mpeg-pes.c. Thanx, Jaap Yan, Patrick (NSN - CN/Beijing) wrote: Hi all, OS is windows XP, wireshark source code is last version of wireshark-1.0.7. Checking for required applications: cl: /cygdrive/c/Program Files/Microsoft Visual Studio 9.0/VC/BIN/cl link: /cygdrive/c/Program Files/Microsoft Visual Studio 9.0/VC/BIN/link nmake: /cygdrive/c/Program Files/Microsoft Visual Studio 9.0/VC/BIN/nmake bash: /usr/bin/bash bison: /usr/bin/bison flex: /usr/bin/flex env: /usr/bin/env grep: /usr/bin/grep /usr/bin/find: /usr/bin/find perl: /usr/bin/perl C:\Python26\python.exe: /cygdrive/c/Python26/python.exe sed: /usr/bin/sed unzip: /usr/bin/unzip wget: /usr/bin/wget During compiling, some problem met. Anyone can help to resolve this problem. Thanks. Generating Code... Compiling... packet-h460.c packet-h501.c packet-inap.c packet-ldap.c packet-logotypecertextn.c packet-mms.c packet-mpeg-audio.c packet-mpeg-pes.c packet-mpeg-pes-template.c(300) : error C2220: warning treated as error - no 'ob ject' file generated packet-mpeg-pes-template.c(300) : warning C4819: The file contains a character t hat cannot be represented in the current code page (936). Save the file in Unico de format to prevent data loss packet-nbap.c packet-ns_cert_exts.c packet-ocsp.c packet-p7.c packet-pcap.c packet-pkcs12.c packet-pkcs1.c packet-pkinit.c packet-pkix1explicit.c packet-pkix1implicit.c packet-pkixproxy.c packet-pkixqualified.c Generating Code... Compiling... packet-pkixtsp.c packet-pres.c packet-q932.c packet-q932-ros.c packet-qsig.c packet-ranap.c packet-rnsap.c packet-ros.c packet-rrlp.c packet-rtse.c packet-s1ap.c packet-s4406.c packet-sabp.c packet-smrse.c packet-snmp.c packet-spnego.c packet-t125.c packet-tcap.c packet-ulp.c packet-wlancertextn.c Generating Code... Compiling... packet-x2ap.c packet-x224.c packet-x411.c packet-x420.c packet-x509af.c packet-x509ce.c packet-x509if.c packet-x509sat.c packet-dcerpc-nt.c Generating Code... NMAKE : fatal error U1077: 'C:\Program Files\Microsoft Visual Studio 9.0\VC\BIN \cl.EXE' : return code '0x2' Stop. NMAKE : fatal error U1077: 'C:\Program Files\Microsoft Visual Studio 9.0\VC\BIN \nmake.exe' : return code '0x2' Stop. NMAKE : fatal error U1077: 'C:\Program Files\Microsoft Visual Studio 9.0\VC\BIN \nmake.exe' : return code '0x2' Stop. Best Regards Patrick ___ 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:
Re: [Wireshark-dev] packet-mpeg-pes.c. compiling fail on win32
Hi, When you want to run it from the build environment you'll have to go into the gtk2 build directory and run from there. Thanx, Jaap Yan, Patrick (NSN - CN/Beijing) wrote: Hi Gurus, It works! Thanks! After compiling, I met other question. When I run wireshark.exe, the output messages is; This application has failed to start because wiretap-0.3.1.dll was not found. Re-installing the application may fix this problem Can I copy a wiretap-0.3.1.dll to wireshark directory? Br-Patrick -Original Message- From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of ext Jaap Keuter Sent: Thursday, April 30, 2009 3:41 PM To: Developer support list for Wireshark; Anders Broman Subject: Re: [Wireshark-dev] packet-mpeg-pes.c. compiling fail on win32 Hi, This is due to a bug in the sourcecode of the MPEG-PES dissector. It originates in r26328, which added a bugfix to the generated code with the use of 'illegal' characters in the comment block. Currently the bugfix is dropped since it was never added to the ASN.1 dissector template, hence has been lost with the new generation of this code. Anders, could you: 1. Make the appropriate changes to the dissectors ASN1 template. 2. Remove the illegal quote characters from the comment block. 3. Add the changes to template and generated code to the 1.0.8 roadmap. Patrick, you can fix this by removing the illegal characters from start of line 853 and end of line 855 in packet-mpeg-pes.c. Thanx, Jaap Yan, Patrick (NSN - CN/Beijing) wrote: Hi all, OS is windows XP, wireshark source code is last version of wireshark-1.0.7. Checking for required applications: cl: /cygdrive/c/Program Files/Microsoft Visual Studio 9.0/VC/BIN/cl link: /cygdrive/c/Program Files/Microsoft Visual Studio 9.0/VC/BIN/link nmake: /cygdrive/c/Program Files/Microsoft Visual Studio 9.0/VC/BIN/nmake bash: /usr/bin/bash bison: /usr/bin/bison flex: /usr/bin/flex env: /usr/bin/env grep: /usr/bin/grep /usr/bin/find: /usr/bin/find perl: /usr/bin/perl C:\Python26\python.exe: /cygdrive/c/Python26/python.exe sed: /usr/bin/sed unzip: /usr/bin/unzip wget: /usr/bin/wget During compiling, some problem met. Anyone can help to resolve this problem. Thanks. Generating Code... Compiling... packet-h460.c packet-h501.c packet-inap.c packet-ldap.c packet-logotypecertextn.c packet-mms.c packet-mpeg-audio.c packet-mpeg-pes.c packet-mpeg-pes-template.c(300) : error C2220: warning treated as error - no 'ob ject' file generated packet-mpeg-pes-template.c(300) : warning C4819: The file contains a character t hat cannot be represented in the current code page (936). Save the file in Unico de format to prevent data loss packet-nbap.c packet-ns_cert_exts.c packet-ocsp.c packet-p7.c packet-pcap.c packet-pkcs12.c packet-pkcs1.c packet-pkinit.c packet-pkix1explicit.c packet-pkix1implicit.c packet-pkixproxy.c packet-pkixqualified.c Generating Code... Compiling... packet-pkixtsp.c packet-pres.c packet-q932.c packet-q932-ros.c packet-qsig.c packet-ranap.c packet-rnsap.c packet-ros.c packet-rrlp.c packet-rtse.c packet-s1ap.c packet-s4406.c packet-sabp.c packet-smrse.c packet-snmp.c packet-spnego.c packet-t125.c packet-tcap.c packet-ulp.c packet-wlancertextn.c Generating Code... Compiling... packet-x2ap.c packet-x224.c packet-x411.c packet-x420.c packet-x509af.c packet-x509ce.c packet-x509if.c packet-x509sat.c packet-dcerpc-nt.c Generating Code... NMAKE : fatal error U1077: 'C:\Program Files\Microsoft Visual Studio 9.0\VC\BIN \cl.EXE' : return code '0x2' Stop. NMAKE : fatal error U1077: 'C:\Program Files\Microsoft Visual Studio 9.0\VC\BIN \nmake.exe' : return code '0x2' Stop. NMAKE : fatal error U1077: 'C:\Program Files\Microsoft Visual Studio 9.0\VC\BIN \nmake.exe' : return code '0x2' Stop. Best Regards Patrick ___ 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
Re: [Wireshark-dev] Compilation errors while building the Wireshark sources
Hi Abhik, What does distclean does? I want to know will my changes remain when i do distclean? And also how do i compile a single file instead of building the whole project? Thanks in advance Rohan On Thu, Apr 30, 2009 at 4:28 AM, Abhik Sarkar sarkar.ab...@gmail.comwrote: Did you try nmake -f makefile.nmake distclean nmake -f makefile.nmake all This has often worked for me in similar situations. On Thu, Apr 30, 2009 at 3:08 PM, Anonymous Anonymous a.master.blas...@gmail.com wrote: No luck so far. I've re-downloaded the sources using TortoiseSVN and compilation again fails in the exact same place. Any suggestions? On Wed, Apr 29, 2009 at 9:14 AM, Jaap Keuter jaap.keu...@xs4all.nlwrote: Hi, Well, he's building the 1.1.4 development version, so 2008 should be fine. It seems that you've a botched tarball or working copy, since little has changed in this area for a long time. Try downloading a new tarball or revert changes in the working copy and start from the current head of development. Thanx, Jaap Rohan Solanki wrote: hi, I think you should try building wireshark with visual studio 2005. Also Make appropriate changes in the config.nmake file. I also had problems with visual studio 2008. I have successfully build and running wireshark 1.0.5 with visual studio 2005. Rohan. On Tue, Apr 28, 2009 at 7:19 PM, Anonymous Anonymous a.master.blas...@gmail.com mailto:a.master.blas...@gmail.com wrote: Hi everyone, I'm new to the Wireshark development process and I'm having some building issues I hope you will be able to solve. Ok, so here it comes. I've followed the developers manual step-by-step and everything worked out fine until I had to issue the command name Makefile.namke all. For some unknown reason this command seems to fail over and over again. The relevant output lines I managed to extract from the console are as follows: /*dissectors.lib(packet-ncp-sss.obj) : error LNK2001: unresolved external symbol _ ett_nds libwireshark.dll : fatal error LNK1120: 1 unresolved externals NMAKE : fatal error U1077: 'C:\Program Files\Microsoft Visual Studio 9.0\VC\BIN \link.EXE' : return code '0x460' Stop. NMAKE : fatal error U1077: 'C:\Program Files\Microsoft Visual Studio 9.0\VC\BIN \nmake.exe' : return code '0x2' Stop. */The same output also appears when I'm trying to build the .sln file provided is the sources using VC++ 2008 Express Edition. Can someone point out what the problem is? Thanks in advance. Any help will be deeply appreciated. My building environment specs: OS - Microsoft Windows XP SP3 IDE - Microsoft Visual C++ 2008 Express Edition SVN - TortoiseSVN Wireshark version - 1.1.4.0 (version info was taken from the config.nmake file) ___ 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 ___ 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
Re: [Wireshark-dev] Compilation errors while building the Wireshark sources
Hi Rohan, The distclean target cleans up any files made for a distribution... this removes any generated stuff and keeps the sources untouched. You can't compile a single file if you are changing the in-built dissectors because all of the functionality is part of one big shared library and that library needs to be relinked. I would like to point out however that the build system compiles only changed sources (and a few other files) and only re-links them... so, I normally find that if I change only a particular dissector the re-build takes a only about a minute, but after a distclean it takes a good 5-10 minutes (on my system). Regards, Abhik. On Thu, Apr 30, 2009 at 3:32 PM, Rohan Solanki solanki.ro...@gmail.comwrote: Hi Abhik, What does distclean does? I want to know will my changes remain when i do distclean? And also how do i compile a single file instead of building the whole project? Thanks in advance Rohan On Thu, Apr 30, 2009 at 4:28 AM, Abhik Sarkar sarkar.ab...@gmail.comwrote: Did you try nmake -f makefile.nmake distclean nmake -f makefile.nmake all This has often worked for me in similar situations. On Thu, Apr 30, 2009 at 3:08 PM, Anonymous Anonymous a.master.blas...@gmail.com wrote: No luck so far. I've re-downloaded the sources using TortoiseSVN and compilation again fails in the exact same place. Any suggestions? On Wed, Apr 29, 2009 at 9:14 AM, Jaap Keuter jaap.keu...@xs4all.nlwrote: Hi, Well, he's building the 1.1.4 development version, so 2008 should be fine. It seems that you've a botched tarball or working copy, since little has changed in this area for a long time. Try downloading a new tarball or revert changes in the working copy and start from the current head of development. Thanx, Jaap Rohan Solanki wrote: hi, I think you should try building wireshark with visual studio 2005. Also Make appropriate changes in the config.nmake file. I also had problems with visual studio 2008. I have successfully build and running wireshark 1.0.5 with visual studio 2005. Rohan. On Tue, Apr 28, 2009 at 7:19 PM, Anonymous Anonymous a.master.blas...@gmail.com mailto:a.master.blas...@gmail.com wrote: Hi everyone, I'm new to the Wireshark development process and I'm having some building issues I hope you will be able to solve. Ok, so here it comes. I've followed the developers manual step-by-step and everything worked out fine until I had to issue the command name Makefile.namke all. For some unknown reason this command seems to fail over and over again. The relevant output lines I managed to extract from the console are as follows: /*dissectors.lib(packet-ncp-sss.obj) : error LNK2001: unresolved external symbol _ ett_nds libwireshark.dll : fatal error LNK1120: 1 unresolved externals NMAKE : fatal error U1077: 'C:\Program Files\Microsoft Visual Studio 9.0\VC\BIN \link.EXE' : return code '0x460' Stop. NMAKE : fatal error U1077: 'C:\Program Files\Microsoft Visual Studio 9.0\VC\BIN \nmake.exe' : return code '0x2' Stop. */The same output also appears when I'm trying to build the .sln file provided is the sources using VC++ 2008 Express Edition. Can someone point out what the problem is? Thanks in advance. Any help will be deeply appreciated. My building environment specs: OS - Microsoft Windows XP SP3 IDE - Microsoft Visual C++ 2008 Express Edition SVN - TortoiseSVN Wireshark version - 1.1.4.0 (version info was taken from the config.nmake file) ___ 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 ___ 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:
Re: [Wireshark-dev] packet-mpeg-pes.c. compiling fail on win32
Hi, If no one beats me to it I'll check this in tonight. /Anders -Original Message- From: Jaap Keuter [mailto:jaap.keu...@xs4all.nl] Sent: den 30 april 2009 09:41 To: Developer support list for Wireshark; Anders Broman Subject: Re: [Wireshark-dev] packet-mpeg-pes.c. compiling fail on win32 Hi, This is due to a bug in the sourcecode of the MPEG-PES dissector. It originates in r26328, which added a bugfix to the generated code with the use of 'illegal' characters in the comment block. Currently the bugfix is dropped since it was never added to the ASN.1 dissector template, hence has been lost with the new generation of this code. Anders, could you: 1. Make the appropriate changes to the dissectors ASN1 template. 2. Remove the illegal quote characters from the comment block. 3. Add the changes to template and generated code to the 1.0.8 roadmap. Patrick, you can fix this by removing the illegal characters from start of line 853 and end of line 855 in packet-mpeg-pes.c. Thanx, Jaap Yan, Patrick (NSN - CN/Beijing) wrote: Hi all, OS is windows XP, wireshark source code is last version of wireshark-1.0.7. Checking for required applications: cl: /cygdrive/c/Program Files/Microsoft Visual Studio 9.0/VC/BIN/cl link: /cygdrive/c/Program Files/Microsoft Visual Studio 9.0/VC/BIN/link nmake: /cygdrive/c/Program Files/Microsoft Visual Studio 9.0/VC/BIN/nmake bash: /usr/bin/bash bison: /usr/bin/bison flex: /usr/bin/flex env: /usr/bin/env grep: /usr/bin/grep /usr/bin/find: /usr/bin/find perl: /usr/bin/perl C:\Python26\python.exe: /cygdrive/c/Python26/python.exe sed: /usr/bin/sed unzip: /usr/bin/unzip wget: /usr/bin/wget During compiling, some problem met. Anyone can help to resolve this problem. Thanks. Generating Code... Compiling... packet-h460.c packet-h501.c packet-inap.c packet-ldap.c packet-logotypecertextn.c packet-mms.c packet-mpeg-audio.c packet-mpeg-pes.c packet-mpeg-pes-template.c(300) : error C2220: warning treated as error - no 'ob ject' file generated packet-mpeg-pes-template.c(300) : warning C4819: The file contains a character t hat cannot be represented in the current code page (936). Save the file in Unico de format to prevent data loss packet-nbap.c packet-ns_cert_exts.c packet-ocsp.c packet-p7.c packet-pcap.c packet-pkcs12.c packet-pkcs1.c packet-pkinit.c packet-pkix1explicit.c packet-pkix1implicit.c packet-pkixproxy.c packet-pkixqualified.c Generating Code... Compiling... packet-pkixtsp.c packet-pres.c packet-q932.c packet-q932-ros.c packet-qsig.c packet-ranap.c packet-rnsap.c packet-ros.c packet-rrlp.c packet-rtse.c packet-s1ap.c packet-s4406.c packet-sabp.c packet-smrse.c packet-snmp.c packet-spnego.c packet-t125.c packet-tcap.c packet-ulp.c packet-wlancertextn.c Generating Code... Compiling... packet-x2ap.c packet-x224.c packet-x411.c packet-x420.c packet-x509af.c packet-x509ce.c packet-x509if.c packet-x509sat.c packet-dcerpc-nt.c Generating Code... NMAKE : fatal error U1077: 'C:\Program Files\Microsoft Visual Studio 9.0\VC\BIN \cl.EXE' : return code '0x2' Stop. NMAKE : fatal error U1077: 'C:\Program Files\Microsoft Visual Studio 9.0\VC\BIN \nmake.exe' : return code '0x2' Stop. NMAKE : fatal error U1077: 'C:\Program Files\Microsoft Visual Studio 9.0\VC\BIN \nmake.exe' : return code '0x2' Stop. Best Regards Patrick packet-mpeg-pes-template.c.diff Description: packet-mpeg-pes-template.c.diff ___ 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
Re: [Wireshark-dev] Compilation errors while building the Wireshark sources
Ok .. got it!!! Thanks Abhik for the reply... On Thu, Apr 30, 2009 at 5:59 AM, Abhik Sarkar sarkar.ab...@gmail.comwrote: Hi Rohan, The distclean target cleans up any files made for a distribution... this removes any generated stuff and keeps the sources untouched. You can't compile a single file if you are changing the in-built dissectors because all of the functionality is part of one big shared library and that library needs to be relinked. I would like to point out however that the build system compiles only changed sources (and a few other files) and only re-links them... so, I normally find that if I change only a particular dissector the re-build takes a only about a minute, but after a distclean it takes a good 5-10 minutes (on my system). Regards, Abhik. On Thu, Apr 30, 2009 at 3:32 PM, Rohan Solanki solanki.ro...@gmail.comwrote: Hi Abhik, What does distclean does? I want to know will my changes remain when i do distclean? And also how do i compile a single file instead of building the whole project? Thanks in advance Rohan On Thu, Apr 30, 2009 at 4:28 AM, Abhik Sarkar sarkar.ab...@gmail.comwrote: Did you try nmake -f makefile.nmake distclean nmake -f makefile.nmake all This has often worked for me in similar situations. On Thu, Apr 30, 2009 at 3:08 PM, Anonymous Anonymous a.master.blas...@gmail.com wrote: No luck so far. I've re-downloaded the sources using TortoiseSVN and compilation again fails in the exact same place. Any suggestions? On Wed, Apr 29, 2009 at 9:14 AM, Jaap Keuter jaap.keu...@xs4all.nlwrote: Hi, Well, he's building the 1.1.4 development version, so 2008 should be fine. It seems that you've a botched tarball or working copy, since little has changed in this area for a long time. Try downloading a new tarball or revert changes in the working copy and start from the current head of development. Thanx, Jaap Rohan Solanki wrote: hi, I think you should try building wireshark with visual studio 2005. Also Make appropriate changes in the config.nmake file. I also had problems with visual studio 2008. I have successfully build and running wireshark 1.0.5 with visual studio 2005. Rohan. On Tue, Apr 28, 2009 at 7:19 PM, Anonymous Anonymous a.master.blas...@gmail.com mailto:a.master.blas...@gmail.com wrote: Hi everyone, I'm new to the Wireshark development process and I'm having some building issues I hope you will be able to solve. Ok, so here it comes. I've followed the developers manual step-by-step and everything worked out fine until I had to issue the command name Makefile.namke all. For some unknown reason this command seems to fail over and over again. The relevant output lines I managed to extract from the console are as follows: /*dissectors.lib(packet-ncp-sss.obj) : error LNK2001: unresolved external symbol _ ett_nds libwireshark.dll : fatal error LNK1120: 1 unresolved externals NMAKE : fatal error U1077: 'C:\Program Files\Microsoft Visual Studio 9.0\VC\BIN \link.EXE' : return code '0x460' Stop. NMAKE : fatal error U1077: 'C:\Program Files\Microsoft Visual Studio 9.0\VC\BIN \nmake.exe' : return code '0x2' Stop. */The same output also appears when I'm trying to build the .sln file provided is the sources using VC++ 2008 Express Edition. Can someone point out what the problem is? Thanks in advance. Any help will be deeply appreciated. My building environment specs: OS - Microsoft Windows XP SP3 IDE - Microsoft Visual C++ 2008 Express Edition SVN - TortoiseSVN Wireshark version - 1.1.4.0 (version info was taken from the config.nmake file) ___ 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 ___ 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
[Wireshark-dev] make error
Hi, I wanted to capture the wireless traffic in the XO.I used tcpdump and I follow this link http://wiki.laptop.org/go/Wireless . Then, to interpret mesh traffic correctly, I installed wireshark-0.99.5 with this patch: http://dev.laptop.org/~javier/patches/wireshark-0.99.5-fw-5.220.11-support.patch. But when I run make, I got these errors: epan/.libs/libwireshark.so: undefined reference to `proto_register_mesh' epan/.libs/libwireshark.so: undefined reference to `proto_reg_handoff_mesh' collect2: ld returned 1 exit status make[2]: *** [wireshark] Error 1 make[2]: Leaving directory `/home/pfe/wireshark-0.99.5' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/pfe/wireshark-0.99.5' make: *** [all] Error 2 Any ideas why there are those undefined references to proto_register_mesh and proto_reg_handoff_mesh ? thanks ___ 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
Re: [Wireshark-dev] Compilation errors while building the Wireshark sources
Didn't work out for me. I got the same error again. On Thu, Apr 30, 2009 at 2:28 PM, Abhik Sarkar sarkar.ab...@gmail.comwrote: Did you try nmake -f makefile.nmake distclean nmake -f makefile.nmake all This has often worked for me in similar situations. On Thu, Apr 30, 2009 at 3:08 PM, Anonymous Anonymous a.master.blas...@gmail.com wrote: No luck so far. I've re-downloaded the sources using TortoiseSVN and compilation again fails in the exact same place. Any suggestions? On Wed, Apr 29, 2009 at 9:14 AM, Jaap Keuter jaap.keu...@xs4all.nlwrote: Hi, Well, he's building the 1.1.4 development version, so 2008 should be fine. It seems that you've a botched tarball or working copy, since little has changed in this area for a long time. Try downloading a new tarball or revert changes in the working copy and start from the current head of development. Thanx, Jaap Rohan Solanki wrote: hi, I think you should try building wireshark with visual studio 2005. Also Make appropriate changes in the config.nmake file. I also had problems with visual studio 2008. I have successfully build and running wireshark 1.0.5 with visual studio 2005. Rohan. On Tue, Apr 28, 2009 at 7:19 PM, Anonymous Anonymous a.master.blas...@gmail.com mailto:a.master.blas...@gmail.com wrote: Hi everyone, I'm new to the Wireshark development process and I'm having some building issues I hope you will be able to solve. Ok, so here it comes. I've followed the developers manual step-by-step and everything worked out fine until I had to issue the command name Makefile.namke all. For some unknown reason this command seems to fail over and over again. The relevant output lines I managed to extract from the console are as follows: /*dissectors.lib(packet-ncp-sss.obj) : error LNK2001: unresolved external symbol _ ett_nds libwireshark.dll : fatal error LNK1120: 1 unresolved externals NMAKE : fatal error U1077: 'C:\Program Files\Microsoft Visual Studio 9.0\VC\BIN \link.EXE' : return code '0x460' Stop. NMAKE : fatal error U1077: 'C:\Program Files\Microsoft Visual Studio 9.0\VC\BIN \nmake.exe' : return code '0x2' Stop. */The same output also appears when I'm trying to build the .sln file provided is the sources using VC++ 2008 Express Edition. Can someone point out what the problem is? Thanks in advance. Any help will be deeply appreciated. My building environment specs: OS - Microsoft Windows XP SP3 IDE - Microsoft Visual C++ 2008 Express Edition SVN - TortoiseSVN Wireshark version - 1.1.4.0 (version info was taken from the config.nmake file) ___ 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 ___ 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
Re: [Wireshark-dev] Compilation errors while building the Wireshark sources
On Thu, Apr 30, 2009 at 5:59 AM, Abhik Sarkar sarkar.ab...@gmail.comwrote: Hi Rohan, The distclean target cleans up any files made for a distribution... this removes any generated stuff and keeps the sources untouched. You can't compile a single file if you are changing the in-built dissectors because all of the functionality is part of one big shared library and that library needs to be relinked. I would like to point out however that the build system compiles only changed sources (and a few other files) and only re-links them... so, I normally find that if I change only a particular dissector the re-build takes a only about a minute, but after a distclean it takes a good 5-10 minutes (on my system). Regards, Abhik. Just for the record: The Windows build does *not* handle changed .h files and .h fie dependencies when deciding what needs to be recompiled. So: if a .h file is changed, then either a complete rebuild is needed or you must manually force a recompile for any .c files using the .h file (E.G.: by deleting the .obj files corresponding to the .c files). Doing this manually can easily miss something so use the manual procedure only if you are exactly sure what needs to be recompiled when a .h file changes. ___ 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
Re: [Wireshark-dev] make error
Hi, You forgot to configure first. Thanx, Jaap Rekik Hanen wrote: Hi, I wanted to capture the wireless traffic in the XO.I used tcpdump and I follow this link http://wiki.laptop.org/go/Wireless . Then, to interpret mesh traffic correctly, I installed wireshark-0.99.5 with this patch: http://dev.laptop.org/~javier/patches/wireshark-0.99.5-fw-5.220.11-support.patch http://dev.laptop.org/%7Ejavier/patches/wireshark-0.99.5-fw-5.220.11-support.patch. But when I run make, I got these errors: epan/.libs/libwireshark.so: undefined reference to `proto_register_mesh' epan/.libs/libwireshark.so: undefined reference to `proto_reg_handoff_mesh' collect2: ld returned 1 exit status make[2]: *** [wireshark] Error 1 make[2]: Leaving directory `/home/pfe/wireshark-0.99.5' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/pfe/wireshark-0.99.5' make: *** [all] Error 2 Any ideas why there are those undefined references to proto_register_mesh and proto_reg_handoff_mesh ? thanks ___ 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
Re: [Wireshark-dev] make error
Hi, But you can't have 'Makefile' without running configure.. try: $make distclean $./autogen.sh $/.configure with appropriate options Thanks, Bhargava On Thu, Apr 30, 2009 at 9:04 PM, Jaap Keuter jaap.keu...@xs4all.nl wrote: Hi, You forgot to configure first. Thanx, Jaap Rekik Hanen wrote: Hi, I wanted to capture the wireless traffic in the XO.I used tcpdump and I follow this link http://wiki.laptop.org/go/Wireless . Then, to interpret mesh traffic correctly, I installed wireshark-0.99.5 with this patch: http://dev.laptop.org/~javier/patches/wireshark-0.99.5-fw-5.220.11-support.patch http://dev.laptop.org/%7Ejavier/patches/wireshark-0.99.5-fw-5.220.11-support.patch . But when I run make, I got these errors: epan/.libs/libwireshark.so: undefined reference to `proto_register_mesh' epan/.libs/libwireshark.so: undefined reference to `proto_reg_handoff_mesh' collect2: ld returned 1 exit status make[2]: *** [wireshark] Error 1 make[2]: Leaving directory `/home/pfe/wireshark-0.99.5' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/pfe/wireshark-0.99.5' make: *** [all] Error 2 Any ideas why there are those undefined references to proto_register_mesh and proto_reg_handoff_mesh ? thanks ___ 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
Re: [Wireshark-dev] [Wireshark-commits] rev 28200:/trunk/epan/dissectors/ /trunk/epan/dissectors/: Makefile.common
Ooops 2) Was intended... /Anders -Ursprungligt meddelande- Från: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] För Guy Harris Skickat: den 30 april 2009 19:30 Till: wireshark-dev@wireshark.org Ämne: Re: [Wireshark-dev] [Wireshark-commits] rev 28200:/trunk/epan/dissectors/ /trunk/epan/dissectors/: Makefile.common On Apr 30, 2009, at 8:55 AM, etx...@wireshark.org wrote: http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=revrevision=28200 User: etxrab Date: 2009/04/30 08:55 AM Log: Resort the list a bit. Directory: /trunk/epan/dissectors/ ChangesPath Action +3 -3 Makefile.commonModified This moved some dissectors generated from ASN.1 specifications from ASN1_DISSECTOR_SRC to DISSECTOR_SRC; that doesn't affect whether they're built with -Werror (or, at least, it *shouldn't* - if it does, that's a bug). Currently, we don't treat dissectors in ASN1_DISSECTOR_SRC and DISSECTOR_SRC differently, but, given that, presumably either 1) we should get rid of ASN1_DISSECTOR_SRC and DIRTY_ASN1_DISSECTOR_SRC and just merge them into DISSECTOR_SRC and DIRTY_DISSECTOR_SRC, respectively or 2) we should keep all dissectors generated with asn2wrs in ASN1_DISSECTOR_SRC and DIRTY_ASN1_DISSECTOR_SRC. ___ 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
Re: [Wireshark-dev] Wireshark Custom Dissector Problems. Windows and Linux
I am running into this same build error now. I am building on Windows Vista using an SVN checkout of the source and Visual Studio 2005. Was a solution discovered? Thank you, ___ 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
