Re: [Wireshark-dev] MSVC 2015 (VC14) notes/issue

2015-08-12 Thread Graham Bloice 
On 12 August 2015 at 17:21, Bill Meier  wrote:

> [Resend]
>
> I see that several people (Anders, ...) been building with MSVC-2015
> (VC14) and have fixed a number of issues.
>
> So: I decided to download VC14 and give it a try (using NMake).
>
> A few questions:
>
> Are you using CMake or NMake ?
>
>
I think the general plan was to move to CMake, although there are some
hold-outs.  README.cmake has the details, although there would be some
adjustments required to generate a solution for VS2015 (I think the CMake
generator option is "Visual Studio 14").

I've been meaning to update the Dev Guide to have CMake as the primary
build for Windows for some time, but spare time to do it has been limited.


> If using NMake, I assume that you've updated config.nmake & etc. Is there
> some reason you've not committed the changes ?
>
> If not, I've made what I think are the required changes for NMake. Do you
> think it's Ok to commit them ?
>
>
See change 8683, I presume that's still live Anders?


>
>
> Have you been able to do a complete build ?
>
> So far:
>
> 1. Compiling packet-pdc.c gets:
>
> [...]\packet-pdc.c(205) : fatal error C1001: An internal error has
> occurred in the compiler.
> (compiler file 'f:\dd\vctools\compiler\utc\src\p2\main.c', line 246)
>  To work around this problem, try simplifying or changing the program near
> the locations listed above.
> Please choose the Technical Support command on the Visual C++
>  Help menu, or open the Technical Support help file for more information
>
> INTERNAL COMPILER ERROR in 'C:\Program Files\Microsoft Visual Studio
> 14.0\VC\BIN\cl.exe'
> Please choose the Technical Support command on the Visual C++
> Help menu, or open the Technical Support help file for more information
>
> I've figured out what to change to fix this.
> (I've also extracted a much smaller test file which causes the error and
> will submit the file to Microsoft).
>
>
>
> 2. I had to disable building with geoip because:
>
> C:\Program Files\Windows Kits\10\include\10.0.10150.0\ucrt\stdio.h(1925):
> warning C4005: 'snprintf': macro redefinition (compiling source file packet-
> ip.c)
> [...]\GeoIP-1.5.1-2-win32ws\include\GeoIP.h(36): note: see previous
> definition of 'snprintf' (compili
> ng source file packet-ip.c)
> C:\Program Files\Windows Kits\10\include\10.0.10150.0\ucrt\stdio.h(1927):
> fatal error C1189: #error:  Macro definition of snprintf conflicts with Stan
> dard Library function declaration (compiling source file packet-ip.c)
>
>
> 3. I disabled building with LUA because there's apparently yet no LUA
> library (dll) for use with VC14.
>
>
CMake should handle that, I'd like to know if it doesn't.


>
> After addressing #1, #2 & #3 above (as well as an issue in
> packet-lwres.c), I got a complete working build (based upon a quick test).
>
>
> 4. When compiling with code-analysis enabled, I'm getting a boatload of
> the following warning message:
>
> c:\program files\windows kits\10\include\10.0.10150.0
> \ucrt\string.h(130) : warning C28252: Inconsistent annotation for
> 'strcpy': _Param_(1) has 'SAL_w
> ritableTo(elementCount(_String_length_(__formal(1,parameter1))+1))' on
> the prior instance. See (0).
>
>
> This makes using "analysis" with vc14 kind of difficult.
>

I've also noticed that elsewhere.  Looks like a MS issue with bad SAL
annotations in the SDK headers.


-- 
Graham Bloice
___
Sent via:Wireshark-dev mailing list 
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] MSVC 2015 (VC14) notes/issue

