Re: Problems with statically linking libpq of Postgres 12.0 + musl

After posting the last post, I got an helpful answer on the
#postgres(at)freenode(dot)net, 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