From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: mingw configure failure workaround |
Date: | 2004-05-02 07:44:25 |
Message-ID: | 200405020944.25239.peter_e@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-hackers-win32 pgsql-patches |
Andrew Dunstan wrote:
> Even if we don't do that can we *please* put in something that
> detects the error, and tells the user what they will have to do to
> fix it? Failing in a situation which we know we can detect and not
> telling the user is intolerable, IMNSHO.
Can you try a more recent version of autoconf and see if that behaves
more tolerably?
From | Date | Subject | |
---|---|---|---|
Next Message | Fabien COELHO | 2004-05-02 09:12:44 | Re: pg ANY/SOME ambiguity wrt sql standard? |
Previous Message | Christopher Kings-Lynne | 2004-05-02 05:11:15 | Re: Plan for feature freeze? |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-05-02 11:11:49 | Timezone database questions |
Previous Message | Bruce Momjian | 2004-05-02 04:26:47 | Re: win32 build and test issues |
From | Date | Subject | |
---|---|---|---|
Next Message | Fabien COELHO | 2004-05-02 09:00:52 | Re: new aggregate functions v1 |
Previous Message | Bruce Momjian | 2004-05-02 04:27:43 | Re: mingw regression test fixes |