[Wireshark-dev] Ubuntu Cmake Build Failing

2014-02-11 Thread Evan Huus
So I finally got the licensecheck passing (woohoo!) and noticed while I was doing it that the cmake build has been failing for a while: Traceback (most recent call last): File "/home/wireshark/builders/trunk/ubuntu1204x64/build/tools/make-tap-reg.py", line 181, in os.rename(tmp_filename, f

Re: [Wireshark-dev] Removal of reedsolomon code

2014-02-11 Thread Evan Huus
Ah, the email in the source file was dead so I gave up, but that looks like the same person, I will try contacting him. Thanks, Evan On Tue, Feb 11, 2014 at 3:53 PM, Didier wrote: > Hi, > > On Tue, 11 Feb 2014 13:07:15 -0500, Evan Huus wrote >> As per my previous emails, the only questionably-li

Re: [Wireshark-dev] Removal of reedsolomon code

2014-02-11 Thread Didier
Hi, On Tue, 11 Feb 2014 13:07:15 -0500, Evan Huus wrote > As per my previous emails, the only questionably-licensed code we > have left is the reed-solomon implementation. It is used only in > packet-dcp-etsi.c. > > I have failed to find any other suitably-licensed reed-solomon > implementation

[Wireshark-dev] Removal of reedsolomon code

2014-02-11 Thread Evan Huus
As per my previous emails, the only questionably-licensed code we have left is the reed-solomon implementation. It is used only in packet-dcp-etsi.c. I have failed to find any other suitably-licensed reed-solomon implementations, and don't have time to write one myself. As such I think our best co

Re: [Wireshark-dev] error encountered during compilation on windows

2014-02-11 Thread Anders Broman
Hi, Have you set your MSVC_VERSION and downloaded vcredist and put it in its correct place? Regards Anders From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Pascal Quantin Sent: den 11 februari 2014 14:50 To: Developer support list for Wireshark

Re: [Wireshark-dev] error encountered during compilation on windows

2014-02-11 Thread Pascal Quantin
2014-02-11 14:38 GMT+01:00 Rahul Rohit : > < epan/except.c, epan/proto.h > > Do you have to comment it also, or only its call in epan/except.h file?>> > > > > > > No we comment 'WS_MSVC_NORETURN ' only inside epan/except.h > > Then there is definitely something weird / wrong on your side and it w

Re: [Wireshark-dev] error encountered during compilation on windows

2014-02-11 Thread Rahul Rohit
<> No we comment 'WS_MSVC_NORETURN ' only inside epan/except.h Regards Rahul Rohit From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Pascal Quantin Sent: Tuesday, February 11, 2014 6:48 PM To: Developer support list for Wireshark Subject: Re

Re: [Wireshark-dev] error encountered during compilation on windows

2014-02-11 Thread Pascal Quantin
2014-02-11 13:50 GMT+01:00 Rahul Rohit : > > Hi, > > > > < #define WS_MSVC_NORETURN__declspec(noreturn) > > in the auto generated config.h file found at the root of your working copy. > > Do you confirm you have it defined in your local copy? > > Does it happen when you compile a specific fil

Re: [Wireshark-dev] error encountered during compilation on windows

2014-02-11 Thread Rahul Rohit
Hi, <> The definition ' WS_MSVC_NORETURN __declspec(noreturn)' is present in our config.h file. No, the problem is general and not related to any particular file Regards Rahul Rohit From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Pascal Q

Re: [Wireshark-dev] error encountered during compilation on windows

2014-02-11 Thread Pascal Quantin
Hi, 2014-02-11 8:41 GMT+01:00 Rahul Rohit : > Hi, > > During the build of wireshark exe in windows machice(32 bit) we get the > following errors. > > > > epan\except.h(97) : error C2054: expected '(' to follow 'WS_MSVC_NORETURN' > > epan\except.h(97) : error C2085: 'except_rethrow' : not in for

Re: [Wireshark-dev] error encountered during compilation on windows

2014-02-11 Thread Graham Bloice
nmake (like all other make systems ??) uses relative times to determine if a rebuild is required, e.g. if the .c is newer than the .obj then compile the .c. The absolute time doesn't make any difference. On 11 February 2014 12:15, Rahul Rohit wrote: > Hi, > > > > < modifications?>> > > Yes. I

Re: [Wireshark-dev] error encountered during compilation on windows

2014-02-11 Thread Rahul Rohit
Hi, <> Yes. I am using Wireshark baseline code but I am unable to make the build . I am getting the errors that I mentioned in my last mail What I observed during the compilation is that at each compilation command(nmake -f Makefile.nmake all) all the files are getting compiled over and over

Re: [Wireshark-dev] error encountered during compilation on windows

2014-02-11 Thread Anders Broman
From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Rahul Rohit Sent: den 11 februari 2014 11:26 To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] error encountered during compilation on windows Hello, <<< If this is the first

Re: [Wireshark-dev] error encountered during compilation on windows

2014-02-11 Thread Rahul Rohit
Hello, << If this is the first time you have tried to build Wireshark, then the usual advice is to go back and read the Developers Guide again and make sure you are following the prescribed method exactly as written because it does work for many people.>> No, this is not the first time, I ofte

Re: [Wireshark-dev] error encountered during compilation on windows

2014-02-11 Thread Graham Bloice
On 11 February 2014 07:41, Rahul Rohit wrote: > Hi, > > During the build of wireshark exe in windows machice(32 bit) we get the > following errors. > > > > epan\except.h(97) : error C2054: expected '(' to follow 'WS_MSVC_NORETURN' > > epan\except.h(97) : error C2085: 'except_rethrow' : not in f

Re: [Wireshark-dev] TCP Reassembly in wireshark

2014-02-11 Thread Guy Harris
On Feb 10, 2014, at 10:19 PM, Vishnu Bhatt wrote: > << get_sabp_pdu_len(), that looks at the first few bytes of the message > (using a routine to do so for ASN.1 PER)>> > > Actually I was asking for some help in this regard only. How does it look at > the first few bytes of the message? I as