From owner-freebsd-ports@freebsd.org Mon Jul 18 23:32:34 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 694B1B9DE49 for ; Mon, 18 Jul 2016 23:32:34 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from mail.infocus-llc.com (mail.infocus-llc.com [199.15.120.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 45A1F1633 for ; Mon, 18 Jul 2016 23:32:34 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (c-75-65-60-66.hsd1.ms.comcast.net [75.65.60.66]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.tarragon.infocus-llc.com (Postfix) with ESMTPSA id 3rtfbj0m3bzph; Mon, 18 Jul 2016 18:32:33 -0500 (CDT) Received: by draco.over-yonder.net (Postfix, from userid 100) id 3rtfbh2c2sz2xb; Mon, 18 Jul 2016 18:32:32 -0500 (CDT) Date: Mon, 18 Jul 2016 18:32:32 -0500 From: "Matthew D. Fuller" To: Euan Thoms Cc: Jim Ohlstein , Kevin Oberman , FreeBSD Ports Mailing List Subject: Re: curl and nginx no longer build on same host Message-ID: <20160718233232.GU31921@over-yonder.net> References: <8FD19636-C34F-4609-BA5D-C6DBC32E7BA1@ohlste.in> <7c8a-578d5c00-1f-6b8b4580@51771804> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7c8a-578d5c00-1f-6b8b4580@51771804> X-Editor: vi X-OS: FreeBSD X-Virus-Scanned: clamav-milter 0.99 at mail.tarragon.infocus-llc.com X-Virus-Status: Clean User-Agent: Mutt/1.6.1-fullermd.4 (2016-04-27) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jul 2016 23:32:34 -0000 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.