Wireshark mailing list archives
Re: error encountered during compilation on windows
From: Pascal Quantin <pascal.quantin () gmail com>
Date: Tue, 11 Feb 2014 14:49:42 +0100
2014-02-11 14:38 GMT+01:00 Rahul Rohit <rahul.rohit () aricent com>:
<<WS_MSVC_NORETURN is also used in other files: dumpcap.c, epan/except.c, epan/proto.h Do you have to comment it also, or only its call in epan/except.h file?>> No we comment 'WS_MSVC_NORETURN ' only inside epan/except.h
Then there is definitely something weird / wrong on your side and it will be hard to provide you more support without extra information. As said earlier, a possible explanation would be a missing inclusion of config.h file before except.h (it will trigger exactly the same kind of warnings), something that is not done in the default Wireshark source code. So if you really have the issue with a vanilla source code, I'm out of ideas sorry. Maybe someone else will come up with something else. Pascal.
Regards Rahul Rohit *From:* wireshark-dev-bounces () wireshark org [mailto: wireshark-dev-bounces () wireshark org] *On Behalf Of *Pascal Quantin *Sent:* Tuesday, February 11, 2014 6:48 PM *To:* Developer support list for Wireshark *Subject:* Re: [Wireshark-dev] error encountered during compilation on windows 2014-02-11 13:50 GMT+01:00 Rahul Rohit <rahul.rohit () aricent com>: Hi, <<WS_MSVC_NORETURN is supposed to be defined as: #define WS_MSVC_NORETURN __declspec(noreturn) in the auto generated config.h file found at the root of your working copy. Do you confirm you have it defined in your local copy? Does it happen when you compile a specific file? If yes, do you have config.h included prior to except.h inclusion?>> The definition ' WS_MSVC_NORETURN __declspec(noreturn)' is present in our config.h file. No, the problem is general and not related to any particular file WS_MSVC_NORETURN is also used in other files: dumpcap.c, epan/except.c, epan/proto.h Do you have to comment it also, or only its call in epan/except.h file? =============================================================================== Please refer to http://www.aricent.com/legal/email_disclaimer.html for important disclosures regarding this electronic communication. =============================================================================== ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://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: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- error encountered during compilation on windows Rahul Rohit (Feb 11)
- Re: error encountered during compilation on windows Graham Bloice (Feb 11)
- Re: error encountered during compilation on windows Rahul Rohit (Feb 11)
- Re: error encountered during compilation on windows Anders Broman (Feb 11)
- Re: error encountered during compilation on windows Rahul Rohit (Feb 11)
- Re: error encountered during compilation on windows Graham Bloice (Feb 11)
- Re: error encountered during compilation on windows Rahul Rohit (Feb 11)
- Re: error encountered during compilation on windows Graham Bloice (Feb 11)
- Re: error encountered during compilation on windows Rahul Rohit (Feb 11)
- Re: error encountered during compilation on windows Pascal Quantin (Feb 11)
- Re: error encountered during compilation on windows Rahul Rohit (Feb 11)
- Re: error encountered during compilation on windows Pascal Quantin (Feb 11)
- Re: error encountered during compilation on windows Anders Broman (Feb 11)