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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Huong Dangminh <huo-dangminh(at)ys(dot)jp(dot)nec(dot)com>
Cc: Jonathan Allen <jallen(at)americansavingslife(dot)com>, Michael Meskes <meskes(at)postgresql(dot)org>, 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>, "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-18 17:30:46
Message-ID: 27518.1526664646@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

I wrote:
> Pushed it that way; the buildfarm will soon tell us if this was a
> stupid idea ...

BTW, after further digging I am suspicious that this means that we need
to propagate HAVE_STRTOLL and HAVE_STRTOULL into ecpg_config.h not only
pg_config.h. I'm not totally sure which compiles include just the former
not the latter.

I'm going to wait and see if the buildfarm is unhappy before trying to
change that, though. It will help prove whether we're actually getting
useful test coverage.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2018-05-18 18:11:52 Re: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT
Previous Message Tom Lane 2018-05-18 17:07:56 Re: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT