Re: [Wireshark-dev] Supported Python versions?
Hi Peter, 2015-03-24 18:17 GMT+01:00 Peter Wu pe...@lekensteyn.nl: On Sun, Mar 22, 2015 at 04:58:14PM +0100, Pascal Quantin wrote: 2015-03-22 16:48 GMT+01:00 Peter Wu pe...@lekensteyn.nl: Hi, Triggered by a build error due to html2text.py, I have recently started with adding Python 3 support to various Python scripts[1][2]. The change to html2text.py[1] was tested with Python 2.6, 2.7, 3.2 and 3.4. The configure script however checks for Python = 2.5 which was first released in 2006 with the last security update in 2011. This version also lacks support for nice language constructs such as 'with'. checklicenses.py is already incompatible with this. Any objections if this gets bumped to 2.6 or even 2.7? The dfilter-test.py script already requires 2.7 (or newer). Hi Peter, the OSX 10.5 x86 buildbot still runs Python 2.5, so bumping the minimum Python version would require updating the buildbot. So it's better to keep compatibility for the scripts used during build steps. Pascal. According to the ComputerWorld source listed by Wikipedia[1], OS X 10.5 became unsupported since June 2011. Python 2.5 also does not receive security updates anymore. (OS X 10.6 has Python 2.7 which is still supported.) Since we use Python with verified input and only for building Wireshark the security concerns don't apply here. Otherwise I think it would be OK to move to newer Python version. Cheers, Balint ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:https://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] CMake on Windows - Can build, but not run executable
I seem to remember earlier issues with other folks using VS2012 and wanting a 64 bit build, due to qt support problems. VS2013 CE is available for free, you might want to consider that. As for CMake build instructions did you look at README.cmake in the top level sources? When we get CMake totally sorted, I'll update the Developers Guide to use that rather than nmake. Still some things to do yet. On 26 March 2015 at 13:10, Roland Knall rkn...@gmail.com wrote: Hi I have only VStudio 2012 available here at my workplace. Using CMake 3.0.2, msvc2012_64_opengl. The error log (in german) produces the following output: = Startet die Generierung des Aktivierungskontextes. Eingabeparameter: Flags = 0 ProcessorArchitecture = AMD64 CultureFallBacks = de-DE;de ManifestPath = C:\dev\Wireshark\cmakebuild\run\wireshark-gtk.exe AssemblyDirectory = C:\dev\Wireshark\cmakebuild\run\ Application Config File = - INFORMATION: Manifestdatei C:\dev\Wireshark\cmakebuild\run\wireshark-gtk.exe wird analysiert. INFORMATION: Die Manifestsdefinitionsidentität ist (null). FEHLER: Zeile 8: Der Wert des processorArchitecture-Attributs im assemblyIdentity-Element ist ungültig. FEHLER: Bei der Generierung des Aktivierungskontextes ist ein Fehler aufgetreten. Beendet die Generierung des Aktivierungskontextes. I am trying to build with 32bit now, and will keep you updated. I've figured it may have something to do with Qt, and the fact, that the package for opensource is only supporting 64 bit with VStudio2013. Why tshark and wireshark-gtk are affected by this, I can't really figure out. Btw, should there be another page on the wiki for building with cmake on Windows? Running the setup script was one thing, but the main thing with my devenv.bat was, that I used to set WIRESHARK_BASE_DIR, but with that I never got the build running. As soon as I set WIRESHARK_LIB_DIR as environment variable, the build worked. I used the stdio information from the buildbot to figure it out, but others may well have some issues here. regards, Roland On Wed, Mar 25, 2015 at 6:32 PM, Graham Bloice graham.blo...@trihedral.com wrote: On 25 March 2015 at 08:17, Roland Knall rkn...@gmail.com wrote: Hi I can build wireshark successfully (gtk and qt interfaces) on Windows, but If I want to execute it, he complains that the side-by-side configuration is not correct. If I trace the launch with sxstrace, he complains, that the ProcessorArchitecture is wrong for the target (amd64). The build is a Windows 64bit build Using VS2013, CMake 3.1.3, QT 5.4.1 msvc2013_64_opengl. I don't normally build x64, so gave it a go using the x64 native compiler and CMake fails configure, the testing for various sizes fails as CMake is asking the linker to use both x64 and x86 modes?? If I use the cross compiler (i.e. x86 building x64) then CMake does configure and the resulting build runs for me (both qt and gtk). I usually run depends (http://www.dependencywalker.com/) to check what DLL's etc are to be loaded. -- Graham Bloice ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:https://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:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org ?subject=unsubscribe -- Graham Bloice Software Developer Trihedral UK Limited ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:https://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] CMake on Windows - Can build, but not run executable
Hi The 32bit is not working either. I am not trying to upgrade my Qt version (although I really can't figure out what the issue should be here for tshark and wireshark-gtk, and if this is not working, I'll try your debug scenario. VS2013 is unfortunately not allowed in our company, not even the CE version, and therefore not an option for me. regards, Roland On Thu, Mar 26, 2015 at 2:19 PM, Graham Bloice graham.blo...@trihedral.com wrote: I seem to remember earlier issues with other folks using VS2012 and wanting a 64 bit build, due to qt support problems. VS2013 CE is available for free, you might want to consider that. As for CMake build instructions did you look at README.cmake in the top level sources? When we get CMake totally sorted, I'll update the Developers Guide to use that rather than nmake. Still some things to do yet. On 26 March 2015 at 13:10, Roland Knall rkn...@gmail.com wrote: Hi I have only VStudio 2012 available here at my workplace. Using CMake 3.0.2, msvc2012_64_opengl. The error log (in german) produces the following output: = Startet die Generierung des Aktivierungskontextes. Eingabeparameter: Flags = 0 ProcessorArchitecture = AMD64 CultureFallBacks = de-DE;de ManifestPath = C:\dev\Wireshark\cmakebuild\run\wireshark-gtk.exe AssemblyDirectory = C:\dev\Wireshark\cmakebuild\run\ Application Config File = - INFORMATION: Manifestdatei C:\dev\Wireshark\cmakebuild\run\wireshark-gtk.exe wird analysiert. INFORMATION: Die Manifestsdefinitionsidentität ist (null). FEHLER: Zeile 8: Der Wert des processorArchitecture-Attributs im assemblyIdentity-Element ist ungültig. FEHLER: Bei der Generierung des Aktivierungskontextes ist ein Fehler aufgetreten. Beendet die Generierung des Aktivierungskontextes. I am trying to build with 32bit now, and will keep you updated. I've figured it may have something to do with Qt, and the fact, that the package for opensource is only supporting 64 bit with VStudio2013. Why tshark and wireshark-gtk are affected by this, I can't really figure out. Btw, should there be another page on the wiki for building with cmake on Windows? Running the setup script was one thing, but the main thing with my devenv.bat was, that I used to set WIRESHARK_BASE_DIR, but with that I never got the build running. As soon as I set WIRESHARK_LIB_DIR as environment variable, the build worked. I used the stdio information from the buildbot to figure it out, but others may well have some issues here. regards, Roland On Wed, Mar 25, 2015 at 6:32 PM, Graham Bloice graham.blo...@trihedral.com wrote: On 25 March 2015 at 08:17, Roland Knall rkn...@gmail.com wrote: Hi I can build wireshark successfully (gtk and qt interfaces) on Windows, but If I want to execute it, he complains that the side-by-side configuration is not correct. If I trace the launch with sxstrace, he complains, that the ProcessorArchitecture is wrong for the target (amd64). The build is a Windows 64bit build Using VS2013, CMake 3.1.3, QT 5.4.1 msvc2013_64_opengl. I don't normally build x64, so gave it a go using the x64 native compiler and CMake fails configure, the testing for various sizes fails as CMake is asking the linker to use both x64 and x86 modes?? If I use the cross compiler (i.e. x86 building x64) then CMake does configure and the resulting build runs for me (both qt and gtk). I usually run depends (http://www.dependencywalker.com/) to check what DLL's etc are to be loaded. -- Graham Bloice ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:https://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:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org ?subject=unsubscribe -- Graham Bloice Software Developer Trihedral UK Limited ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:https://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:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
Re: [Wireshark-dev] Supported Python versions?
Bálint Réczey balint@... writes: Since we use Python with verified input and only for building Wireshark the security concerns don't apply here. Otherwise I think it would be OK to move to newer Python version. Not that we must, but maybe we could plan on bumping minimum required versions (Python, Qt[1], etc.) according to schedules such as RHEL's[2]? As Luke mentioned, RHEL6 ships with Python 2.6, so I would not be in favor of requiring a minimum of Python 2.7 until at least the end of the RHEL6 Production 1 Phase. - Chris [1]: https://www.wireshark.org/lists/wireshark-dev/201408/msg00074.html [2]: https://access.redhat.com/support/policy/updates/errata ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
