From owner-freebsd-doc@FreeBSD.ORG Mon Nov 17 21:07:25 2014 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0590E35D for ; Mon, 17 Nov 2014 21:07:25 +0000 (UTC) Received: from host203.r-bonomi.com (host203.r-bonomi.com [204.87.227.203]) by mx1.freebsd.org (Postfix) with ESMTP id D110E6B0 for ; Mon, 17 Nov 2014 21:07:24 +0000 (UTC) Received: (from root@localhost) by host203.r-bonomi.com (8.14.9/8.14.7) id sAHKuBiZ015566; Mon, 17 Nov 2014 14:56:11 -0600 (CST) (envelope-from bonomi) Date: Mon, 17 Nov 2014 14:56:11 -0600 (CST) From: Robert Bonomi Message-Id: <201411172056.sAHKuBiZ015566@host203.r-bonomi.com> To: freebsd-doc@FreeBSD.org Subject: errata for FreeBSD Handbook, Section 14.6 OpenSSL X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Nov 2014 21:07:25 -0000 Current text reads: FreeBSD provides two versions of OpenSSL: one in the base system and one in the Ports Collection. Users can choose which version to use by default for other ports using the following knobs: WITH_OPENSSL_PORT: when set, the port will use OpenSSL from the security/openssl port, even if the version in the base system is up to date or newer. WITH_OPENSSL_BASE: when set, the port will compile against OpenSSL provided by the base system. The meaning of 'knobs' is _not_ clear -- if one reads this section alone. A simple edit, changing both occurances of 'when set, the port will' to 'when this environment variable is set, any port build will' makes it absolutely clear (on a stand-alone basis) what the 'knob' is, and what it affects. I had a GAWDAFUL time trying to build 'mplayer', in *small* part because of this (nghttp2 build abords 'OpenSSL 1.0.1+ required, even when OpenSSL 1.0.1j' is installed -- apparently it finds the base version _first_, and doesn't check for the ports version. it should be smart enough to check for both, if the first check comes up 'not recent enough', and if either library _is_ 'new enough' use that one, possibly requesting confirmation if more than one version is found. *snarl* ), and in large part because there are _circular_ dependencies among some of the 'mplayer' dependencies mplayer cmake curl nghttp2 llvm35 {and one more whose name escapes me} I appear to have gotten things beaten into submission, by installing 'packages' for curl, cmake and nghttp2 and _then_ trying the port build, but it *HAS* been a major (as in most of a _week_) battle.