Re: Warning compiling pg_dump (MinGW, Windows XP)

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Pavel Golub <pavel(at)gf(dot)microolap(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Warning compiling pg_dump (MinGW, Windows XP)
Date: 2011-01-17 12:52:14
Message-ID: AANLkTikbdk19jaeqzBwfUKACJnq4qqm00zSu8fy97rqZ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jan 17, 2011 at 5:54 AM, Pavel Golub <pavel(at)microolap(dot)com> wrote:
> 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?

Not sure. I notice that the configure test has this comment:

# PGAC_FUNC_SNPRINTF_LONG_LONG_INT_FORMAT
# ---------------------------------------
# Determine which format snprintf uses for long long int. We handle
# %lld, %qd, %I64d. The result is in shell variable
# LONG_LONG_INT_FORMAT.
#
# MinGW uses '%I64d', though gcc throws an warning with -Wall,
# while '%lld' doesn't generate a warning, but doesn't work.
#

...and the values the test actually tries are:

%lld
%qd
%I64d

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-01-17 12:55:15 Re: texteq/byteaeq: avoid detoast [REVIEW]
Previous Message Peter Eisentraut 2011-01-17 12:48:43 Re: psql: Add \dL to show languages