> You should rather add the #define NOCRYPT, but otherwise the answer is
> "yes". We switched to the newer set of Windows header files deliberately.
Thank you. I will do that.
--
Eduardo
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Do
On Dec 13 18:12, Eduardo Chappa wrote:
> >> This used to work in the past, there was no need to switch the order, but
> >> it fails now. Why?
>
> > Because the new Windows headers from Mingw64 define X509_NAME and
> > OCSP_RESPONSE, which the former Mingw32 Windows headers didn't.
>
> Hi Corinna
>> This used to work in the past, there was no need to switch the order, but it
>> fails now. Why?
> Because the new Windows headers from Mingw64 define X509_NAME and
> OCSP_RESPONSE, which the former Mingw32 Windows headers didn't.
Hi Corinna,
Thank you for your reply. In this case, the reas
On Dec 13 16:37, Eduardo Chappa wrote:
> Hello,
>
> I am trying to understand why a program that used to compile before, now it
> does not. I can make the program compile if I switch the order of the
> #include directives.
> [...]
> #include
> #include
> #include
>
> int main(int argc, cha
Hello,
I am trying to understand why a program that used to compile before, now it
does not. I can make the program compile if I switch the order of the #include
directives.
Here is a minimal example:
file: success.c
#include
#include
#include
int main(int argc, char *argv[])
{
return 0
5 matches
Mail list logo