2015-08-12 Thread Pascal Quantin 
Hi,
Le 12 août 2015 6:21 PM, "Bill Meier"  a écrit :
>
> [Resend]
>
> I see that several people (Anders, ...) been building with MSVC-2015
(VC14) and have fixed a number of issues.
>
> So: I decided to download VC14 and give it a try (using NMake).
>
> A few questions:
>
> Are you using CMake or NMake ?
>
> If using NMake, I assume that you've updated config.nmake & etc. Is there
some reason you've not committed the changes ?
>
> If not, I've made what I think are the required changes for NMake. Do you
think it's Ok to commit them ?
>
>
>
> Have you been able to do a complete build ?
>
> So far:
>
> 1. Compiling packet-pdc.c gets:
>
> [...]\packet-pdc.c(205) : fatal error C1001: An internal error has
occurred in the compiler.
> (compiler file 'f:\dd\vctools\compiler\utc\src\p2\main.c', line 246)
>  To work around this problem, try simplifying or changing the program
near the locations listed above.
> Please choose the Technical Support command on the Visual C++
>  Help menu, or open the Technical Support help file for more information
>
> INTERNAL COMPILER ERROR in 'C:\Program Files\Microsoft Visual Studio
14.0\VC\BIN\cl.exe'
> Please choose the Technical Support command on the Visual C++
> Help menu, or open the Technical Support help file for more
information
>
> I've figured out what to change to fix this.
> (I've also extracted a much smaller test file which causes the error and
will submit the file to Microsoft).
>
>
>
> 2. I had to disable building with geoip because:
>
> C:\Program Files\Windows Kits\10\include\10.0.10150.0\ucrt\stdio.h(1925):
warning C4005: 'snprintf': macro redefinition (compiling source file packet-
> ip.c)
> [...]\GeoIP-1.5.1-2-win32ws\include\GeoIP.h(36): note: see previous
definition of 'snprintf' (compili
> ng source file packet-ip.c)
> C:\Program Files\Windows Kits\10\include\10.0.10150.0\ucrt\stdio.h(1927):
fatal error C1189: #error:  Macro definition of snprintf conflicts with Stan
> dard Library function declaration (compiling source file packet-ip.c)
>
>
> 3. I disabled building with LUA because there's apparently yet no LUA
library (dll) for use with VC14.

I might have a look at it when coming back from vacation if the packager I
used last time did not update the library (I have no reliable Internet
access right now, yes this is still possible nowadays :)). But I was not in
a hurry as there is no Qt package compiled with MSVC2015 yet, so we still
have a strong dependency on MSVC2013.

Pascal.

>
>
> After addressing #1, #2 & #3 above (as well as an issue in
packet-lwres.c), I got a complete working build (based upon a quick test).
>
>
> 4. When compiling with code-analysis enabled, I'm getting a boatload of
the following warning message:
>
> c:\program files\windows kits\10\include\10.0.10150.0
> \ucrt\string.h(130) : warning C28252: Inconsistent annotation for
> 'strcpy': _Param_(1) has 'SAL_w
> ritableTo(elementCount(_String_length_(__formal(1,parameter1))+1))' on
> the prior instance. See (0).
>
>
> This makes using "analysis" with vc14 kind of difficult.
>
>
> Bill
>
___
> Sent via:Wireshark-dev mailing list 
> 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 
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] MSVC 2015 (VC14) notes/issue

2015-08-12 Thread Graham Bloice 
On 12 August 2015 at 17:57, Pascal Quantin  wrote:

