Re: [Wireshark-dev] Make CMake reuse Makefile.common?
On 03/04/15 04:07, Michal Labedzki wrote: On 03/03/15 11:50, Alexis La Goutte wrote: And also if i remember the target is only have CMake for build system (and remove autofoo...) I hope there will be only CMake in near future (imply remove autotools). As I know cmake aka build systems working for all platforms. What about remove building part of autotools, use cmake for that and use autotools for other tasks? It may work but last I checked it didn't work too well: there's a bunch of stuff that works when running from an autotools build directory that doesn't from a cmake directory. And it doesn't appear many people have been working on that. ___ 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] WS runtime error
When starting Wireshark with a specific trace file (unfortunately confidential), I get the following message on startup (git head): /home/jmayer/work/wireshark/git/ui/qt/packet_list.cpp:537:13: runtime error: load of value 9, which is not a valid value for type 'bool' Does this provide enough information? If not, what should I do to track down the cause of this? Thanks Jörg -- Joerg Mayer jma...@loplof.de We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. ___ 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 CMake reuse Makefile.common?
On 4 March 2015 at 16:44, Jeff Morriss jeff.morriss...@gmail.com wrote: On 03/04/15 04:07, Michal Labedzki wrote: On 03/03/15 11:50, Alexis La Goutte wrote: And also if i remember the target is only have CMake for build system (and remove autofoo...) I hope there will be only CMake in near future (imply remove autotools). As I know cmake aka build systems working for all platforms. What about remove building part of autotools, use cmake for that and use autotools for other tasks? It may work but last I checked it didn't work too well: there's a bunch of stuff that works when running from an autotools build directory that doesn't from a cmake directory. And it doesn't appear many people have been working on that. Maybe that should be enumerated somewhere. I've only built (off Windows) on Ubuntu using CMake and it worked for me. On Windows there are a few bits left to finish off, but I think the nmake usage is coming to an end. -- Graham Bloice ___ 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 CMake reuse Makefile.common?
On 4 March 2015 at 19:04, Jeff Morriss jeff.morriss...@gmail.com wrote: On 03/04/15 11:55, Graham Bloice wrote: On 4 March 2015 at 16:44, Jeff Morriss jeff.morriss...@gmail.com mailto:jeff.morriss...@gmail.com wrote: On 03/04/15 04:07, Michal Labedzki wrote: On 03/03/15 11:50, Alexis La Goutte wrote: And also if i remember the target is only have CMake for build system (and remove autofoo...) I hope there will be only CMake in near future (imply remove autotools). As I know cmake aka build systems working for all platforms. What about remove building part of autotools, use cmake for that and use autotools for other tasks? It may work but last I checked it didn't work too well: there's a bunch of stuff that works when running from an autotools build directory that doesn't from a cmake directory. And it doesn't appear many people have been working on that. Maybe that should be enumerated somewhere. I've only built (off Windows) on Ubuntu using CMake and it worked for me. On Windows there are a few bits left to finish off, but I think the nmake usage is coming to an end. It generally works it's just missing features. A bunch are documented in README.cmake but not all. For example I think Evan found that the test suite--at least the Lua portion--don't work in cmake builds; I fixed that in autotools (starting with https://code.wireshark.org/review/3348) but I don't think anyone has touched the cmake part (I gave up even thinking about cmake a while ago). Must force change of Jeff's viewpoint of CMake I'l be sending the vibes over later :-) -- Graham Bloice ___ 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] Wireshark 1.10.13 is now available
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm proud to announce the release of Wireshark 1.10.13. __ What is Wireshark? Wireshark is the world's most popular network protocol analyzer. It is used for troubleshooting, analysis, development and education. __ What's New Bug Fixes The following vulnerabilities have been fixed. * [1]wnpa-sec-2015-07 The WCP dissector could crash. ([2]Bug 10844) [3]CVE-2015-2188 * [4]wnpa-sec-2015-08 The pcapng file parser could crash. ([5]Bug 10895) [6]CVE-2015-2189 * [7]wnpa-sec-2015-10 The TNEF dissector could go into an infinite loop. Discovered by Vlad Tsyrklevich. ([8]Bug 11023) [9]CVE-2015-2190 The following bugs have been fixed: * IPv6 AUTH mobility option parses Mobility SPI and Authentication Data incorrectly. ([10]Bug 10626) * DHCP Option 125 Suboption: (1) option-len always expects 1 but specification allows for more. ([11]Bug 10784) * Little-endian OS X Bluetooth PacketLogger files aren't handled. ([12]Bug 10861) * X.509 certificate serial number incorrectly interpreted as negative number. ([13]Bug 10862) * H.248 ServiceChangeReasonStr messages are not shown in text generated by tshark. ([14]Bug 10879) * Clang ASAN : AddressSanitizer: global-buffer-overflow ANSI. ([15]Bug 10897) * MEGACO wrong decoding on media port. ([16]Bug 10898) * Wrong media format. ([17]Bug 10899) * BSSGP Status PDU decoding fault (missing Mandatory element (0x04) BVCI for proper packet). ([18]Bug 10903) * Packets on OpenBSD loopback decoded as raw not null. ([19]Bug 10956) * Display Filter Macro unable to edit. ([20]Bug 10957) * IPv6 Local Mobility Anchor Address mobility option code is treated incorrectly. ([21]Bug 10961) * Juniper Packet Mirror dissector expects ipv6 flow label = 0. ([22]Bug 10976) * Infinite loop DoS in TNEF dissector. ([23]Bug 11023) New and Updated Features There are no new features in this release. New Protocol Support There are no new protocols in this release. Updated Protocol Support ANSI IS-637-A, DHCP, GSM MAP, H.248, IPv6, Juniper Jmirror, and X.509AF New and Updated Capture File Support PacketLogger, and Pcapng __ Getting Wireshark Wireshark source code and installation packages are available from [24]http://www.wireshark.org/download.html. Vendor-supplied Packages Most Linux and Unix vendors supply their own Wireshark packages. You can usually install or upgrade Wireshark using the package management system specific to that platform. A list of third-party packages can be found on the [25]download page on the Wireshark web site. __ File Locations Wireshark and TShark look in several different locations for preference files, plugins, SNMP MIBS, and RADIUS dictionaries. These locations vary from platform to platform. You can use About-Folders to find the default locations on your system. __ Known Problems Dumpcap might not quit if Wireshark or TShark crashes. ([26]Bug 1419) The BER dissector might infinitely loop. ([27]Bug 1516) Capture filters aren't applied when capturing from named pipes. ([28]Bug 1814) Filtering tshark captures with read filters (-R) no longer works. ([29]Bug 2234) The 64-bit Windows installer does not support Kerberos decryption. ([30]Win64 development page) Resolving ([31]Bug 9044) reopens ([32]Bug 3528) so that Wireshark no longer automatically decodes gzip data when following a TCP stream. Application crash when changing real-time option. ([33]Bug 4035) Hex pane display issue after startup. ([34]Bug 4056) Packet list rows are oversized. ([35]Bug 4357) Summary pane selected frame highlighting not maintained. ([36]Bug 4445) Wireshark and TShark will display incorrect delta times in some cases. ([37]Bug 4985) __ Getting Help Community support is available on [38]Wireshark's QA site and on the wireshark-users mailing list. Subscription information and archives for all of Wireshark's mailing lists can be found on [39]the web site. Official Wireshark training and certification are available from [40]Wireshark University. __ Frequently Asked Questions A complete FAQ is available on the [41]Wireshark web site. __ Last updated 2015-03-04 09:06:46 PST
[Wireshark-dev] Wireshark 1.12.4 is now available
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm proud to announce the release of Wireshark 1.12.4. __ What is Wireshark? Wireshark is the world's most popular network protocol analyzer. It is used for troubleshooting, analysis, development and education. __ What's New Bug Fixes The following vulnerabilities have been fixed. * [1]wnpa-sec-2015-06 The ATN-CPDLC dissector could crash. ([2]Bug 9952) [3]CVE-2015-2187 * [4]wnpa-sec-2015-07 The WCP dissector could crash. ([5]Bug 10844) [6]CVE-2015-2188 * [7]wnpa-sec-2015-08 The pcapng file parser could crash. ([8]Bug 10895) [9]CVE-2015-2189 * [10]wnpa-sec-2015-09 The LLDP dissector could crash. ([11]Bug 10983) [12]CVE-2015-2190 * [13]wnpa-sec-2015-10 The TNEF dissector could go into an infinite loop. Discovered by Vlad Tsyrklevich. ([14]Bug 11023) [15]CVE-2015-2191 * [16]wnpa-sec-2015-11 The SCSI OSD dissector could go into an infinite loop. Discovered by Vlad Tsyrklevich. ([17]Bug 11024) [18]CVE-2015-2192 The following bugs have been fixed: * RTP player crashes on decode of long call: BadAlloc (insufficient resources for operation). ([19]Bug 2630) * Telephony-SCTP-Analyse This Association crashes Wireshark on manufactured SCTP packet. ([20]Bug 9849) * IPv6 Mobility Header Link Layer Address is parsed incorrectly. ([21]Bug 10006) * DNS NXT RR is parsed incorrectly. ([22]Bug 10615) * IPv6 AUTH mobility option parses Mobility SPI and Authentication Data incorrectly. ([23]Bug 10626) * IPv6 Mobility Header Link-Layer Address Mobility Option is parsed incorrectly. ([24]Bug 10627) * HTTP chunked response includes data beyond the chunked response. ([25]Bug 10707) * DHCP Option 125 Suboption: (1) option-len always expects 1 but specification allows for more. ([26]Bug 10784) * Incorrect decoding of IPv4 Interface/Neighbor Address sub-TLVs in Extended IS Reachability TLV of IS-IS. ([27]Bug 10837) * Little-endian OS X Bluetooth PacketLogger files aren't handled. ([28]Bug 10861) * X.509 certificate serial number incorrectly interpreted as negative number. ([29]Bug 10862) * Malformed Packet on rsync-version with length 2. ([30]Bug 10863) * ZigBee epoch time is incorrectly displayed in OTA cluster. ([31]Bug 10872) * BGP EVPN - Route Type 4 - Invalid length of IP Address - Expert Info shows a false error. ([32]Bug 10873) * Bad bytes read for extended rnc id value in GTP dissector. ([33]Bug 10877) * ServiceChangeReasonStr messages are not shown in txt generated by tshark. ([34]Bug 10879) * Clang ASAN : AddressSanitizer: global-buffer-overflow ANSI. ([35]Bug 10897) * MEGACO wrong decoding on media port. ([36]Bug 10898) * Wrong media format. ([37]Bug 10899) * BSSGP Status PDU decoding fault (missing Mandatory element (0x04) BVCI for proper packet). ([38]Bug 10903) * DNS LOC Precision missing units. ([39]Bug 10940) * Packets on OpenBSD loopback decoded as raw not null. ([40]Bug 10956) * Display Filter Macro unable to edit. ([41]Bug 10957) * IPv6 Local Mobility Anchor Address mobility option code is treated incorrectly. ([42]Bug 10961) * SNTP server list improperly formatted in DHCPv6 packet details. ([43]Bug 10964) * Juniper Packet Mirror dissector expects ipv6 flow label = 0. ([44]Bug 10976) * NS Trace (NetScaler Trace) file format is not able to export specified packets. ([45]Bug 10998) New and Updated Features There are no new features in this release. New Protocol Support There are no new protocols in this release. Updated Protocol Support ACN, ANSI IS-637-A, AppleMIDI, ATN-CPDLC, BGP, BSSGP, CMIP, DHCP, DHCPv6, DIS, DLM3, DMP, DNS, Extreme Networks, ForCES, FTAM, GMHDR, GSM A BSSMAP, GSM A-bis OML, GSM MAP, GSM RLC MAC, GTP, H.248, H.264, HTTP, IEEE 802.11, IPv6, IS-IS, ISMACryp, J1939, Juniper Jmirror, KDP, L2CAP, LDAP, LLDP, MGCP, MIP6, NBNS, NET/ROM, Netflow, Novell PKIS, PANA, PPPoE, RSL, RSYNC, RTMPT, RTP, SCSI OSD, SDP, SMB Pipe, SMPP, SYNCHROPHASOR, TETRA, TiVoConnect, TNEF, USB HID, V.52, VSS-Monitoring, X.509AF, Zebra, and ZigBee New and Updated Capture File Support NetScaler, PacketLogger, and Pcapng __ Getting Wireshark Wireshark source code and installation packages are available from [46]http://www.wireshark.org/download.html. Vendor-supplied Packages Most Linux and Unix vendors supply their own Wireshark packages. You can usually install or upgrade Wireshark using the package management system specific to
Re: [Wireshark-dev] WS runtime error
On Mar 4, 2015, at 7:29 AM, Joerg Mayer jma...@loplof.de wrote: When starting Wireshark with a specific trace file (unfortunately confidential), I get the following message on startup (git head): /home/jmayer/work/wireshark/git/ui/qt/packet_list.cpp:537:13: runtime error: load of value 9, which is not a valid value for type 'bool' Does this provide enough information? If not, what should I do to track down the cause of this? Some Googling suggests that this is an error from ASAN. If the line number is correct, perhaps the constructor for PacketList needs to initialize the tail_at_end_ member. ___ 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 CMake reuse Makefile.common?
On 03/04/15 11:55, Graham Bloice wrote: On 4 March 2015 at 16:44, Jeff Morriss jeff.morriss...@gmail.com mailto:jeff.morriss...@gmail.com wrote: On 03/04/15 04:07, Michal Labedzki wrote: On 03/03/15 11:50, Alexis La Goutte wrote: And also if i remember the target is only have CMake for build system (and remove autofoo...) I hope there will be only CMake in near future (imply remove autotools). As I know cmake aka build systems working for all platforms. What about remove building part of autotools, use cmake for that and use autotools for other tasks? It may work but last I checked it didn't work too well: there's a bunch of stuff that works when running from an autotools build directory that doesn't from a cmake directory. And it doesn't appear many people have been working on that. Maybe that should be enumerated somewhere. I've only built (off Windows) on Ubuntu using CMake and it worked for me. On Windows there are a few bits left to finish off, but I think the nmake usage is coming to an end. It generally works it's just missing features. A bunch are documented in README.cmake but not all. For example I think Evan found that the test suite--at least the Lua portion--don't work in cmake builds; I fixed that in autotools (starting with https://code.wireshark.org/review/3348) but I don't think anyone has touched the cmake part (I gave up even thinking about cmake a while ago). ___ 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 CMake reuse Makefile.common?
On Wed, Mar 4, 2015 at 2:04 PM, Jeff Morriss jeff.morriss...@gmail.com wrote: On 03/04/15 11:55, Graham Bloice wrote: On 4 March 2015 at 16:44, Jeff Morriss jeff.morriss...@gmail.com mailto:jeff.morriss...@gmail.com wrote: On 03/04/15 04:07, Michal Labedzki wrote: On 03/03/15 11:50, Alexis La Goutte wrote: And also if i remember the target is only have CMake for build system (and remove autofoo...) I hope there will be only CMake in near future (imply remove autotools). As I know cmake aka build systems working for all platforms. What about remove building part of autotools, use cmake for that and use autotools for other tasks? It may work but last I checked it didn't work too well: there's a bunch of stuff that works when running from an autotools build directory that doesn't from a cmake directory. And it doesn't appear many people have been working on that. Maybe that should be enumerated somewhere. I've only built (off Windows) on Ubuntu using CMake and it worked for me. On Windows there are a few bits left to finish off, but I think the nmake usage is coming to an end. It generally works it's just missing features. A bunch are documented in README.cmake but not all. For example I think Evan found that the test suite--at least the Lua portion--don't work in cmake builds; I fixed that in autotools (starting with https://code.wireshark.org/review/3348) but I don't think anyone has touched the cmake part (I gave up even thinking about cmake a while ago). Yes, the last time I checked the lua test suite on an out-of-tree cmake build failed because it couldn't find the right init.lua 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
Re: [Wireshark-dev] Make CMake reuse Makefile.common?
On 4 March 2015 at 20:58, Jeff Morriss jeff.morriss...@gmail.com wrote: On 03/04/15 14:10, Graham Bloice wrote: On 4 March 2015 at 19:04, Jeff Morriss jeff.morriss...@gmail.com mailto:jeff.morriss...@gmail.com wrote: On 03/04/15 11:55, Graham Bloice wrote: On 4 March 2015 at 16:44, Jeff Morriss jeff.morriss...@gmail.com mailto:jeff.morriss...@gmail.com mailto:jeff.morriss.ws@gmail.__com mailto:jeff.morriss...@gmail.com wrote: On 03/04/15 04:07, Michal Labedzki wrote: On 03/03/15 11:50, Alexis La Goutte wrote: And also if i remember the target is only have CMake for build system (and remove autofoo...) I hope there will be only CMake in near future (imply remove autotools). As I know cmake aka build systems working for all platforms. What about remove building part of autotools, use cmake for that and use autotools for other tasks? It may work but last I checked it didn't work too well: there's a bunch of stuff that works when running from an autotools build directory that doesn't from a cmake directory. And it doesn't appear many people have been working on that. Maybe that should be enumerated somewhere. I've only built (off Windows) on Ubuntu using CMake and it worked for me. On Windows there are a few bits left to finish off, but I think the nmake usage is coming to an end. It generally works it's just missing features. A bunch are documented in README.cmake but not all. For example I think Evan found that the test suite--at least the Lua portion--don't work in cmake builds; I fixed that in autotools (starting with https://code.wireshark.org/__review/3348 https://code.wireshark.org/review/3348) but I don't think anyone has touched the cmake part (I gave up even thinking about cmake a while ago). Must force change of Jeff's viewpoint of CMake I'l be sending the vibes over later :-) How about a cmake book--oh, and the time and inclination to read it (the docs and answers I found online didn't help me a lot)? Ah, I guess the inclination part may be the real problem now--so maybe the vibes /would/ help. ;-) And what is an easy cross-compilation target to aim for (with Ubuntu as the host OS)? -- Graham Bloice ___ 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 CMake reuse Makefile.common?
On 03/04/15 14:10, Graham Bloice wrote: On 4 March 2015 at 19:04, Jeff Morriss jeff.morriss...@gmail.com mailto:jeff.morriss...@gmail.com wrote: On 03/04/15 11:55, Graham Bloice wrote: On 4 March 2015 at 16:44, Jeff Morriss jeff.morriss...@gmail.com mailto:jeff.morriss...@gmail.com mailto:jeff.morriss.ws@gmail.__com mailto:jeff.morriss...@gmail.com wrote: On 03/04/15 04:07, Michal Labedzki wrote: On 03/03/15 11:50, Alexis La Goutte wrote: And also if i remember the target is only have CMake for build system (and remove autofoo...) I hope there will be only CMake in near future (imply remove autotools). As I know cmake aka build systems working for all platforms. What about remove building part of autotools, use cmake for that and use autotools for other tasks? It may work but last I checked it didn't work too well: there's a bunch of stuff that works when running from an autotools build directory that doesn't from a cmake directory. And it doesn't appear many people have been working on that. Maybe that should be enumerated somewhere. I've only built (off Windows) on Ubuntu using CMake and it worked for me. On Windows there are a few bits left to finish off, but I think the nmake usage is coming to an end. It generally works it's just missing features. A bunch are documented in README.cmake but not all. For example I think Evan found that the test suite--at least the Lua portion--don't work in cmake builds; I fixed that in autotools (starting with https://code.wireshark.org/__review/3348 https://code.wireshark.org/review/3348) but I don't think anyone has touched the cmake part (I gave up even thinking about cmake a while ago). Must force change of Jeff's viewpoint of CMake I'l be sending the vibes over later :-) How about a cmake book--oh, and the time and inclination to read it (the docs and answers I found online didn't help me a lot)? Ah, I guess the inclination part may be the real problem now--so maybe the vibes /would/ help. ;-) ___ 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 CMake reuse Makefile.common?
On 4 March 2015 at 20:58, Jeff Morriss jeff.morriss...@gmail.com wrote: On 03/04/15 14:10, Graham Bloice wrote: On 4 March 2015 at 19:04, Jeff Morriss jeff.morriss...@gmail.com mailto:jeff.morriss...@gmail.com wrote: On 03/04/15 11:55, Graham Bloice wrote: On 4 March 2015 at 16:44, Jeff Morriss jeff.morriss...@gmail.com mailto:jeff.morriss...@gmail.com mailto:jeff.morriss.ws@gmail.__com mailto:jeff.morriss...@gmail.com wrote: On 03/04/15 04:07, Michal Labedzki wrote: On 03/03/15 11:50, Alexis La Goutte wrote: And also if i remember the target is only have CMake for build system (and remove autofoo...) I hope there will be only CMake in near future (imply remove autotools). As I know cmake aka build systems working for all platforms. What about remove building part of autotools, use cmake for that and use autotools for other tasks? It may work but last I checked it didn't work too well: there's a bunch of stuff that works when running from an autotools build directory that doesn't from a cmake directory. And it doesn't appear many people have been working on that. Maybe that should be enumerated somewhere. I've only built (off Windows) on Ubuntu using CMake and it worked for me. On Windows there are a few bits left to finish off, but I think the nmake usage is coming to an end. It generally works it's just missing features. A bunch are documented in README.cmake but not all. For example I think Evan found that the test suite--at least the Lua portion--don't work in cmake builds; I fixed that in autotools (starting with https://code.wireshark.org/__review/3348 https://code.wireshark.org/review/3348) but I don't think anyone has touched the cmake part (I gave up even thinking about cmake a while ago). Must force change of Jeff's viewpoint of CMake I'l be sending the vibes over later :-) How about a cmake book--oh, and the time and inclination to read it (the docs and answers I found online didn't help me a lot)? Ah, I guess the inclination part may be the real problem now--so maybe the vibes /would/ help. ;-) Docs seem to be a perennial complaint about CMake. There is a dead-tree book (http://www.kitware.com/products/books/CMakeBook.html) that is used to support the project. -- Graham Bloice Software Developer Trihedral UK Limited ___ 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 CMake reuse Makefile.common?
On 03/04/15 16:24, Graham Bloice wrote: And what is an easy cross-compilation target to aim for (with Ubuntu as the host OS)? I'm not sure there is an easy cross-compilation target. I just know people sometimes come here asking questions or reporting problems. ___ 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] Will there be a 1.99.3 release soon?
P.S. Practically there isn't much real difference between those releases and the ones available via https://www.wireshark.org/download/automated/ - if you need a more recent pre-built version in the mean time that's probably where you should go. On Wed, Mar 4, 2015 at 5:08 PM, Evan Huus eapa...@gmail.com wrote: Gerald might have one in mind, but typically we seem to be hitting about 2 months between dev snapshots. 1.99.2 was released at the beginning of February, so that suggests to me around the beginning of April. Evan On Wed, Mar 4, 2015 at 5:06 PM, Richard Sharpe realrichardsha...@gmail.com wrote: Hi folks, Is there a schedule for a 1.99.3 release? -- Regards, Richard Sharpe (何以解憂？唯有杜康。--曹操) ___ 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] Make CMake reuse Makefile.common?
On 4 March 2015 at 22:09, Jeff Morriss jeff.morriss...@gmail.com wrote: On 03/04/15 16:24, Graham Bloice wrote: And what is an easy cross-compilation target to aim for (with Ubuntu as the host OS)? I'm not sure there is an easy cross-compilation target. I just know people sometimes come here asking questions or reporting problems. This page http://www.cmake.org/Wiki/CMake_Cross_Compiling seems to imply it's a matter of creating a CMAKE_TOOLCHAIN_FILE and passing it into the CMake command. Until we actually determine what cross-compilation is required, it'll just have to be a wishlist item. -- Graham Bloice ___ 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] Will there be a 1.99.3 release soon?
Hi folks, Is there a schedule for a 1.99.3 release? -- Regards, Richard Sharpe (何以解憂？唯有杜康。--曹操) ___ 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] Will there be a 1.99.3 release soon?
Gerald might have one in mind, but typically we seem to be hitting about 2 months between dev snapshots. 1.99.2 was released at the beginning of February, so that suggests to me around the beginning of April. Evan On Wed, Mar 4, 2015 at 5:06 PM, Richard Sharpe realrichardsha...@gmail.com wrote: Hi folks, Is there a schedule for a 1.99.3 release? -- Regards, Richard Sharpe (何以解憂？唯有杜康。--曹操) ___ 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] Will there be a 1.99.3 release soon?
I scheduled a release for tomorrow (March 5). On 3/4/15 2:08 PM, Evan Huus wrote: Gerald might have one in mind, but typically we seem to be hitting about 2 months between dev snapshots. 1.99.2 was released at the beginning of February, so that suggests to me around the beginning of April. Evan On Wed, Mar 4, 2015 at 5:06 PM, Richard Sharpe realrichardsha...@gmail.com wrote: Hi folks, Is there a schedule for a 1.99.3 release? -- Regards, Richard Sharpe (何以解憂？唯有杜康。--曹操) ___ 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] Will there be a 1.99.3 release soon?
On Wed, Mar 4, 2015 at 2:10 PM, Evan Huus eapa...@gmail.com wrote: P.S. Practically there isn't much real difference between those releases and the ones available via https://www.wireshark.org/download/automated/ - if you need a more recent pre-built version in the mean time that's probably where you should go. That should work. Thanks. On Wed, Mar 4, 2015 at 5:08 PM, Evan Huus eapa...@gmail.com wrote: Gerald might have one in mind, but typically we seem to be hitting about 2 months between dev snapshots. 1.99.2 was released at the beginning of February, so that suggests to me around the beginning of April. Evan On Wed, Mar 4, 2015 at 5:06 PM, Richard Sharpe realrichardsha...@gmail.com wrote: Hi folks, Is there a schedule for a 1.99.3 release? -- Regards, Richard Sharpe (何以解憂？唯有杜康。--曹操) ___ 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 -- Regards, Richard Sharpe (何以解憂？唯有杜康。--曹操) ___ 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] Use Transifex for manage Translations
Ok, now I have a little experience with Transifex, it seems to be ok. But there is one more question. Example :) 1. Michał translate xxx (English) to yyy (in Polish) 2. Evil Alexis change my yyy to yya (Michał do not know about that?) 3. Neutral TxPullBot pull changes to our Gerrit. I suppose that I should put -1 and fix that in Transifex? Or maybe there is way to use Transifex as Gerrit of translation? Alexis, could we test this scenario? On 3 March 2015 at 16:02, Bálint Réczey bal...@balintreczey.hu wrote: 2015-03-03 11:58 GMT+01:00 Alexis La Goutte alexis.lagou...@gmail.com: On Tue, Feb 24, 2015 at 10:54 AM, Alexis La Goutte alexis.lagou...@gmail.com wrote: Hi, I have start to use Transifex web service to manage and follow Wireshark Translations. Transifex, it is a Gerrit of translation ;-), it is possible to review translation, add comment... The idea is manage directly translation with Transifex and refuse patch about translation on Gerrit. It is possible to download and reupload directy ts file (don't need Gerrit) I think, the translation will be resync (between Gerrit/Transifex) every week, i have start a script for launch this resync. Hi, It is ok for everybody ? I don't plan working on translation thus it is OK with me if you would like to manage translations there . Do I understand correctly that you plan committing the translations in bulk through Gerrit? Either way please explain the change in the workflow on our wiki pages about contributing patches. Cheers, Balint ___ 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 -- Pozdrawiam / Best regards - Michał Łabędzki, Software Engineer Tieto Corporation Product Development Services http://www.tieto.com / http://www.tieto.pl --- ASCII: Michal Labedzki location: Swobodna 1 Street, 50-088 Wrocław, Poland room: 5.01 (desk next to 5.08) --- Please note: The information contained in this message may be legally privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, you are hereby notified that any unauthorised use, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank You. --- Please consider the environment before printing this e-mail. --- Tieto Poland spółka z ograniczoną odpowiedzialnością z siedzibą w Szczecinie, ul. Malczewskiego 26. Zarejestrowana w Sądzie Rejonowym Szczecin-Centrum w Szczecinie, XIII Wydział Gospodarczy Krajowego Rejestru Sądowego pod numerem 124858. NIP: 8542085557. REGON: 812023656. Kapitał zakładowy: 4 271500 PLN ___ 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
