Dave Cramer <pg@fastcrypt.com> writes:
> It appears to be getting the wrong address for tsearch()
I applied a patch for that earlier today. It seems that in OS X 10.4
the compiler generates a function with the same name as the shared
library, ie tsearch() for libtsearch ... and it doesn't tell you about
the name conflict, it just lets the wrong function get called at
runtime. Earlier OS X versions did not do this, and I have to say that
it's one of the most brain-dead usurpations of application namespace
I've seen in a long time. But there you have it.
regards, tom lane