> Hi,
> Le 12 août 2015 6:21 PM, "Bill Meier"  a écrit :
> >
> > [Resend]
> >
> > I see that several people (Anders, ...) been building with MSVC-2015
> (VC14) and have fixed a number of issues.
> >
> > So: I decided to download VC14 and give it a try (using NMake).
> >
> > A few questions:
> >
> > Are you using CMake or NMake ?
> >
> > If using NMake, I assume that you've updated config.nmake & etc. Is
> there some reason you've not committed the changes ?
> >
> > If not, I've made what I think are the required changes for NMake. Do
> you think it's Ok to commit them ?
> >
> >
> >
> > Have you been able to do a complete build ?
> >
> > So far:
> >
> > 1. Compiling packet-pdc.c gets:
> >
> > [...]\packet-pdc.c(205) : fatal error C1001: An internal error has
> occurred in the compiler.
> > (compiler file 'f:\dd\vctools\compiler\utc\src\p2\main.c', line 246)
> >  To work around this problem, try simplifying or changing the program
> near the locations listed above.
> > Please choose the Technical Support command on the Visual C++
> >  Help menu, or open the Technical Support help file for more information
> >
> > INTERNAL COMPILER ERROR in 'C:\Program Files\Microsoft Visual Studio
> 14.0\VC\BIN\cl.exe'
> > Please choose the Technical Support command on the Visual C++
> > Help menu, or open the Technical Support help file for more
> information
> >
> > I've figured out what to change to fix this.
> > (I've also extracted a much smaller test file which causes the error and
> will submit the file to Microsoft).
> >
> >
> >
> > 2. I had to disable building with geoip because:
> >
> > C:\Program Files\Windows
> Kits\10\include\10.0.10150.0\ucrt\stdio.h(1925): warning C4005: 'snprintf':
> macro redefinition (compiling source file packet-
> > ip.c)
> > [...]\GeoIP-1.5.1-2-win32ws\include\GeoIP.h(36): note: see previous
> definition of 'snprintf' (compili
> > ng source file packet-ip.c)
> > C:\Program Files\Windows
> Kits\10\include\10.0.10150.0\ucrt\stdio.h(1927): fatal error C1189:
> #error:  Macro definition of snprintf conflicts with Stan
> > dard Library function declaration (compiling source file packet-ip.c)
> >
> >
> > 3. I disabled building with LUA because there's apparently yet no LUA
> library (dll) for use with VC14.
>
> I might have a look at it when coming back from vacation if the packager I
> used last time did not update the library (I have no reliable Internet
> access right now, yes this is still possible nowadays :)). But I was not in
> a hurry as there is no Qt package compiled with MSVC2015 yet, so we still
> have a strong dependency on MSVC2013.
>
> Pascal.
>
FYI Windows CMake doesn't currently seem to configure without Qt, I'm not
too fussed about that as on Windows the Qt version is the main build.

The QT folks had previously indicated VS2015 support would be released as a
5.5.x release so it's likely not too far off:
https://blog.qt.io/blog/2015/04/29/windows-10-support-in-qt/

Enjoying your vacation in the mountains Pascal?


-- 
Graham Bloice
___
Sent via:Wireshark-dev mailing list 
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] MSVC 2015 (VC14) notes/issue

2015-08-12 Thread Guy Harris 

On Aug 12, 2015, at 10:18 AM, Graham Bloice  wrote:

> FYI Windows CMake doesn't currently seem to configure without Qt, I'm not too 
> fussed about that as on Windows the Qt version is the main build.

...and people are probably a *lot* less likely to want CLI-only builds on 
Windows than on UN*X (on UN*X, we need to support them; people often want to 
build TShark for headless machines).

That might change some day for, say, headless Windows machines (I always find 
the notion of "headless Windows" amusing; in the world of the Internet of 
Things, if things go the way Microsoft wants them to, more machines running 
"Windows" may be incapable of displaying actual *windows* than capable of 
displaying them).
___
Sent via:Wireshark-dev mailing list 
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] MSVC 2015 (VC14) notes/issue

2015-08-12 Thread Anders Broman 

Graham Bloice skrev den 2015-08-12 19:18:
On 12 August 2015 at 17:57, Pascal Quantin > wrote:


Hi,

Le 12 août 2015 6:21 PM, "Bill Meier" mailto:wme...@newsguy.com>> a écrit :
>
> [Resend]
>
> I see that several people (Anders, ...) been building with
MSVC-2015 (VC14) and have fixed a number of issues.
>
> So: I decided to download VC14 and give it a try (using NMake).
>
> A few questions:
>
> Are you using CMake or NMake ?



I used nmake


>
> If using NMake, I assume that you've updated config.nmake & etc.
Is there some reason you've not committed the changes ?



Graham asked me to hold off until all issues was fixed ad as LUA, GeoIP 
and Qt was excluded I was in no hurry.


>
> If not, I've made what I think are the required changes for
NMake. Do you think it's Ok to commit them ?

I have no objections, it'll be easier to make sure it continues to work 
if the changes are committed.


>
>
>
> Have you been able to do a complete build ?



Yes


>
> So far:
>
> 1. Compiling packet-pdc.c gets:
>
> [...]\packet-pdc.c(205) : fatal error C1001: An internal error
has occurred in the compiler.
> (compiler file 'f:\dd\vctools\compiler\utc\src\p2\main.c', line 246)
>  To work around this problem, try simplifying or changing the
program near the locations listed above.
> Please choose the Technical Support command on the Visual C++
>  Help menu, or open the Technical Support help file for more
information
>
> INTERNAL COMPILER ERROR in 'C:\Program Files\Microsoft Visual
Studio 14.0\VC\BIN\cl.exe'
> Please choose the Technical Support command on the Visual C++
> Help menu, or open the Technical Support help file for more
information
>
> I've figured out what to change to fix this.
> (I've also extracted a much smaller test file which causes the
error and will submit the file to Microsoft).
>



