Re: MinGW compiler warnings in ecpg tests

2024-12-05 Thread Thomas Munro
On Fri, Dec 6, 2024 at 4:13 AM Tom Lane wrote: > Thomas Munro writes: > > Yeah. This warning is visible on CI, and on fairywren since its MSYS2 > > upgrade a couple of months ago. Old MinGW didn't like %lld (I think > > perhaps the printf from msvcrt.dll from 1996 didn't like it and MinGW > > k

Re: MinGW compiler warnings in ecpg tests

2024-12-05 Thread Tom Lane
Thomas Munro writes: > Yeah. This warning is visible on CI, and on fairywren since its MSYS2 > upgrade a couple of months ago. Old MinGW didn't like %lld (I think > perhaps the printf from msvcrt.dll from 1996 didn't like it and MinGW > knew that), but new MinGW doesn't like %I64d (that's intere

Re: MinGW compiler warnings in ecpg tests

2024-12-05 Thread Thomas Munro
On Fri, Nov 10, 2023 at 9:00 PM Hayato Kuroda (Fujitsu) wrote: > Sorry for reviving the old thread. While trying to build postgres on msys2 by > meson, > I faced the same warning. The OS is Windows 10. Yeah. This warning is visible on CI, and on fairywren since its MSYS2 upgrade a couple of mon

RE: MinGW compiler warnings in ecpg tests

2023-11-10 Thread Hayato Kuroda (Fujitsu)
Dear Peter, Michael, Sorry for reviving the old thread. While trying to build postgres on msys2 by meson, I faced the same warning. The OS is Windows 10. ``` $ ninja [2378/2402] Compiling C object src/interfaces/ecpg/test/sql/sqlda.exe.p/meson-generated_.._sqlda.c.obj ../postgres/src/interfaces

Re: MinGW compiler warnings in ecpg tests

2019-10-29 Thread Peter Eisentraut
On 2019-10-26 10:40, Michael Meskes wrote: These files don't use our printf replacement or the c.h porting layer, so unless we want to start doing that, I propose the attached patch to determine the appropriate format conversion the hard way. I don't think such porting efforts are worth it for

Re: MinGW compiler warnings in ecpg tests

2019-10-26 Thread Michael Meskes
> These files don't use our printf replacement or the c.h porting > layer, > so unless we want to start doing that, I propose the attached patch > to > determine the appropriate format conversion the hard way. I don't think such porting efforts are worth it for a single test case, or in other word