This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
[Fwd: Re: PVECTORED_EXCEPTION_HANDLER undefined compiling assert.cc]
- From: Earnie Boyd <earnie_boyd at yahoo dot com>
- To: Cygwin Developers <cygwin-developers at cygwin dot com>
- Date: Thu, 09 Oct 2003 08:26:22 -0400
- Subject: [Fwd: Re: PVECTORED_EXCEPTION_HANDLER undefined compiling assert.cc]
-------- Original Message --------
Subject: Re: PVECTORED_EXCEPTION_HANDLER undefined compiling assert.cc
Date: Thu, 09 Oct 2003 08:13:57 -0400
From: Earnie Boyd <earnie@users.sf.net>
To: Corinna Vinschen <vinschen@redhat.com>
CC: Dimitri Papadopoulos-Orfanos <papadopo@shfj.cea.fr>,
cygwin-developers@cygwin.com
References: <Pine.GSO.4.56.0310081024100.2767@eos>
<20031008155304.GA6396@cygbert.vinschen.de>
<3F84F382.7070104@shfj.cea.fr> <20031009091445.GB13721@cygbert.vinschen.de>
Corinna Vinschen wrote:
I've checked in a patch in CVS. The problem was raised by
PVECTORED_EXCEPTION_HANDLER defined only if _WIN32_WINNT >= 0x0501
but the usage in winbase was guarded by _WIN32_WINNT >= 0x0500.
Cygwin sets _WIN32_WINNT to 0x0500.
Cygwin should consider a higher value for _WIN32_WINNT since it handles
the OS Version discrepencies with it's autoload feature. The time to
change the value would be at the first use of a new feature of a new
version of OS. So if you're using Windows XP specific declarations then
you need to modify your value of _WIN32_WINNT to 0x0501. If you're
using Windows 2003 specific declarations then you should set it to what
ever value MS has deemed to represent that version of Win32 OS.
Earnie.
--
http://www.mingw.org