Re: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT - Mailing list pgsql-bugs

From Andrew Dunstan
Subject Re: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT
Date
Msg-id 0be2fa60-a92c-f7cd-d7ea-4c675dd07fc1@dunslane.net
Whole thread Raw
In response to Re: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs

On 05/19/2018 07:33 PM, Andrew Dunstan wrote:
>
>
> On 05/19/2018 07:31 PM, Tom Lane wrote:
>>
>>>      /* add this define on XP only, not needed elsewhere */
>>>      #ifdef WIN32_WINNT
>>>      #if WIN32_WINNT < 0x0600
>>>      #define __USE_MINGW_ANSI_STDIO 1
>>>      #endif
>>>      #endif
>> I'd be inclined to just stick -D__USE_MINGW_ANSI_STDIO=1 into
>> frogmouth's configuration.  Given that we've already tossed
>> support for XP overboard in HEAD, it would seem a bit silly
>> to put it back in this way.
>>
>>
>
>
>
> Good point. Doing that now.
>


Well that seems to have crashed and burned badly. I'm just going to 
disable ecpg checks on this animal as suggested upthread.

cheers

andrew



pgsql-bugs by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT
Next
From: Tom Lane
Date:
Subject: Re: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT