how was bind compiled/configured?

[Stefan Puiu]

I guess using 'ldd -v' on the old named binary could help, too. If
libcrypto shows up in the library dependencies, then openssl support
was enabled (--with-openssl=...) (most likely); if libpthread is
linked in, then that is most likely an indication that
--enable-threads was used. If libisc, libisccc and friends (the BIND 9
libraries) also show up, it means that the binary was dynamically
linked against those (by default it uses static linking). I don't know
if there's anything else you might need to care about.

The --enable-threads option seems to be a good idea on some platforms,
but not others (you haven't mentioned your platform). openssl is used
for DNSSEC, and I don't remember if it's required for anything else
(TSIG maybe?).

Hope this helps,
Stefan.

On 3/27/06, Pamela Rock <prock111 at yahoo.com> wrote:
> Anyone?  Is my request below doable?  Is there a way
> to tell what options where passed to "configure"
> during the build phase?
>
> Thanks.
>
> --- Pamela Rock <prock111 at yahoo.com> wrote:
>
> > Is there a way to tell what options (if any) were
> > passed to bind (9.2.2) in the **configure** process.
> >
> > I need to upgrade an instance of bind and I don't
> > know
> > how it was originally built.  Obviously the person
> > who
> > built the instance is no longer on board.
> >
> > Thank you,
> >
> > Pamela Rock
> >
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Tired of spam?  Yahoo! Mail has the best spam
> > protection around
> > http://mail.yahoo.com
> >
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
>
>