Wireshark mailing list archives
Re: Problem in 'packet-f5ethtrailer.c'
From: "Maynard, Chris via Wireshark-dev" <wireshark-dev () wireshark org>
Date: Thu, 19 Mar 2020 18:01:54 +0000
-----Original Message----- From: Wireshark-dev <wireshark-dev-bounces () wireshark org> On Behalf Of Gisle Vanem Sent: Thursday, March 19, 2020 1:33 PM To: wireshark-dev () wireshark org Subject: Re: [Wireshark-dev] Problem in 'packet-f5ethtrailer.c' Maynard, Chris wrote:Which specific release of VS2019 are you running? This is a bit of a stretch,but *possibly* your version could use an update? I have the latest AFAIK I ran vs_installer last week. From 'cl /?': Version 19.24.28319 for x86 From 'vswhere': VisualStudio.16.Release/16.4.6+29905.134 But IMHO, you're dodging the problem; a "#define s_addr S_un.S_addr" has been in the *Win-SDK* for ages. Nothing to do with 'cl' or it's headers.
Well, it wasn't my intention at dodging anything. My apologies if this is a dead-end. I can only say that it still appears that there's something unique or different with your build environment vs. everyone else's, including the buildbots; otherwise this problem would likely have been encountered. With very little information to go by, I'm not sure how else to try to help except to say that maybe you could compare your environment with the buildbot and look for differences. Maybe others have better suggestions. Good luck. - Chris https://buildbot.wireshark.org/wireshark-master/waterfall CONFIDENTIALITY NOTICE: This message is the property of International Game Technology PLC and/or its subsidiaries and may contain proprietary, confidential or trade secret information. This message is intended solely for the use of the addressee. If you are not the intended recipient and have received this message in error, please delete this message from your system. Any unauthorized reading, distribution, copying, or other use of this message or its attachments is strictly prohibited. ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Problem in 'packet-f5ethtrailer.c' Gisle Vanem (Mar 19)
- Re: Problem in 'packet-f5ethtrailer.c' Maynard, Chris via Wireshark-dev (Mar 19)
- Re: Problem in 'packet-f5ethtrailer.c' Gisle Vanem (Mar 19)
- Re: Problem in 'packet-f5ethtrailer.c' Graham Bloice (Mar 19)
- Re: Problem in 'packet-f5ethtrailer.c' Maynard, Chris via Wireshark-dev (Mar 19)
- Re: Problem in 'packet-f5ethtrailer.c' Jason Cohen (Mar 19)
- Re: Problem in 'packet-f5ethtrailer.c' Gisle Vanem (Mar 19)
- Re: Problem in 'packet-f5ethtrailer.c' Graham Bloice (Mar 19)
- Re: Problem in 'packet-f5ethtrailer.c' Guy Harris (Mar 19)
- Re: Problem in 'packet-f5ethtrailer.c' Guy Harris (Mar 19)
- Re: Problem in 'packet-f5ethtrailer.c' João Valverde (Mar 20)
- Re: Problem in 'packet-f5ethtrailer.c' Guy Harris (Mar 20)
- Re: Problem in 'packet-f5ethtrailer.c' João Valverde (Mar 20)
- Re: Problem in 'packet-f5ethtrailer.c' Maynard, Chris via Wireshark-dev (Mar 19)
- Re: Problem in 'packet-f5ethtrailer.c' Guy Harris (Mar 20)