Re: [Wireshark-dev] Compilation errors

2011-04-22 Thread Jakub Zawadzki
On Thu, Apr 21, 2011 at 02:02:00PM +0200, Anders Broman wrote: Ok, unfortunately I can't try myself as I'm trying to assist a co-worker at a remote location. He is using gcc version 3.4.3 20041212 (Red Hat 3.4.3-9.EL4) which is quite old. Commited fix in r36797

[Wireshark-dev] Compilation errors

2011-04-21 Thread Anders Broman
Hi, I'm not sure what the right fix for this one is hostlist_table.c: In function `hostlist_sort_column': hostlist_table.c:341: warning: control reaches end of non-void function make: *** [libui_a-hostlist_table.o] Error 1 Should case 1: return CMP.. ? In the default branch there should also be

Re: [Wireshark-dev] Compilation errors

2011-04-21 Thread Stig Bjørlykke
On Thu, Apr 21, 2011 at 1:03 PM, Anders Broman anders.bro...@ericsson.com wrote: Should case 1: return CMP.. ? In the default branch there should also be a return, right? Do you get this without GEOIP? We should always have a default in a switch, so I guess we should have a return 0 in the

Re: [Wireshark-dev] Compilation errors

2011-04-21 Thread Anders Broman
-Original Message- From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Stig Bjørlykke Sent: den 21 april 2011 13:19 To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] Compilation errors On Thu, Apr 21, 2011 at 1:03 PM

Re: [Wireshark-dev] Compilation errors

2011-04-21 Thread Stig Bjørlykke
On Thu, Apr 21, 2011 at 1:30 PM, Anders Broman anders.bro...@ericsson.com wrote: Ok, but both case 1 and the default branch (with GEOIP) ends in g_assert unless I'm misstaken and that's hardly the intention is it? case 1 has a CMP_INT which does return. The default branch is only used for

Re: [Wireshark-dev] Compilation errors

2011-04-21 Thread Anders Broman
-Original Message- From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Stig Bjørlykke Sent: den 21 april 2011 13:52 To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] Compilation errors On Thu, Apr 21, 2011 at 1:30 PM

Re: [Wireshark-dev] Compilation errors in wiretap/ (without zlib)

2010-04-17 Thread Stig Bjørlykke
2010/4/12 Jakub Zawadzki darkja...@darkjames.ath.cx: Attaching patch for vms and packetlogger. Committed revision 32501. -- Stig Bjørlykke ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:

[Wireshark-dev] Compilation errors in wiretap/ (without zlib)

2010-04-12 Thread Jakub Zawadzki
Hi, cause of bug 4606 (zlib-1.2.4 bug) I tried to compile wireshark without zlib: #v+ netscaler.c: In function 'nstrace_open': netscaler.c:496: error: comparison between signed and unsigned integer expressions netscaler.c:532: error: comparison between signed and unsigned integer expressions

Re: [Wireshark-dev] Compilation errors while building the Wireshark sources

2009-05-12 Thread Alfred Alinazar
I have the same problem. I have tried to do distclean and compile again several times, but no luck. Anyone has luck in solving this problem? regards, -Alfred- On Fri, May 1, 2009 at 8:28 PM, Anonymous Anonymous a.master.blas...@gmail.com wrote: I'm still stuck at this. Here is the complete

Re: [Wireshark-dev] Compilation errors while building the Wireshark sources

2009-05-01 Thread Anonymous Anonymous
I'm still stuck at this. Here is the complete build log I've managed to extract using the command: nmake -f Makefile.nmake all build-log.txt 21 * Microsoft (R) Program Maintenance Utility Version 9.00.30729.01 Copyright (C) Microsoft Corporation. All rights reserved. cd tools

Re: [Wireshark-dev] Compilation errors while building the Wireshark sources

2009-04-30 Thread Anonymous Anonymous
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

Re: [Wireshark-dev] Compilation errors while building the Wireshark sources

2009-04-30 Thread Abhik Sarkar
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

Re: [Wireshark-dev] Compilation errors while building the Wireshark sources

2009-04-30 Thread Rohan Solanki
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

Re: [Wireshark-dev] Compilation errors while building the Wireshark sources

2009-04-30 Thread Abhik Sarkar
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

Re: [Wireshark-dev] Compilation errors while building the Wireshark sources

2009-04-30 Thread Rohan Solanki
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

Re: [Wireshark-dev] Compilation errors while building the Wireshark sources

2009-04-30 Thread Anonymous Anonymous
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,

Re: [Wireshark-dev] Compilation errors while building the Wireshark sources

2009-04-30 Thread Bill Meier
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

Re: [Wireshark-dev] Compilation errors while building the Wireshark sources

2009-04-29 Thread Rohan Solanki
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,

Re: [Wireshark-dev] Compilation errors while building the Wireshark sources

2009-04-29 Thread Jaap Keuter
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

[Wireshark-dev] Compilation errors while building the Wireshark sources

2009-04-28 Thread Anonymous Anonymous
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

Re: [Wireshark-dev] compilation errors in packet-spnego-template.c

2007-05-25 Thread Brian Vandenberg
Some code was changed for asn1\spnego\packet-spnego-template.c on line 472 that's causing the following warning/compilation error: Microsoft (R) Program Maintenance Utility Version 8.00.50727.42 Copyright (C) Microsoft Corporation. All rights reserved. cl -DWIN32 -DNULL=0 -D_MT

[Wireshark-dev] Compilation errors

2007-03-20 Thread taraniteja.vishwanatha
Hi , I have written a dissector, compiled and tested it( no problems). But the same dissector when used by somebody else at a different location is giving compilation problems. They are using the same OS (RHEL 4) and the same compiler version as ours. It is giving the following error: