Re: Cygwin linking rules

From: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>
To: Marco Atzeri <marco(dot)atzeri(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Cygwin linking rules
Date: 2018-09-30 14:13:19
Message-ID: fda91d8a-93ae-d7a5-a555-4a88d5783f36@2ndQuadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 09/29/2018 02:13 PM, Marco Atzeri wrote:
>
> building from git and using the attached patch that is used for all
> cygwin packages on latest cygwin
>
> $ uname -svrm
> CYGWIN_NT-10.0 2.11.1(0.329/5/3) 2018-09-05 10:24 x86_64
>
> I do not see the problem
>
> ============== creating database "contrib_regression" ==============
> CREATE DATABASE
> ALTER DATABASE
> ============== running regression test queries ==============
> test paths                        ... ok
> test dblink                       ... ok
> ============== shutting down postmaster ==============
>
>
>  $ objdump -x usr/lib/postgresql/dblink.dll |grep "DLL Name:"
>         DLL Name: postgres.exe
>         DLL Name: cygpq-5.dll
>         DLL Name: cygwin1.dll
>         DLL Name: KERNEL32.dll
>

Yes. So there are a couple of things here. First, the dll has
SO_MAJORVERSION in the name. And second it stops building any static
libraries and instead builds windows import libraries with names like
lippq.a.

I've tested this on both HEAD and REL9_3_STABLE and it works fine.

I think we should apply this to HEAD. If it's not too late it would
probably be a good thing for release 11 - would need a release note.

cheers

andrew

--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2018-09-30 17:18:14 Re: executor relation handling
Previous Message Michael Paquier 2018-09-30 13:51:44 Re: [HACKERS] Optional message to user when terminating/cancelling backend