This is a static archive of our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

stdint.h error on building wireshark 1.12.6

0
ERROR in Stdint.h

c:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\INCLUDE\stdint.h(1) : error C2018: unknown character '0x12' c:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\INCLUDE\stdint.h(1) : error C2018: unknown character '0x2' c:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\INCLUDE\stdint.h(1) : error C2061: syntax error : identifier 'stdint' c:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\INCLUDE\stdint.h(1) : error C2059: syntax error : ';' c:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\INCLUDE\stdint.h(1) : error C2059: syntax error : '.' c:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\INCLUDE\stdint.h(1) : error C2017: illegal escape sequence c:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\INCLUDE\stdint.h(1) : error C2017: illegal escape sequence c:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\INCLUDE\stdint.h(1) : error C2017: illegal escape sequence c:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\INCLUDE\stdint.h(1) : error C2017: illegal escape sequence c:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\INCLUDE\stdint.h(1) : error C2017: illegal escape sequence c:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\INCLUDE\stdint.h(1) : error C2018: unknown character '0x3' c:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\INCLUDE\stdint.h(1) : error C2017: illegal escape sequence c:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\INCLUDE\stdint.h(1) : error C2017: illegal escape sequence c:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\INCLUDE\stdint.h(1) : error C2017: illegal escape sequence c:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\INCLUDE\stdint.h(1) : error C2017: illegal escape sequence c:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\INCLUDE\stdint.h(1) : error C2017: illegal escape sequence c:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\INCLUDE\stdint.h(1) : error C2017: illegal escape sequence c:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\INCLUDE\stdint.h(1) : error C2018: unknown character '0x10' c:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\INCLUDE\stdint.h(143) : fatal error C1071: unexpected end of file found in comment NMAKE : fatal error U1077: '"c:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\BIN\cl.EXE"' : return code '0x2' Stop. NMAKE : fatal error U1077: '"c:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\BIN\nmake.exe"' : return code '0x2' Stop.

asked 17 Mar ‘17, 03:19

DhanuShalz's gravatar image

DhanuShalz
36101115
accept rate: 100%

edited 17 Mar ‘17, 04:46

grahamb's gravatar image

grahamb ♦
19.8k330206

1

What version of Wireshark are you attempting to build?

(17 Mar ‘17, 03:47) grahamb ♦

wireshark 1.12.6

(17 Mar ‘17, 03:52) DhanuShalz


One Answer:

0

Microsoft Visual Studio 9.0

Is that Visual Studio 2008?

If so, we haven't use VS 2008 to build Wireshark releases since Wireshark 1.6. The Windows toolchain page in the Developer's Guide only talks about VS 2010 and later. There's no guarantee that current versions of Wireshark will build on VS 2008 - and there's no guarantee that, if you take some random version of stdint.h and install it, it will work with VS 2008.

answered 17 Mar '17, 03:54

Guy%20Harris's gravatar image

Guy Harris ♦♦
17.4k335196
accept rate: 19%

Thanks, That worked but very further it throught the error

packet-ipmi-app.c packet-ipmi-bridge.c packet-ipmi-chassis.c packet-ipmi-picmg.c packet-ipmi-se.c packet-ipmi-storage.c packet-ipmi-transport.c packet-ipmi-pps.c packet-ipmi-update.c packet-ipmi-vita.c packet-dcerpc-nt.c usb.c NMAKE : fatal error U1077: '"c:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\BIN\cl.EXE"' : return code '0x2' Stop. NMAKE : fatal error U1077: '"c:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\BIN\nmake.exe"' : return code '0x2' Stop. NMAKE : fatal error U1077: '"c:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\BIN\nmake.exe"' : return code '0x2' Stop.

(17 Mar '17, 04:30) DhanuShalz

The "official" build toolchain for 1.12.6 is Visual Studio 2010.

(17 Mar '17, 04:45) grahamb ♦

the same was working for the VS2008

(17 Mar '17, 04:50) DhanuShalz

packet-frame.c file-file.c C:\Aravind\Project\SVN\CalyposoGeneralTools\trunk\Wireshark_Plugin\WSI_Simple\epan\color_filters.h(40) : error C2371: 'color_t' : redefinition; different basic types C:\Aravind\Project\SVN\CalyposoGeneralTools\trunk\Wireshark_Plugin\WSI_Simple\color.h(44) : see declaration of 'color_t' C:\Aravind\Project\SVN\CalyposoGeneralTools\trunk\Wireshark_Plugin\WSI_Simple\epan\color_filters.h(40) : error C2371: 'color_t' : redefinition; different basic types C:\Aravind\Project\SVN\CalyposoGeneralTools\trunk\Wireshark_Plugin\WSI_Simple\color.h(44) : see declaration of 'color_t' NMAKE : fatal error U1077: '"c:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\BIN\cl.EXE"' : return code '0x2' Stop. NMAKE : fatal error U1077: '"c:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\BIN\nmake.exe"' : return code '0x2' Stop. NMAKE : fatal error U1077: '"c:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\BIN\nmake.exe"' : return code '0x2' Stop.

(17 Mar '17, 04:51) DhanuShalz

The official builds were made with VS 2010 SP1 and 1.12 is now out of support so you're pretty much on your own, especially if trying to persist with VS 2008 which was last officially used for 1.6.

(17 Mar '17, 04:55) grahamb ♦

epan\color_filters.h(40) : error C2371: 'color_t' : redefinition; different basic types _Simple\color.h(44) : see declaration of 'color_t' epan\color_filters.h(40) : error C2371: 'color_t' : redefinition; different basic types _Simple\color.h(44) : see declaration of 'color_t'

ANY INPUT ON THIS PARTICULAR ERROR

(17 Mar '17, 04:58) DhanuShalz

You seem to have a proprietary file color.h that uses a structure named color_t like the one provided by Wireshark (in epan\color_filters.h) but with a different content. You need to modify your code to avoid this error (either rename the structure, or ensure they are defined the same way. As we do not have access to your local modifications, you are on your own here.

(17 Mar '17, 08:00) Pascal Quantin
showing 5 of 7 show 2 more comments