public inbox for [email protected]  

help / color / mirror / Atom feed

From: Pyry Kontio <[email protected]>
To: [email protected]
Subject: Re: Problems with statically linking libpq of Postgres 12.0 + musl
Date: Mon, 17 Feb 2020 14:31:42 +0900
Message-ID: <CACS8yHL0gbL3ECONrDygcBioTQBY=oVG-KGWB6+N7spG+eSMQw@mail.gmail.com> (raw)
In-Reply-To: <CACS8yHKjrFOoTKKFOOted4d+16oN438DE0ydtp9y5QrxvcGp2w@mail.gmail.com>
References: <CACS8yHKjrFOoTKKFOOted4d+16oN438DE0ydtp9y5QrxvcGp2w@mail.gmail.com>

After posting the last post, I got an helpful answer on the
#[email protected], so I'm sharing that here.

It seems that in 12.0 branch, the following change was made:
https://github.com/postgres/postgres/commit/ea53100d5

Some needed source files from libpgcommon and libpqport
used to be directly symlinked to libpq and ecpg sources.
This practice was eschewed to improve maintainability,
so linking libpgcommon and libpqport separatelybecame a necessity.

I was also pointed out that especially libpgcommon defines
some common names without the pg prefix, and if those collide
with names defined elsewhere, funny things will happen.

Nevertheless, the way to link libpq statically from
Postgres 12.0 and on is to include libpgcommon and libpqport.

Thanks for the help to all!
Pyry Kontio

view thread (2+ messages)

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Problems with statically linking libpq of Postgres 12.0 + musl
  In-Reply-To: <CACS8yHL0gbL3ECONrDygcBioTQBY=oVG-KGWB6+N7spG+eSMQw@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox