On Mar 22, 2015, at 4:43 PM, Tom Lane <tgl@xxxxxxxxxxxxx> wrote: > > 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 immediately after make install where I decided I did not like the name of the folder I had built into, and re-named it. I am surprised though, that with a full path to libpq, when that path does not exist, the loader searches and finds a system lib instead of just failing. It's questionable whether the PG executables should be built with full or relative paths to the libs, both have their own disadvantages. But might be worth considering --relative-rpath someday? Or an option to link the frickin' static libraries in and avoid the whole issue of mismatches. -- Scott Ribe scott_ribe@xxxxxxxxxxxxxxxx http://www.elevated-dev.com/ https://www.linkedin.com/in/scottribe/ (303) 722-0567 voice -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
