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.
As a counterpoint, I compiled today with the latest VS2019, no issue at all. From vswhere, the version is VisualStudio.16.Release/16.5.0+29911.84, so slightly newer than your version. I do only build x64 though, not x86.
