https://bugzilla.novell.com/show_bug.cgi?id=361431 User max@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=361431#c15 Reinhard Max <max@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |INVALID --- Comment #15 from Reinhard Max <max@novell.com> 2008-06-16 04:18:07 MDT --- (In reply to comment #14 from Peter Poeml)
So you basically say, that every software which tries to use pg_config --libs is broken, and they should not use pg_config at all?
Using pg_config e.g. to query PostgreSQL's installation paths is fine, but using pg_config --libs and expecting it to tell you what linker flags to use for linking client applications against the PostgreSQL client library is not.
We are a distributor, we should cater for that.
The only senseful way I see to cater for that is to remove the usage of "pg_config --libs" from the other packages and send patches to the respective upstreams.
The fact that other projects *do* use pg_config indicates that this works somehow, just not in our evironment.
The fact that it works somehow somewhere doesn't mean it is correct.
Could you not just ditch that stuff from pg_config?
Why do people insist on abusing "pg_config --libs" for things it wasn't made for and demand it be fixed although it is not broken, if all they would really need to pull libpq in is "AC_CHECK_LIB([pq], [PQconnectdb])" ? -- 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.