Re: pg_crypto failures with llvm on OSX

Robert Creager <robert(at)logicalchaos(dot)org> writes:
> On Mar 10, 2012, at 4:19 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>> On 03/09/2012 07:50 PM, Tom Lane wrote:
>>> I suspect that mussel has an ABI-incompatible openssl library hanging
>>> around someplace. On my machine "otool -L pgcrypto.so" shows
>>> /usr/lib/libcrypto.0.9.8.dylib (compatibility version 0.9.8, current version 44.0.0)
>>> It'd be interesting to know what it says on mussel.

> creagers-imac:pgcrypto Robert$ otool -L pgcrypto.so
> pgcrypto.so:
> /opt/local/lib/libcrypto.1.0.0.dylib (compatibility version 1.0.0, current version 1.0.0)
> /opt/local/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.5)
> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 159.1.0)

Uh-huh. I will bet a good deal that you are compiling against the
Apple-supplied openssl header files, but then linking against the
MacPorts openssl shlib, which evidently is configured a bit differently
than Apple's copy.

[ pokes around in the mussel build logs ] I see "-L/opt/local/lib"
in the link commands, which explains why you're linking to that shlib,
and I don't see anything like "-I/opt/local/include", which is probably
needed to find the matching header files. There is a
"-I/opt/local/include/libxml2", but that isn't going to help unless your
/opt/local layout is really weird.

What's really odd though is that there is nothing in the configuration
script that injects any of those switches. I think you've got some
screwy global configuration on that machine, which you'd be well advised
to try to get rid of --- it's tough for people to do remote diagnosis of
buildfarm critters when there's relevant configuration that's not
exposed in the config script.

regards, tom lane