I didn't encounter that problem...


>
>
> 2. I had to disable building with geoip because:
>
> C:\Program Files\Windows
Kits\10\include\10.0.10150.0\ucrt\stdio.h(1925): warning C4005:
'snprintf': macro redefinition (compiling source file packet-
> ip.c)
> [...]\GeoIP-1.5.1-2-win32ws\include\GeoIP.h(36): note: see
previous definition of 'snprintf' (compili
> ng source file packet-ip.c)
> C:\Program Files\Windows
Kits\10\include\10.0.10150.0\ucrt\stdio.h(1927): fatal error
C1189: #error:  Macro definition of snprintf conflicts with Stan
> dard Library function declaration (compiling source file
packet-ip.c)



Yes me too and that's also a comment about it in my commit, same for the 
next point..


>
>
> 3. I disabled building with LUA because there's apparently yet
no LUA library (dll) for use with VC14.

I might have a look at it when coming back from vacation if the
packager I used last time did not update the library (I have no
reliable Internet access right now, yes this is still possible
nowadays :)). But I was not in a hurry as there is no Qt package
compiled with MSVC2015 yet, so we still have a strong dependency
on MSVC2013.

Pascal.

FYI Windows CMake doesn't currently seem to configure without Qt, I'm 
not too fussed about that as on Windows the Qt version is the main build.


The QT folks had previously indicated VS2015 support would be released 
as a 5.5.x release so it's likely not too far off: 
https://blog.qt.io/blog/2015/04/29/windows-10-support-in-qt/


Enjoying your vacation in the mountains Pascal?


--
Graham Bloice


___
Sent via:Wireshark-dev mailing list 
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 
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] MSVC 2015 (VC14) notes/issue

2015-08-12 Thread Graham Bloice 
On 12 August 2015 at 18:38, Anders Broman  wrote:

> Graham Bloice skrev den 2015-08-12 19:18:
>
> On 12 August 2015 at 17:57, Pascal Quantin 
> wrote:
>
>> Hi,
>> Le 12 août 2015 6:21 PM, "Bill Meier"  a écrit :
>> >
>> > [Resend]
>> >
>> > I see that several people (Anders, ...) been building with MSVC-2015
>> (VC14) and have fixed a number of issues.
>> >
>> > So: I decided to download VC14 and give it a try (using NMake).
>> >
>> > A few questions:
>> >
>> > Are you using CMake or NMake ?
>>
>
> I used nmake
>
> >
>> > If using NMake, I assume that you've updated config.nmake & etc. Is
>> there some reason you've not committed the changes ?
>>
>
> Graham asked me to hold off until all issues was fixed ad as LUA, GeoIP
> and Qt was excluded I was in no hurry.
>
> I think the point I made was that I didn't think we should commit things
to master that don't build.  If we now have something that builds, I'm fine
with that.


-- 
Graham Bloice
___
Sent via:Wireshark-dev mailing list 
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] MSVC 2015 (VC14) notes/issue

2015-08-12 Thread Graham Bloice 
On 12 August 2015 at 18:37, Guy Harris  wrote:

>
> On Aug 12, 2015, at 10:18 AM, Graham Bloice 
> wrote:
>
> > FYI Windows CMake doesn't currently seem to configure without Qt, I'm
> not too fussed about that as on Windows the Qt version is the main build.
>
> ...and people are probably a *lot* less likely to want CLI-only builds on
> Windows than on UN*X (on UN*X, we need to support them; people often want
> to build TShark for headless machines).
>
> That might change some day for, say, headless Windows machines (I always
> find the notion of "headless Windows" amusing; in the world of the Internet
> of Things, if things go the way Microsoft wants them to, more machines
> running "Windows" may be incapable of displaying actual *windows* than
> capable of displaying them).
>
>
Good point, I forgot about folks wanting to build only tshark.  IIRC the
issue is that some of the CMake tasks to copy the 3rd party DLL's etc. seem
to complain if Qt isn't found.  Should be able to fix that up.


