Tom Lane wrote:
>"Rocco Altier" <RoccoA@Routescape.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.
cheers
andrew