[openssl.org #1684] bug: name collision with Windows SDK

2008-06-02 Thread David W. Thomas via RT
The following produced a series of compiler errors that seem unrelated to the cause: #include #include I tracked it down to a name collision of: typedef struct ocsp_response_st OCSP_RESPONSE; within openssl/ossl_typ.h collides with #define OCSP_RESPONSE ((LPCSTR) 67) with

Re: [openssl.org #1684] bug: name collision with Windows SDK

2008-06-02 Thread [EMAIL PROTECTED]
- > typedef struct ocsp_response_st OCSP_RESPONSE; > > > > within openssl/ossl_typ.h collides with > > > > #define OCSP_RESPONSE ((LPCSTR) 67) > > > > within WinCrypt.h, a windows header file (Microsoft Windows SDK 6.0A). > There are work-arounds, but the compiler errors led to a few hour

Re: [openssl.org #1684] bug: name collision with Windows SDK

2008-06-02 Thread Dr. Stephen Henson
On Mon, Jun 02, 2008, [EMAIL PROTECTED] wrote: > > - > > typedef struct ocsp_response_st OCSP_RESPONSE; > > > > > > > > within openssl/ossl_typ.h collides with > > > > > > > > #define OCSP_RESPONSE ((LPCSTR) 67) > > > > > > > > within WinCrypt.h, a windows header file (Microsoft Windows

Re: [openssl.org #1684] bug: name collision with Windows SDK

2008-06-03 Thread Roumen Petrov
[EMAIL PROTECTED] wrote: - typedef struct ocsp_response_st OCSP_RESPONSE; within openssl/ossl_typ.h collides with #define OCSP_RESPONSE ((LPCSTR) 67) within WinCrypt.h, a windows header file (Microsoft Windows SDK 6.0A). There are work-arounds, but the compiler errors led to a few hours