Skip site navigation (1) Skip section navigation (2)

Re: win32 build and test issues

From: "Andrew Dunstan" <andrew(at)dunslane(dot)net>
To: <claudio(dot)natoli(at)memetrics(dot)com>
Cc: <andrew(at)dunslane(dot)net>, <pgsql-hackers-win32(at)postgresql(dot)org>
Subject: Re: win32 build and test issues
Date: 2004-04-30 12:13:35
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers-win32
Claudio Natoli said:
>> The first is the fix I made in configure - on my W2K machine with the
>> current MinGW/MSys I was getting the previously reported symlink
>> problem  every time. With the looping patch (yes I *know* it's ugly,
>> and we have  to get to the root of the problem, but I wanted to get
>> past it for now)  it never happened, and builds worked. In any case we
>> should use  something like the last couple of lines at least, to
>> *show* something  went wrong. As we have it now we say we are doing
>> something and not  testing for failure.
> FWIW, I agree. I'd rather have a few unfortunate lines in the configure
> code, than a few hundred (or more) questions from Win32 users asking
> why they can't build.

Yeah. I think we need either to do something like what I did or find a
better solution.

>> The regression tests themselves seem to fail for the most
>> part in every configuration I have tried. The problem seems to be
>> mostly
> buffering
>> issues - error messages appear out of order from what is expected. I
>> have not made sure what passes if we ignore that issue.
> It is a MingW problem. Appears like there is not much we can do about
> it. Refer to
> for
> details on how to test outside of Ming.

I am not giving up on it yet. I have a couple of ideas I'm going to try.
Telling people they have to run the tests under cygwin is just horrible.



In response to


pgsql-hackers-win32 by date

Next:From: Andrew DunstanDate: 2004-04-30 15:00:12
Subject: Re: win32 build and test issues
Previous:From: Magnus HaganderDate: 2004-04-30 07:38:41
Subject: Re: win32 build and test issues

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group