Re: Fix pkg-config file for static linking

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Filip Gospodinov <f(at)gospodinov(dot)ch>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Fix pkg-config file for static linking
Date: 2021-09-06 08:30:06
Message-ID: 3d083444-0fc8-b873-ecf1-d90d72558b2e@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 05.09.21 21:57, Tom Lane wrote:
> Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> writes:
>> Makes sense. I think we could do it without hardcoding those library
>> names, as in the attached patch. But it comes out to the same result
>> AFAICT.
>
> This has been pushed, but the CF entry is still open, which is
> making the cfbot unhappy. Were you leaving it open pending
> pushing to back branches as well? I'm not sure what the point
> of waiting is --- the buildfarm isn't going to exercise the
> troublesome scenario.

I noticed another fix that was required and didn't get to it until now.
It's all done and backpatched now. CF entry is closed.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dilip Kumar 2021-09-06 08:59:38 Re: [Proposal] Fully WAL logged CREATE DATABASE - No Checkpoints
Previous Message houzj.fnst@fujitsu.com 2021-09-06 08:19:34 RE: [BUG] Unexpected action when publishing partition tables