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

From Pavel Golub
Subject Re: Warning compiling pg_dump (MinGW, Windows XP)
Date
Msg-id 192529203.20110117125452@gf.microolap.com
Whole thread Raw
In response to Re: Warning compiling pg_dump (MinGW, Windows XP)  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Warning compiling pg_dump (MinGW, Windows XP)  (Andrew Dunstan <andrew@dunslane.net>)
Re: Warning compiling pg_dump (MinGW, Windows XP)  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Hello, Robert.

You wrote:

RH> 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?

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

Thanks Robert. What value should I enter for this option?




-- 
With best wishes,Pavel                          mailto:pavel@gf.microolap.com



pgsql-hackers by date:

Previous
From: Joel Jacobson
Date:
Subject: Re: Bug in pg_describe_object, patch v2
Next
From: Itagaki Takahiro
Date:
Subject: Re: pg_stat_replication security