This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
Re: PVECTORED_EXCEPTION_HANDLER undefined compiling assert.cc
- From: Corinna Vinschen <vinschen at redhat dot com>
- To: Dimitri Papadopoulos-Orfanos <papadopo at shfj dot cea dot fr>
- Cc: cygwin-developers at cygwin dot com
- Date: Thu, 9 Oct 2003 11:14:45 +0200
- Subject: Re: PVECTORED_EXCEPTION_HANDLER undefined compiling assert.cc
- References: <Pine.GSO.4.56.0310081024100.2767@eos> <20031008155304.GA6396@cygbert.vinschen.de> <3F84F382.7070104@shfj.cea.fr>
On Thu, Oct 09, 2003 at 07:34:58AM +0200, Dimitri Papadopoulos-Orfanos wrote:
> Hi,
>
> >>I get the following error trying to compile current Cygwin CVS on NT4.
> >>PVECTORED_EXCEPTION_HANDLER is defined in winnt.h. Suggestions?
> >
> >
> >I'm getting the same error now when trying to build. This seems to be
> >a new problem introduced by a checkin by Dimitri Papadopoulos-Orfanos
> >from today. I've cc'd him in this mail.
> >
> >Please test if Cygwin still builds before you're checking in stuff into
> >w32api and mingw.
>
> I'm sorry, however I'm not sure I have the resources to rebuild Cygwin.
> I usually just rebuild w32api and run its test (make test). My
> understanding was that this test is sufficient when changing only w32api.
>
> This specific problem seems to occur when defining _WIN32_WINNT,
> probably to a value of 0x0500.
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.
> Maybe the w32api test should be extended
> to be run with a variety of _WIN32_WINNT and WINVER values?
That would be a good idea, IMHO.
Corinna
--
Corinna Vinschen
Cygwin Developer
Red Hat, Inc.