Bug#481577: libpq-dev: pg_config lists too much

2008-05-20 Thread Tollef Fog Heen
* Peter Eisentraut | Tollef Fog Heen wrote: | | There's currently a discussion on | [EMAIL PROTECTED] about how to link in libpq correctly and | people are proposing to use the output of pg_config --libs. | | The correct way is to use pg_config --libdir to find out the correct | directory

Bug#481577: libpq-dev: pg_config lists too much

2008-05-18 Thread Tollef Fog Heen
* Peter Eisentraut | Tollef Fog Heen wrote: | it seems like pg_config outputs quite a lot of libraries that should | just be pulled in through libpgport being linked with them rather than | linking all libs using postgres to them: | | From the man page: | |--libs Print the value of

Bug#481577: libpq-dev: pg_config lists too much

2008-05-18 Thread Peter Eisentraut
Tollef Fog Heen wrote: What is the use for --libs, then? Probably none, except debugging by upstream developers. I admit I have heard of more people than just you who are confused by this. We may need to clarify this somehow. There's currently a discussion on [EMAIL PROTECTED] about how

Bug#481577: libpq-dev: pg_config lists too much

2008-05-17 Thread Tollef Fog Heen
Package: libpq-dev Version: 8.3.1-2+b1 Hi, it seems like pg_config outputs quite a lot of libraries that should just be pulled in through libpgport being linked with them rather than linking all libs using postgres to them: $ pg_config --libs -lpgport -lxslt -lxml2 -lpam -lssl -lcrypto -lkrb5

Bug#481577: libpq-dev: pg_config lists too much

2008-05-17 Thread Peter Eisentraut
Tollef Fog Heen wrote: it seems like pg_config outputs quite a lot of libraries that should just be pulled in through libpgport being linked with them rather than linking all libs using postgres to them: From the man page: --libs Print the value of the LIBS variable that was used