lib/52187: New libarchive-3-3-2pre won't build with MKCRYPTO=no

[paul%whooppee.com@localhost]

>Number:         52187
>Category:       lib
>Synopsis:       New libarchive-3-3-2pre won't build with MKCRYPTO=no
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    lib-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Apr 22 07:50:00 +0000 2017
>Originator:     Paul Goyette
>Release:        NetBSD 7.99.66
>Organization:
+------------------+--------------------------+----------------------------+
| Paul Goyette     | PGP Key fingerprint:     | E-mail addresses:          |
| (Retired)        | FA29 0E3B 35AF E8AE 6651 | paul at whooppee dot com   |
| Kernel Developer | 0786 F758 55DE 53BA 7731 | pgoyette at netbsd dot org |
+------------------+--------------------------+----------------------------+
>Environment:
	
	
System: NetBSD speedy.whooppee.com 7.99.66 NetBSD 7.99.66 (SPEEDY 2017-03-24 21:50:36 UTC) #0: Fri Mar 24 22:50:09 UTC 2017 paul%speedy.whooppee.com@localhost:/build/netbsd-local/obj/amd64/sys/arch/amd64/compile/SPEEDY amd64
Architecture: x86_64
Machine: amd64
>Description:
	
With the recent importation of libarchive-3-3-2pre (see [1] and [2]), it
is no longer possible to successfully build a release with MKCRYPTO=no.
Among other things, archive_cryptor.c references openssl/evp.h which does
not get installed for MKCRYPTO=no


[1] http://mail-index.netbsd.org/source-changes/2017/04/20/msg083802.html
[2] http://mail-index.netbsd.org/source-changes/2017/04/20/msg083806.html
>How-To-Repeat:
Invoke build.sh in a manner similar to:

	./build.sh -T /build/netbsd-local/tools/x86_64/amd64 \
		-D /build/netbsd-local/dest/amd64 \
		-O /build/netbsd-local/obj/amd64 \
		-R /build/netbsd-local/release \
		-V RELEASEMACHINEDIR=amd64 \
		-V MKKDEBUG=yes \
		-V MKCRYPTO=no \
		-U -u -x -m amd64 -j1 release
	
>Fix:
	
Either 
   * modify libarchive to have an "export" variant that doesn't require
     use of any other code that gets removed via MKCRYPTO=no, or
   * deprecate/de-support the MKCRYPTO option

Maintaining a working build with MKCRYPTO=no is quite painful, and is
likely no longer worth the effort, since US export restrictions on the
crypto code were significantly eased (and mostly removed) many years
ago.  We probably should deprecate MKCRYPTO and always build the crypto
code.

>Unformatted: