Re: Warning compiling pg_dump (MinGW, Windows XP) - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Warning compiling pg_dump (MinGW, Windows XP)
Date
Msg-id AANLkTimfi2jujkEEv+HcWRSy4vkP--ZDLr9wA=taDrBs@mail.gmail.com
Whole thread Raw
In response to Warning compiling pg_dump (MinGW, Windows XP)  (Pavel Golub <pavel@microolap.com>)
Responses Re: Warning compiling pg_dump (MinGW, Windows XP)  (Pavel Golub <pavel@microolap.com>)
Re: Warning compiling pg_dump (MinGW, Windows XP)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
2011/1/13 Pavel Golub <pavel@microolap.com>:
> Hello, Pgsql-hackers.
>
> I'm getting such warnings:
>
> pg_dump.c: In function 'dumpSequence':
> pg_dump.c:11449:2: warning: unknown conversion type character 'l' in format
> pg_dump.c:11449:2: warning: too many arguments for format
> pg_dump.c:11450:2: warning: unknown conversion type character 'l' in format
> pg_dump.c:11450:2: warning: too many arguments for format
>
> Line numbers my not be the same in the official sources, because I've
> made some changes. But the lines are:
>
>        snprintf(bufm, sizeof(bufm), INT64_FORMAT, SEQ_MINVALUE);
>        snprintf(bufx, sizeof(bufx), INT64_FORMAT, SEQ_MAXVALUE);
>
> In my oppinion configure failed for MinGw+Windows in this case. Am I
> right? Can someone give me a hint how to avoid this?

It seems like PGAC_FUNC_SNPRINTF_LONG_LONG_INT_FORMAT is getting the
wrong answer on your machine, though I'm not sure why.  The easiest
workaround is probably to run configure and then edit
src/include/pg_config.h before compiling.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: walreceiver fallback_application_name
Next
From: Tatsuo Ishii
Date:
Subject: Re: Streaming base backups