On Tue Dec 28 1999 at 22:18:55 -0200, Paulo A. P. Pires wrote:

> I have some doubts related to building crypto-enabled binaries
> out of crypto-intl sources (tracked with cvs).  Apparently,
> libraries build and install just fine, and I was told that IPsec
> support in kernel builds are also OK.
> 
> What happened, however, to userland programs like bdes and all
> kerberos-related stuff (I know kerberos is US-only, but there is
> a replacement for it somewhere, isn't there?)?  Also, if I do
> 
>     make -DDOMESTIC DOMESTIC=crypto-intl build
> 
> the process fails since there no Makefile in /usr/src/crypto-intl
> (yet since there is not what to build in usr.bin, perhaps it
> should not be there anyway).
> 
> I may sound stupid, but I do not understand how crypto support
> is now.  I'd appreciate some directions to get a picture of how
> it is organized and, hopefully, get the full of it in my system.

Well I don't claim to understand it either, but I took a shot at
building it last weekend and it went just great. (don't know if it's any
use though ;). Reading eg. usr.bin/Makefile:

.if defined(CRYPTOPATH)
.sinclude "${CRYPTOPATH}/usr.bin/Makefile.frag"
.endif

and from bsd.crypto.mk:

.if !defined(CRYPTOBASE)
.if exists(${SRCTOP}/crypto-us)
CRYPTOBASE=crypto-us
.elif exists(${SRCTOP}/crypto-intl)
CRYPTOBASE=crypto-intl
.else
.undef CRYPTOBASE
.endif # exists
.endif # CRYPTOBASE

So having the directory & files around apparently makes it work.

-- 
  "Never underestimate the power of the Lite side of the \Source/"
 Antti Kantee   /       NetBSD        \  1973 <- draken   \    / o
<pooka@iki.fi> / http://www.netbsd.org \  platters -> 1999 \  /  |
______________/ Free Multiplatform UN*X \___________________\/__ |