From: Tom Lane <tgl@sss.pgh.pa.us>
To: Scott Ribe <scott_ribe@elevated-dev.com>
cc: Postgres Maillist <pgsql-admin@postgresql.org>
Subject: Re: unix socket location confusion
In-reply-to: <3184.1427063304@sss.pgh.pa.us>
References: <0A21BC93-7B9C-476E-AAF4-0FF71708E87F@elevated-dev.com>
 <3184.1427063304@sss.pgh.pa.us>
Comments: In-reply-to Tom Lane <tgl@sss.pgh.pa.us>
 message dated "Sun, 22 Mar 2015 18:28:24 -0400"
Date: Sun, 22 Mar 2015 18:43:10 -0400
Message-ID: <3533.1427064190@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

I wrote:
> Evidently your psql is linking to this libpq and not the one you built.
> You can fix that with suitable use of rpath; although I'm not sure why
> an out-of-the-box build doesn't do that for you.  It works fine for
> me:

> $ otool -L ~/testversion/bin/psql
> /Users/tgl/testversion/bin/psql:
>         /Users/tgl/testversion/lib/libpq.5.dylib (compatibility version 5.0.0, current version 5.8.0)
>         /usr/lib/libedit.3.dylib (compatibility version 2.0.0, current version 3.0.0)
>         /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1213.0.0)

> and I don't believe I'm using any nondefault switches to get that.

I poked around a bit more and remembered what it is that makes it work:
you need an -install_name switch when building libpq.dylib (and then the
link of psql has to be sure to reference that .dylib file).  For example
I see this as part of the libpq link step:

	-install_name '/Users/tgl/testversion/lib/libpq.5.dylib'

after having configured with "--prefix=/Users/tgl/testversion".

So this works only if your libpq.dylib is actually installed at the
location that was expected when you built it.  The recipe you gave
looks like it should have done that, but I'm suspicious that the
answer is somewhere near here.

			regards, tom lane


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin