oh man, sorry about this.  I hadn't been following this thread.  I does
appear that I'm the guilty party for this.  Looks like in the cvs package
makefile, it says:

.if exists(/usr/lib/libkrb.a)
CONFIGURE_ARGS+=        --with-krb4=/usr --enable-encryption
.endif

and I do have the security set installed so when I built the package, it
linked against the kerberos library.  Hmm.  For now I'll remove the binary
package from ftp.netbsd.org.  This is most unfortunate that the package
will automatically pick up on kerberos but not give a warning.  

My apologies to all who wasted time on this.  Frederick, thanks for
bringing this to my attention.

-Dan

On Sun, 31 Oct 1999, Frederick Bruckman wrote:

> On Fri, 29 Oct 1999, David A. Gatwood wrote:
> 
> > On Fri, 29 Oct 1999, Henry B. Hotz wrote:
> > 
> > > >> 2. tar -xzf got me the cvs file, but didn't contain the necessary kerberos
> > > >>    libraries.
> > > 
> > > Is this an export issue?  Kerberos is distributed separately because it
> > > isn't exportable.
> > 
> > Yeah.  Which makes me wonder why the pre-built mac68k package was built
> > that way....
> 
> Dan?
> 
> > And how did someone build it when I can't find a secr
> > tarball for several releases back....  Or did they move to their own
> > directory hierarchy somewhere?  :-)
> 
> It's always been in a seperate directory, I think.
> 
> ftp.netbsd.org:///pub/NetBSD/NetBSD-1.4.1/mac68k/binary/security/secr.tgz
> 
> 
> 
>