-- 
Graham Bloice
___
Sent via:Wireshark-dev mailing list 
Archives:https://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.12.7 is now available

2015-08-12 Thread Gerald Combs 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I'm proud to announce the release of Wireshark 1.12.7.

 __

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-21
   Protocol tree crash. ([2]Bug 11309)
 * [3]wnpa-sec-2015-22
   Memory manager crash. ([4]Bug 11373)
 * [5]wnpa-sec-2015-23
   Dissector table crash. ([6]Bug 11381)
 * [7]wnpa-sec-2015-24
   ZigBee crash. ([8]Bug 11389)
 * [9]wnpa-sec-2015-25
   GSM RLC/MAC infinite loop. ([10]Bug 11358)
 * [11]wnpa-sec-2015-26
   WaveAgent crash. ([12]Bug 11358)
 * [13]wnpa-sec-2015-27
   OpenFlow infinite loop. ([14]Bug 11358)
 * [15]wnpa-sec-2015-28
   Ptvcursor crash. ([16]Bug 11358)
 * [17]wnpa-sec-2015-29
   WCCP crash. ([18]Bug 11358)

   The following bugs have been fixed:
 * DCE RPC "Decode As" capability is missing. ([19]Bug 10368)
 * Mergecap turns nanosecond-resolution time stamps into
   microsecond-resolution time stamps. ([20]Bug 11202)
 * The Aruba ERM Type 1 Dissector inconsistent with Type 0 and Type 3.
   ([21]Bug 11204)
 * Parse CFM Type Test signal (TST) without CRC. ([22]Bug 11286)
 * Tshark: output format of rpc.xid changed from Hex to Integer.
   ([23]Bug 11292)
 * Not stop -a filecount . ([24]Bug 11305)
 * lldp.ieee.802_3.mdi_power_class display is wrong. ([25]Bug 11330)
 * Powerlink (EPL) SDO packages interpreted as frame duplication.
   ([26]Bug 11341)
 * Mysql dissector adds packet content to INFO column without
   scrubbing it. ([27]Bug 11344)
 * PIM null-register according to rfc4601 is incorrectly parsed.
   ([28]Bug 11354)
 * Wireshark Lua dissectors: both expand together. ([29]Bug 11356)
 * Link-type not retrieved for rpcap interfaces configured with
   authentication. ([30]Bug 11366)
 * SSL Decryption (RSA private key with p smaller than q) failing on
   the Windows 7 buildbot. ([31]Bug 11372)
 * [gtpv2]PCSCF ip in the Protocol configuration of update bearer
   request is not getting populated. ([32]Bug 11378)
 * wpan.src64 (and dst64) filter always gives "is not a valid EUI64
   Address" error. ([33]Bug 11380)
 * Websphere MQ Work Information Header incorrectly showing
   "Reserved". ([34]Bug 11384)
 * DUP ACK Counter resetting after Window Update. ([35]Bug 11397)
 * CSV values missing when using tshark -2 option. ([36]Bug 11401)
 * Ethernet PAUSE frames are decoded incorrectly as PFC. ([37]Bug
   11403)
 * SOCKS decoder giving strange values for seemingly normal SOCKS
   connection. ([38]Bug 11417)
 * 802.11ad decoding error. ([39]Bug 11419)

  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

   Aruba ERM, CFM, EPL, GSM A-bis OML, GSM MAP, GSM RLC/MAC, GTPv2, IEEE
   802.11, LLDP, LTE RRC, MAC Control, MQ, MySQL, OpcUa, OpenFlow,
   Radiotap, SCCP, SOCKS, TCP, WaveAgent, WCCP, and ZigBee

  New and Updated Capture File Support

   There is no new or updated capture file support in this release.
 __

Getting Wireshark

   Wireshark source code and installation packages are available from
   [40]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 [41]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. ([42]Bug 1419)

   The BER dissector might infinitely loop. ([43]Bug 1516)

   Capture filters aren't applied when capturing from named pipes.
   ([44]Bug 1814)

   Filtering tshark captures with read filters (-R) no longer works.
   ([45]Bug 2234)

   The 64-bit Windows installer does not support Kerberos decryption.
   ([46]Win64 development page)

   Resolving ([47]Bug 9044) reopens ([48]Bug 3528) so that Wireshark no
   longer automatically decodes gzip data when following a TC

