From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Rocco Altier <RoccoA(at)Routescape(dot)com> |
Subject: | Re: Cygwin - make check broken |
Date: | 2005-08-07 15:01:27 |
Message-ID: | 42F62247.8030609@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
er that would be this patch.
Andrew Dunstan wrote:
>
>
> Tom Lane wrote:
>
>> "Rocco Altier" <RoccoA(at)Routescape(dot)com> writes:
>>
>>
>>> It looks like when we changed regress/GNUmakefile to pull rules from
>>> Makefile.shlib, cygwin got broken in the process.
>>> ...
>>> I don't know enough about the rest of the way the cygwin port is put
>>> together, but it seems that the other platforms all have
>>> shlib=lib$(NAME)...
>>>
>>
>> Seems to me that defining shlib that way for Cygwin too would be a
>> reasonable answer, but I'm not sure if there will be any side-effects.
>> Can someone try it?
>>
>>
>>
>>
>
> The attached patch worked for me. The second part should not be
> applied - I simply include it to illustrate the hack (taken from a
> recent clue on the Cygwin mailing list) that I found necessary to get
> around brokenness on the latest release of Cygwin. The good news is
> that they do seem to be trying to find out what broke and fix it.
>
>
Attachment | Content-Type | Size |
---|---|---|
workdiff | text/plain | 1.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-08-07 16:02:24 | Re: Cygwin - make check broken |
Previous Message | Andrew Dunstan | 2005-08-07 13:52:00 | Re: Cygwin - make check broken |