Re: Complier warnings on mingw gcc 4.5.0

On 12/15/2010 08:46 PM, Tom Lane wrote:
>
>> I believe #2 is in fact necessary. When I tried just #1 before it
>> failed. What's the best way to do #2 cleanly?
> We can't change the meaning of HAVE_INT_OPTRESET because that would
> break the declaration logic in getopt.c.  I'm thinking we have to
> complicate the #if logic in postmaster.c and postgres.c.

I agree.

> Will look
> into it as soon as I get done with the contrib/seg patch (ie in an
> hour or so).
>
>             

OK. I'll test any patch you post ASAP.

cheers

andrew