[Wireshark-dev] Reload Lua plugins

2015-08-12 Thread Stig Bjørlykke 
This is news for those of you writing Lua plugins.  The latest
development automated night build[1] now have the ability to reload
Lua plugins without the need for restarting Wireshark.  It even
reloads the capture file and stays at the selected packet.

This is a brand new feature and bugs exists.  Please try it out and
report problems in bugzilla[2].

Known limitations:
- Having Lua fields in a custom column will crash at reload
- Reloading FileHandler is not supported yet
- “Show Packet in New Window” will not update after a reload and may crash


[1] https://www.wireshark.org/download/automated/
[2] https://bugs.wireshark.org/bugzilla/


-- 
Stig Bjørlykke
___
Sent via:Wireshark-dev mailing list 
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] MSVC 2015 (VC14) notes/issue

2015-08-12 Thread Bill Meier 


I used nmake


>
> If using NMake, I assume that you've updated config.nmake & etc.
Is there some reason you've not committed the changes ?





Oops: I hadn't checked for and noticed change #8683.  I would have saved 
myself a lot of effort.  I'll try it out.





>
> So far:
>
> 1. Compiling packet-pdc.c gets:
>


I didn't encounter that problem...



I'll see if I get the error with your change #8683 (and if not try to 
see what the difference is).



Bill

___
Sent via:Wireshark-dev mailing list 
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] MSVC 2015 (VC14) notes/issue

2015-08-12 Thread Bill Meier 

On 8/12/2015 3:17 PM, Bill Meier wrote:


I used nmake



Oops: I hadn't checked for and noticed change #8683.  I would have saved
myself a lot of effort.  I'll try it out.



Ok: There are a few additional changes needed to config.nmake when 
building on a 32-bit Windows system.  I'll upload a revised patch to 
change #8683 shortly.






>
> So far:
>
> 1. Compiling packet-pdc.c gets:
>


I didn't encounter that problem...



I'll see if I get the error with your change #8683 (and if not try to
see what the difference is).


I still get the failure. I'm now guessing that the issue is something 
related to building on a 32 bit system.





Bill



___
Sent via:Wireshark-dev mailing list 
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] MSVC 2015 (VC14) notes/issue

2015-08-12 Thread Pascal Quantin 
Le 12 août 2015 7:19 PM, "Graham Bloice"  a
écrit :
>
> On 12 August 2015 at 17:57, Pascal Quantin 
wrote:
>>
>> Hi,
>>
>> Le 12 août 2015 6:21 PM, "Bill Meier"  a écrit :
>> >
>> > [Resend]
>> >
>> > I see that several people (Anders, ...) been building with MSVC-2015
(VC14) and have fixed a number of issues.
>> >
>> > So: I decided to download VC14 and give it a try (using NMake).
>> >
>> > A few questions:
>> >
>> > Are you using CMake or NMake ?
>> >
>> > If using NMake, I assume that you've updated config.nmake & etc. Is
there some reason you've not committed the changes ?
>> >
>> > If not, I've made what I think are the required changes for NMake. Do
you think it's Ok to commit them ?
>> >
>> >
>> >
>> > Have you been able to do a complete build ?
>> >
>> > So far:
>> >
>> > 1. Compiling packet-pdc.c gets:
>> >
>> > [...]\packet-pdc.c(205) : fatal error C1001: An internal error has
occurred in the compiler.
>> > (compiler file 'f:\dd\vctools\compiler\utc\src\p2\main.c', line 246)
>> >  To work around this problem, try simplifying or changing the program
near the locations listed above.
>> > Please choose the Technical Support command on the Visual C++
>> >  Help menu, or open the Technical Support help file for more
information
>> >
>> > INTERNAL COMPILER ERROR in 'C:\Program Files\Microsoft Visual Studio
14.0\VC\BIN\cl.exe'
>> > Please choose the Technical Support command on the Visual C++
>> > Help menu, or open the Technical Support help file for more
information
>> >
>> > I've figured out what to change to fix this.
>> > (I've also extracted a much smaller test file which causes the error
and will submit the file to Microsoft).
>> >
>> >
>> >
>> > 2. I had to disable building with geoip because:
>> >
>> > C:\Program Files\Windows
Kits\10\include\10.0.10150.0\ucrt\stdio.h(1925): warning C4005: 'snprintf':
macro redefinition (compiling source file packet-
>> > ip.c)
>> > [...]\GeoIP-1.5.1-2-win32ws\include\GeoIP.h(36): note: see previous
definition of 'snprintf' (compili
>> > ng source file packet-ip.c)
>> > C:\Program Files\Windows
Kits\10\include\10.0.10150.0\ucrt\stdio.h(1927): fatal error C1189:
#error:  Macro definition of snprintf conflicts with Stan
>> > dard Library function declaration (compiling source file packet-ip.c)
>> >
>> >
>> > 3. I disabled building with LUA because there's apparently yet no LUA
library (dll) for use with VC14.
>>
>> I might have a look at it when coming back from vacation if the packager
I used last time did not update the library (I have no reliable Internet
access right now, yes this is still possible nowadays :)). But I was not in
a hurry as there is no Qt package compiled with MSVC2015 yet, so we still
have a strong dependency on MSVC2013.
>>
>> Pascal.
>
> FYI Windows CMake doesn't currently seem to configure without Qt, I'm not
too fussed about that as on Windows the Qt version is the main build.
>
> The QT folks had previously indicated VS2015 support would be released as
a 5.5.x release so it's likely not too far off:
https://blog.qt.io/blog/2015/04/29/windows-10-support-in-qt/
>
> Enjoying your vacation in the mountains Pascal?

