[Wireshark-dev] Error while installing wireshark 1.10.3

2013-12-05 Thread Vishnu Bhatt
Hello, I have compiled the source code of Wireshark version 1.10.3. Everything worked fine. But after the rpm was created, I tried to install it and got the following error. error: unpacking of archive failed on file /install/bin/dumpcap: cpio: cap_set_file failed - Operation not supported I

Re: [Wireshark-dev] Windows build setup - Concept required

2013-12-05 Thread Gerald Combs
On 12/4/13 12:27 PM, Joerg Mayer wrote: > Hello, > > as Graham and I are working on getting the Windows build process to > a) work at all and b) be on par with the current nmake build process > we currently rely on the setup infrastructure of the nmake build. I > really don't like porting the "nma

Re: [Wireshark-dev] Windows build setup - Concept required

2013-12-05 Thread Bill Meier
Re: creating/using a standard package directory structure on Windows It sounds like you're suggesting that we take the packages as distribited and move things around to a standard structure. This sounds to me like the effort to do this it might be crazy-making ... Also: A fe

Re: [Wireshark-dev] Windows build setup - Concept required

2013-12-05 Thread Bill Meier
On 12/5/2013 3:02 PM, Bill Meier wrote: I like Gerald's answers much better than mine :) ___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://w

Re: [Wireshark-dev] Windows build setup - Concept required

2013-12-05 Thread Pascal Quantin
2013/12/5 Gerald Combs > > 10) The setup process does not allow for the simultanous installation > >of gtk2 and gtk3 > > Does GTK3 work well enough on Windows to drop GTK2? This would simplify > things quite a bit. > Personally I find the GTK2 GUI much more polished than GTK3 on Windows (may

Re: [Wireshark-dev] [Wireshark-commits] rev 53683: /trunk/tools/ /trunk/tools/: make-dissector-reg.py

2013-12-05 Thread Gerald Combs
On 12/1/13 9:21 AM, Graham Bloice wrote: > > BTW, why is OSX using such an ancient version of Python. I believe only > 2.7 and 3.3 are supported by the Python folks. As I recall, Buildbot on each of the OS X builders was installed using the version of Python that shipped with each system. Both t

Re: [Wireshark-dev] Windows build setup - Concept required

2013-12-05 Thread mmann78
+1 -Original Message- From: Pascal Quantin To: Developer support list for Wireshark Sent: Thu, Dec 5, 2013 3:33 pm Subject: Re: [Wireshark-dev] Windows build setup - Concept required Personally I find the GTK2 GUI much more polished than GTK3 on Windows (maybe just a matter of ta

Re: [Wireshark-dev] [Wireshark-commits] rev 53683: /trunk/tools/ /trunk/tools/: make-dissector-reg.py

2013-12-05 Thread Guy Harris
On Dec 5, 2013, at 12:27 PM, Gerald Combs wrote: > On 12/1/13 9:21 AM, Graham Bloice wrote: >> >> BTW, why is OSX using such an ancient version of Python. I believe only >> 2.7 and 3.3 are supported by the Python folks. > > As I recall, Buildbot on each of the OS X builders was installed usin

Re: [Wireshark-dev] Windows build setup - Concept required

2013-12-05 Thread Christopher Maynard
writes: > +1 > > -Original Message- > From: Pascal Quantin > To: Developer support list for Wireshark > Sent: Thu, Dec 5, 2013 3:33 pm > Subject: Re: [Wireshark-dev] Windows build setup - Concept required > > Personally I find the GTK2 GUI much more polished than GTK3 on Windows (may

Re: [Wireshark-dev] Windows build setup - Concept required

2013-12-05 Thread Pascal Quantin
2013/12/5 Christopher Maynard > writes: > > > +1 > > > > -Original Message- > > From: Pascal Quantin > > To: Developer support list for Wireshark > > > Sent: Thu, Dec 5, 2013 3:33 pm > > Subject: Re: [Wireshark-dev] Windows build setup - Concept required > > > > Personally I find the

Re: [Wireshark-dev] [Wireshark-commits] rev 53683: /trunk/tools/ /trunk/tools/: make-dissector-reg.py

2013-12-05 Thread Michael Tuexen
On Dec 5, 2013, at 9:42 PM, Guy Harris wrote: > > On Dec 5, 2013, at 12:27 PM, Gerald Combs wrote: > >> On 12/1/13 9:21 AM, Graham Bloice wrote: >>> >>> BTW, why is OSX using such an ancient version of Python. I believe only >>> 2.7 and 3.3 are supported by the Python folks. >> >> As I reca

Re: [Wireshark-dev] Status Cmake Win32 support

2013-12-05 Thread Graham Bloice
> > > > > I still have the issue with GTK3, in that I have to comment out the > path > > > > "corrections" in FindGTK3.cmake. > > > > > > Hmm, can you please explain the problems you are encountering - I'd > like to > > > fix them. In case it involves rewriting the results from pkg-config, > can >

Re: [Wireshark-dev] Status Cmake Win32 support

2013-12-05 Thread Graham Bloice
On 5 December 2013 21:49, Graham Bloice wrote: > > > > I still have the issue with GTK3, in that I have to comment out the >> path >> > > > "corrections" in FindGTK3.cmake. >> > > >> > > Hmm, can you please explain the problems you are encountering - I'd >> like to >> > > fix them. In case it inv

Re: [Wireshark-dev] Status Cmake Win32 support

2013-12-05 Thread Graham Bloice
On 2 December 2013 16:14, Joerg Mayer wrote: > On Mon, Dec 02, 2013 at 02:28:43PM +, Graham Bloice wrote: > > On 2 December 2013 13:49, Joerg Mayer wrote: > > > > > > > > 8. Fix build of plugins. > > > > > > > > > > They build on my system (cmake with nmake and msbuild). > > > > > > > > > >

Re: [Wireshark-dev] Windows build setup - Concept required

2013-12-05 Thread Graham Bloice
On 5 December 2013 21:06, Pascal Quantin wrote: > 2013/12/5 Christopher Maynard > >> writes: >> >> > +1 >> > >> > -Original Message- >> > From: Pascal Quantin >> > To: Developer support list for Wireshark >> >> > Sent: Thu, Dec 5, 2013 3:33 pm >> > Subject: Re: [Wireshark-dev] Window

Re: [Wireshark-dev] Windows build setup - Concept required

2013-12-05 Thread Graham Bloice
On 5 December 2013 19:59, Gerald Combs wrote: > On 12/4/13 12:27 PM, Joerg Mayer wrote: > > Hello, > > > > as Graham and I are working on getting the Windows build process to > > a) work at all and b) be on par with the current nmake build process > > we currently rely on the setup infrastructure

Re: [Wireshark-dev] Windows build setup - Concept required

2013-12-05 Thread Joerg Mayer
Before replying to some of the points, I want to clarify something: This is about problems I have encountered in a current setup (no "old" libs package, current source, clean out of tree setup and build). Also, when I mentioned setup-macosx.sh I didn't take into account that some people who are not

Re: [Wireshark-dev] Status Cmake Win32 support

2013-12-05 Thread Joerg Mayer
On Thu, Dec 05, 2013 at 10:04:36PM +, Graham Bloice wrote: > > > > They are built automagically, i.e. right now I do out of tree builds > > > > on 32 bit arch: > > > > cmake ..\..\trunk 2>&1 | tee cmake.log > > > > cmake --build . 2>&1 | tee build.log > > > > With default cmakeoptions and defau

Re: [Wireshark-dev] Status Cmake Win32 support

2013-12-05 Thread Guy Harris
On Dec 5, 2013, at 3:39 PM, Joerg Mayer wrote: > On Thu, Dec 05, 2013 at 10:04:36PM +, Graham Bloice wrote: > >> I get some warnings for qtshark: >> >> E:\Wireshark\trunk\ui\qt\capture_interfaces_dialog.ui : warning : >> The name 'layoutWidget' (QWidget) is already in use, defaulti