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

From Tom Lane
Subject Re: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT
Date
Msg-id 3578.1526825478@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-bugs
Andrew Dunstan <andrew@dunslane.net> writes:
> On 05/20/2018 12:12 AM, Tom Lane wrote:
>> Hmm ... this might be too much of a coincidence, but I can't help noticing
>> that the places that are going south with -D__USE_MINGW_ANSI_STDIO are
>> pretty nearly the same ones I just pointed to in
>> https://www.postgresql.org/message-id/21670.1526769114@sss.pgh.pa.us
>> as using "%lf".  I'd supposed that that was mostly compulsive neatnik-ism,
>> but is it possible that mingw's "ansi stdio" library is actually
>> sensitive to that?

> Yeah, it sure is. With that applied ecpg-check actually passes on 
> frogmouth. If you apply it to all the live branches I'll re-enable the 
> tests.

Huh.  I'd have laid long odds that I was just being anal-retentive ...
but sometimes it pays.  Will push the fix later today.

            regards, tom lane


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: "158306855"
Date:
Subject: Re: [BUG] Re-entering malloc problem when use --enable-nls buildpostgresql