PostgreSQL always uses own versions of *printf(), but does not export them - Mailing list pgsql-bugs

From Patrik Novotny
Subject PostgreSQL always uses own versions of *printf(), but does not export them
Date
Msg-id CAE_EZkhy0Sxm8Bnx3q4tBQakN4y--CQ-vDM24VNXXN83kVHgyA@mail.gmail.com
Whole thread Raw
Responses Re: PostgreSQL always uses own versions of *printf(), but does not export them
List pgsql-bugs
Hi,

we came across an issue when compiling projects against PostgreSQL
version >=12, as the *printf symbols seems not to be properly
exported.

Build log example:
/builddir/build/BUILDROOT/gambas3-3.14.3-3.fc33.x86_64/usr/bin/gbi3:
symbol lookup error:
/builddir/build/BUILDROOT/gambas3-3.14.3-3.fc33.x86_64/usr/lib64/gambas3/gb.db.postgresql.so:
undefined symbol: pg_fprintf

Are we missing some steps required for building against PostgreSQL
version >=12, or is this an unexpected error?

Also, the issue seems to be related to this commit[1], and more
details can be found in the original Fedora bug report[2].

[1] https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=96bf88d52711ad3a0a4cc2d1d9cb0e2acab85e63
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1849884


Thanks! Regards

Patrik Novotný
Associate Software Engineer
Red Hat
panovotn@redhat.com




pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #16507: RTRIM function doesnt behave as expected for certain scenario
Next
From: Tom Lane
Date:
Subject: Re: PostgreSQL always uses own versions of *printf(), but does not export them