From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | "Andrew Dunstan" <andrew(at)dunslane(dot)net>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: mingw configure failure detection |
Date: | 2004-05-12 16:56:27 |
Message-ID: | 26235.1084380987@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-hackers-win32 pgsql-patches |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Am Montag, 10. Mai 2004 09:17 schrieb Andrew Dunstan:
>> It appears that Dann Corbit has filed a MinGW bug on this, with accurate
>> problem description, but he received a less than stellar response. See
>>
>> https://sourceforge.net/tracker/index.php?
>> func=detail&aid=931263&group_id=2435&atid=102435
> I added a followup to this bug and he requests a minimal reproduceable
> example. Can someone provide one?
From what we've been hearing, all you have to do is download current
Postgres (snapshot tarball or CVS pull) and try "configure" a few times
(with "make distclean" to clean up). That's perhaps not minimal but it
should at least convince him the bug exists ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-05-12 16:58:58 | Re: threads stuff/UnixWare |
Previous Message | Larry Rosenman | 2004-05-12 16:55:55 | Re: threads stuff/UnixWare |
From | Date | Subject | |
---|---|---|---|
Next Message | Laurent Ballester | 2004-05-12 17:02:39 | DLL for log event |
Previous Message | V i s h a l Kashyap @ [Sai Hertz And Control Systems] | 2004-05-12 16:21:09 | Re: Novice Guide to Windows Compile How to |
From | Date | Subject | |
---|---|---|---|
Next Message | pgsql | 2004-05-12 18:10:52 | Configuration patch |
Previous Message | Peter Eisentraut | 2004-05-12 15:01:33 | Re: mingw configure failure detection |