Re: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Huong Dangminh <huo-dangminh(at)ys(dot)jp(dot)nec(dot)com>, Jonathan Allen <jallen(at)americansavingslife(dot)com>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Michael Meskes <meskes(at)postgresql(dot)org>, Akio Iwaasa <aki-iwaasa(at)vt(dot)jp(dot)nec(dot)com>
Subject: Re: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT
Date: 2018-05-20 13:38:18
Message-ID: c085e1da-0d64-1c15-242d-c921f32e0d5c@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 05/20/2018 12:12 AM, Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>> Well that seems to have crashed and burned badly. I'm just going to
>> disable ecpg checks on this animal as suggested upthread.
> 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.

cheers

andrew

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2018-05-20 14:11:18 Re: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT
Previous Message Milorad Krstevski 2018-05-20 10:34:50 Re: BUG #15206: Can not import CSV into PostgreSQL