| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: mingw configure failure workaround |
| Date: | 2004-05-01 20:42:20 |
| Message-ID: | 16068.1083444140@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-hackers-win32 pgsql-patches |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> And if not 3), is there some autoconf wizard out there who can help do
> this properly? It would probably take me many hours to work out, as I
> have never touched the beast.
Obviously, or you would know that configure is a generated file that
there is no point in editing by hand.
The real issue in my mind is why is "ln" unreliable in mingw? I cannot
see any point in a retry kluge when we do not know what's really going
on.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2004-05-01 21:00:32 | Re: mingw configure failure workaround |
| Previous Message | Tom Lane | 2004-05-01 20:35:30 | Re: FW: Timezone library |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2004-05-01 21:00:32 | Re: mingw configure failure workaround |
| Previous Message | Andrew Dunstan | 2004-05-01 15:16:57 | mingw configure failure workaround |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2004-05-01 21:00:32 | Re: mingw configure failure workaround |
| Previous Message | Tom Lane | 2004-05-01 20:35:30 | Re: FW: Timezone library |