how was bind compiled/configured?

[Stefan Puiu]

Yes, I think you can assume that. It would be pretty unusual to link
with libpthread without enabling thread support, I would say.

libnsl and libsocket have to be linked in when you're using socket
code on Solaris, they're pretty standard. libdl I think is related to
dynamic loading, also pretty standard.

You don't seem to have libcrypto in the list, and I don't think it's
possible to link statically against openssl, at least by looking at
the output of './configure --help'.

So, I think you can go with './configure --enable-threads
--with-openssl=no' (no openssl might be the default, though). You can
optionally specify a different prefix if you don't like /usr/local
(named would go in $prefix/sbin/named, dig/host/nslookup in
$prefix/bin).

On 3/28/06, Pamela Rock <prock111 at yahoo.com> wrote:
>
> XXXXXX snip snip XXXXXXXXXXXXXX

> The output of ldd is below.  By the way, this is bind
> 9.2.2 running on a Solaris 8 Sparc platform.  Based on
> your comments, is it safe to assume that bind was
> compiled with "--enable-threads"?  Any other hints or
> suggestions as to what was passed to configure durring
> the build phase would also be appreciated.