Re: Problem in 'packet-f5ethtrailer.c'

[Jason Cohen <kryojenik2 () gmail com>]

Gisle,

Do you have the steps you used to setup your build environment, and then
the steps to build Wireshark? Unless we're able to reproduce it, there may
be little we can do.  It certainly hasn't been something I've seen either.

Jason

On Thu, Mar 19, 2020 at 12:34 PM Gisle Vanem <gisle.vanem () gmail com> wrote:

> 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.
>
> --
> --gv
> ___________________________________________________________________________
> 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
___________________________________________________________________________
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