Re: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT
От | Andrew Dunstan |
---|---|
Тема | Re: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT |
Дата | |
Msg-id | c085e1da-0d64-1c15-242d-c921f32e0d5c@dunslane.net обсуждение исходный текст |
Ответ на | Re: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: BUG #15080: ecpg on windows doesn't define HAVE_LONG_LONG_INT
|
Список | pgsql-bugs |
On 05/20/2018 12:12 AM, Tom Lane wrote: > Andrew Dunstan <andrew@dunslane.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
В списке pgsql-bugs по дате отправления: