https://bugzilla.novell.com/show_bug.cgi?id=361431
User max@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=361431#c18
Reinhard Max
It worked up to 10.3 -- in 11.0 is broken.
It was wrong in 10.3 and before already, just "happened to work".
11.0 is more "correct"?
Yes, because it prevents incorrect usage of "pg_config --libs".
What about libpgport -- why was it removed in 11.0? In 10.3 it's there.
Because it is a) not needed and b) I removed all static libs from the postgresql packages for 11.0.
Wny does pg_config report it in --libs anyway?
Because it is linked in to the postgresql backend.
Is that not a bug?
No, because (I am repeating myself) "pg_config --libs" is not intended to be used by client programs for linking against libpq.
What should other projects to do, if they write autoconf macros that compile little test programs for checking stuff?
They can do whatever they want as long as they don't mistakenly use "pg_config --libs" for unintended purposes. What's wrong with using "AC_CHECK_LIB([pq], [PQconnectdb])" in autoconf as I suggested above?
The building of those little test programs fails because they use pg_config --libs to build them, which seems to be the logical thing to do, or not?
No, because (again) "pg_config --libs" only tells you how the backend executable was linked together, not more and not less.
I suppose projects _need_ to use pg_config --libs to compile such test programs, because the libs will be needed in cases of static linkage.
We don't ship a static version of libpq, so static linkage is not a problem we need to cater for. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.