Re: mingw check hung

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: mingw check hung
Date: 2009-01-30 16:13:34
Message-ID: 4983272E.8080201@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan wrote:
>
>
> Magnus Hagander wrote:
>> Andrew Dunstan wrote:
>>
>>> Magnus Hagander wrote:
>>>
>>>> Are we *sure*, btw, that this is actually a mingw issue, and not
>>>> something else in the environment? Could you try a MSVC compiled
>>>> binary
>>>> on the same machine?
>>>>
>>> My MSVC buildfarm animal runs on the same machine, and does not suffer
>>> the same problem.
>>>
>>
>> Meh. Stupid mingw :-)
>>
>> So how about we #ifdef out that NULL setting based on
>> WIN32_ONLY_COMPILER, does that seem reasonable?
>>
>>
>>
>
> The odd thing is that it doesn't seem to affect Vista, only XP.
>
> Anyway, yes, I think that would be OK. How do we then test to see if
> the original problem is still fixed?
>
>

Further proof that this is a Windows version issue: I took the problem
build from my XP and put it on my Vista box: the same build that causes
a problem on XP runs perfectly on Vista. Go figure. Maybe we need a
version check at runtime? That would be icky.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-01-30 16:27:56 Re: using composite types in insert/update
Previous Message Merlin Moncure 2009-01-30 16:01:53 Re: using composite types in insert/update