On Wed, Dec 08, 1999 at 08:20:58AM +0000, Christos Zoulas wrote:
> In article <19991207041511.A33473@greycat.com>,
> Dann Lunsford <dann@greycat.com> wrote:
> >On Mon, Dec 06, 1999 at 08:20:21PM +0000, Christos Zoulas wrote:
> >> In article <19991206112848.A31108@greycat.com>,
> >> Dann Lunsford <dann@greycat.com> wrote:
> >> 
> >> >Hmmm.   Didn't the rest of my message get through?  This was just the first
> >> >three lines of the log extract.  I appreciate the pointer, and I *have* 
> >> >subscribed, but that was a very small part of my original problem.  As
> >> >far as I can tell, after wasting another two days, the above has nothing 
> >> >at all to do with dig failing to link.  That appears to be caused by
> >> >the bind library not compiling the MD5_* routines.  What I want to know is,
> >> >how to get those routines into libbind?  Nothing I've tried has worked.
> >> 
> >> I don't recall. I just saw the top part of the error I think. Can you
> >> forward the rest of it again please?
> >> 
> >> christos
> >
> >OK.  Here it is, everything from the start of building bind to the end.
> >Thanks for the help; this is driving me nuts (it's not a long drive, 
> >I live pretty near there...)
> 
> The MD5 stuff should be in libc... Do nm /usr/lib/libc.a | grep MD5. If it
> is not, then try to find out why your libc is missing them.

That's what I thought, also; take a closer look.  The routines that are missing
are MD5_*, the libc routines are MD5*.  That "_" indicates the routines in 
bind/lib/dst, not the ones in libc.  They are supposed to be included if you set
CRYPTFLAGS=-DHMAC (see the README in the dst directory), but apparently, 
they aren't.  I must be missing something that's hugely obvious to everyone else.
Just wish I could figure out what!  

Thanks for the help.  Really appreciate it.

-- 
Dann Lunsford       The only thing necessary for the triumph of evil
dann@greycat.com    is that men of good will do nothing.  --  Cicero