Re: Determining client_encoding from client locale

On Thursday 23 July 2009 20:16:39 Jaime Casanova wrote:
> On Thu, Jul 23, 2009 at 11:02 AM, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > On most Linux systems, -L doesn't have any effect on what happens at
> > runtime --- the dynamic linker's search path will determine that.
> > Try "ldd" on the executable to see which shlibs really get picked up.
>
> yeah! it's using the one that ships with 8.4.0
>
> postgres(at)casanova1:~/pg_releases/pgtests$ ldd test-libpq
> [...other no related libraries...]
> libpq.so.5 => /opt/PostgreSQL/8.4/lib/libpq.so.5 (0x00007f7ef6db2000)
>
> The only way i can compile with the patched version of libpq is with this
> gcc -o test-libpq test-libpq.o -L../pgsql/src/port -lpgport
> -L../pgsql/src/interfaces/libpq -lpq -L../pgsql/src/port
> -Wl,--as-needed -Wl,-rpath,'/usr/local/pgsql/head/lib' -lpgport
>
> BTW, i can compile with the unpatched version if i add -lpgport (seems
> like this patch is adding a dependency)
> gcc -o test-libpq test-libpq.o -L/usr/local/pgsql/head/lib -lpq -lpgport

Which proves my point, because libpgport includes chkconfig.c. But this is
just a workaround.