Date: Mon, 18 Jul 2016 18:32:32 -0500 From: "Matthew D. Fuller" <fullermd@over-yonder.net> To: Euan Thoms <euan@potensol.com> Cc: Jim Ohlstein <jim@ohlste.in>, Kevin Oberman <rkoberman@gmail.com>, FreeBSD Ports Mailing List <freebsd-ports@freebsd.org> Subject: Re: curl and nginx no longer build on same host Message-ID: <20160718233232.GU31921@over-yonder.net> In-Reply-To: <7c8a-578d5c00-1f-6b8b4580@51771804> References: <8FD19636-C34F-4609-BA5D-C6DBC32E7BA1@ohlste.in> <7c8a-578d5c00-1f-6b8b4580@51771804>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jul 19, 2016 at 06:44:49AM +0800 I heard the voice of Euan Thoms, and lo! it spake thus: > > Aha, I got ftp/curl to build using WITH_OPENSSL_PORT=yes. Don't know > why I didn't try it before, perhaps since it is deprecated. > > So, I think we need to address some shortcoming in the new macro > DEFAULT_VERSIONS+=ssl=openssl. That seems... odd. > DEFAULT_VERSIONS+=ssl=openssl will cause bsd.default-versions.mk to set the variable SSL_DEFAULT to the value 'openssl'. Contrarily, > WITH_OPENSSL_PORT=yes will cause bsd.default-versions.mk to set the variable SSL_DEFAULT to the value 'openssl' (unless you've got OPENSSL_PORT defined, in which case it's set to whatever that is) and spit out a warning. So, unless you're setting OPENSSL_PORT, they're doing exactly the same thing (modulo the warning). If you are (e.g., from using libressl instead), you need to set THAT instead of 'openssl' in the DEFAULT_VERSIONS line. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160718233232.GU31921>