On Wed, 22 Nov 2000, Todd Vierling wrote:

> On Wed, 22 Nov 2000, Frederick Bruckman wrote:
> 
> : > MKCRYPTO=no
> : > 
> : > in /etc/mk.conf  by any chance?
> : 
> : Shouldn't matter; the command line setting overrides the setting in
> : /etc/mk.conf or $MAKECONF.
> 
> Not if the line reads MKCRYPTO=no instead of MKCRYPTO?=no.  The difference
> is very important to bsd.pkg.mk, which does recursion and does not pass down
> "overrides".

For settings in the environment, yes. But do you have an explanation
for the following? It looks as if setting a variable on the command
line (and /etc/mk.conf simultaneously) produces undefined behavior...


root@handy-> head -2 /etc/mk.conf
MKCRYPTO=               no
FOO=                    bar
root@handy-> FOO=BAR make -V FOO
bar
root@handy-> make FOO=BAR -V FOO
bar
root@handy-> make show-var VARNAME=FOO FOO=BAR
BAR
root@handy-> make MKCRYPTO=yes
===> vnc-3.3.3.1 may not be built, because it utilizes strong cryptography
=> Checksum OK for vnc-3.3.3r1_unixsrc.tgz.
=> Checksum mismatch for vnc-latest_doc.tgz.
Make sure the Makefile and md5 file (/s/pkgsrc/net/vnc/files/md5)
are up to date.  If you want to override this check, type
"make NO_CHECKSUM=yes [other args]".
*** Error code 1

Stop.
root@handy-> MKCRYPTO=yes make
===> vnc-3.3.3.1 may not be built, because it utilizes strong cryptography
root@handy-> 


Frederick