Re: Complier warnings on mingw gcc 4.5.0

Magnus Hagander <magnus@hagander.net>

From: Magnus Hagander <magnus@hagander.net>

To: Tom Lane <tgl@sss.pgh.pa.us>

Cc: Andrew Dunstan <andrew@dunslane.net>, Alvaro Herrera <alvherre@commandprompt.com>, Itagaki Takahiro <itagaki.takahiro@gmail.com>, Hiroshi Inoue <inoue@tpf.co.jp>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>

Date: 2010-12-15T16:45:28Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Make the win32 putenv() override update *all* present versions of the
- 741e4ad7de9e 9.0.0 cited
Remove the use of the pg_auth flat file for client authentication.
- e710b65c1c56 9.0.0 cited

On Wed, Dec 15, 2010 at 17:43, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Andrew Dunstan <andrew@dunslane.net> writes:
>> On 12/15/2010 11:12 AM, Tom Lane wrote:
>>> 1. Is that build using src/port/getopt.c, or a library-supplied getopt?
>>> What about getopt_long.c?
>>>
>>> 2. Is HAVE_INT_OPTRESET getting defined?  Should it be?
>
>> I had the same thought. I did try forcing use of our getopt and
>> getopt_long, without success, but didn't look at optreset.
>
> Do we use configure at all on a mingw build?  If we don't, then
> HAVE_INT_OPTRESET is surely not getting defined.

We do use configure on mingw. The output from a regular mingw
configure run formed the base for the config file we use for MSVC
where we can't run it, but an actual mingw build will re-run configure
every time.


-- 
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/