Yep, in the Cevennes for now and moving to the Alps soon :)

>
>
> --
> Graham Bloice
>
>
___
> Sent via:Wireshark-dev mailing list 
> 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 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

[Wireshark-dev] MSVC 2015 (VC14) notes/issue

2015-08-12 Thread Bill Meier 

[Resend]

I see that several people (Anders, ...) been building with MSVC-2015 
(VC14) and have fixed a number of issues.


So: I decided to download VC14 and give it a try (using NMake).

A few questions:

Are you using CMake or NMake ?

If using NMake, I assume that you've updated config.nmake & etc. Is 
there some reason you've not committed the changes ?


If not, I've made what I think are the required changes for NMake. Do 
you think it's Ok to commit them ?




Have you been able to do a complete build ?

So far:

1. Compiling packet-pdc.c gets:

[...]\packet-pdc.c(205) : fatal error C1001: An internal error has 
occurred in the compiler.

(compiler file 'f:\dd\vctools\compiler\utc\src\p2\main.c', line 246)
 To work around this problem, try simplifying or changing the program 
near the locations listed above.

Please choose the Technical Support command on the Visual C++
 Help menu, or open the Technical Support help file for more information

INTERNAL COMPILER ERROR in 'C:\Program Files\Microsoft Visual Studio 
14.0\VC\BIN\cl.exe'

Please choose the Technical Support command on the Visual C++
Help menu, or open the Technical Support help file for more information

I've figured out what to change to fix this.
(I've also extracted a much smaller test file which causes the error and 
will submit the file to Microsoft).




2. I had to disable building with geoip because:

C:\Program Files\Windows 
Kits\10\include\10.0.10150.0\ucrt\stdio.h(1925): warning C4005: 
'snprintf': macro redefinition (compiling source file packet-

ip.c)
[...]\GeoIP-1.5.1-2-win32ws\include\GeoIP.h(36): note: see previous 
definition of 'snprintf' (compili

ng source file packet-ip.c)
C:\Program Files\Windows 
Kits\10\include\10.0.10150.0\ucrt\stdio.h(1927): fatal error C1189: 
#error:  Macro definition of snprintf conflicts with Stan

dard Library function declaration (compiling source file packet-ip.c)


3. I disabled building with LUA because there's apparently yet no LUA 
library (dll) for use with VC14.



After addressing #1, #2 & #3 above (as well as an issue in 
packet-lwres.c), I got a complete working build (based upon a quick test).



4. When compiling with code-analysis enabled, I'm getting a boatload of 
the following warning message:


c:\program files\windows kits\10\include\10.0.10150.0
\ucrt\string.h(130) : warning C28252: Inconsistent annotation for
'strcpy': _Param_(1) has 'SAL_w
ritableTo(elementCount(_String_length_(__formal(1,parameter1))+1))' on
the prior instance. See (0).


This makes using "analysis" with vc14 kind of difficult.


Bill
___
Sent via:Wireshark-dev mailing list 
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe