Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
Subject: Re: unix socket location confusion
From: Scott Ribe <scott_ribe@elevated-dev.com>
In-Reply-To: <3533.1427064190@sss.pgh.pa.us>
Date: Sun, 22 Mar 2015 17:26:27 -0600
Cc: Postgres Maillist <pgsql-admin@postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <5600A100-C4A4-427D-938E-9FFDDBE87132@elevated-dev.com>
References: <0A21BC93-7B9C-476E-AAF4-0FF71708E87F@elevated-dev.com>
 <3184.1427063304@sss.pgh.pa.us> <3533.1427064190@sss.pgh.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

On Mar 22, 2015, at 4:43 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>=20
> 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.

Oh, take me out back and shoot me now ;-)

The one step I left out of my description of the process was the one immedi=
ately after make install where I decided I did not like the name of the fol=
der I had built into, and re-named it. I am surprised though, that with a f=
ull path to libpq, when that path does not exist, the loader searches and f=
inds a system lib instead of just failing.

It's questionable whether the PG executables should be built with full or r=
elative paths to the libs, both have their own disadvantages. But might be =
worth considering --relative-rpath someday? Or an option to link the fricki=
n' static libraries in and avoid the whole issue of mismatches.

--=20
Scott Ribe
scott_ribe@elevated-dev.com
http://www.elevated-dev.com/
https://www.linkedin.com/in/scottribe/
(303) 722-0567 voice


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