Re: mingw configure failure workaround

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-03 18:02:47
Message-ID: 200405032002.47400.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:
> However, the problem is that the first line will actually appear to
> have succeeded, i.e. MSys's ln is lying to us ;-(

Then msys needs to be fixed. There is certainly a bunch of
autoconfiscated software that gets compiled on mingw/msys every day. I
would like to know why we are the only ones having this problem. Has
anyone contacted the msys authors about this?

> This comes from the autoconf macro _AC_OUTPUT_LINKS defined in its
> status.m4, which I guess is what we'd need to override (is that
> possible?)

No

> if we are going to detect the failure, or maybe there's
> some more magical way that in my unfamiliarity with autoconf I am
> unaware of.

No

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2004-05-03 19:18:37 Re: Weird prepared stmt behavior
Previous Message James Robinson 2004-05-03 17:57:18 Re: Weird prepared stmt behavior

Browse pgsql-hackers-win32 by date

  From Date Subject
Next Message Tom Lane 2004-05-03 19:34:41 Re: Fixed directory locations in installs
Previous Message Peter Eisentraut 2004-05-03 17:43:47 Re: Fixed directory locations in installs

Browse pgsql-patches by date

  From Date Subject
Next Message Magnus Hagander 2004-05-03 18:59:37 Run-as-admin warning for win32
Previous Message Peter Eisentraut 2004-05-03 17:43:47 Re: Fixed directory locations in installs