On Sun, May 27, 2012 at 11:06 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> julia.jacobson@arcor.de writes:
>> Moreover, all required dependencies of the library are present on the machine:
>> MacMini:~ user$ otool -L /Library/PostgreSQL/psqlODBC/lib/psqlodbcw.so
>> /Library/PostgreSQL/psqlODBC/lib/psqlodbcw.so:
>> /usr/lib/libltdl.3.dylib (compatibility version 5.0.0, current version 5.4.0)
>> /usr/lib/libssl.0.9.7.dylib (compatibility version 0.9.7, current version 0.9.7)
>> @loader_path/libpq.5.dylib (compatibility version 5.0.0, current version 5.4.0)
>> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 111.1.4)
>> /usr/lib/libiodbc.2.dylib (compatibility version 4.0.0, current version 4.17.0)
>> /usr/lib/libiodbcinst.2.dylib (compatibility version 4.0.0, current version 4.17.0)
>> /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0)
>
> Hm, what's that "@loader_path" business? I don't know much about
> dynamic linking on OS X, but if that works at all, it must be some sort
> of environment reference, which would be pretty fragile. I'd suggest
> asking EnterpriseDB whether that's meant to be like that or is a
> packaging bug.
It is meant to be like that - it expands to the directory containing
the psqlodbcw.so file (@loader_path is useful when creating
relocatable frameworks). We ship the required libpq in the psqlODBC
installer, so it should always be available in that path.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
