From owner-freebsd-ports@FreeBSD.ORG Fri Mar 7 02:05:19 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BB70B722; Fri, 7 Mar 2014 02:05:19 +0000 (UTC) Received: from yoshi.brtsvcs.net (yoshi.brtsvcs.net [IPv6:2607:f2f8:a450::66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A1C2CAD9; Fri, 7 Mar 2014 02:05:19 +0000 (UTC) Received: from poodle.laskoprinting.com (poodle.laskoprinting.com [173.11.14.36]) by yoshi.brtsvcs.net (Postfix) with ESMTPSA id 4F77CE604D; Thu, 6 Mar 2014 18:05:10 -0800 (PST) Received: from [192.168.5.11] (unknown [192.168.5.11]) by poodle.laskoprinting.com (Postfix) with ESMTPSA id C4D8474D1; Thu, 6 Mar 2014 18:05:08 -0800 (PST) Message-ID: <53192954.5070707@laskoprinting.com> Date: Thu, 06 Mar 2014 18:05:08 -0800 From: Darren Pilgrim Organization: Lasko Printing, Inc. User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: Mark Felder Subject: Re: ports/182985 maintainer timeout References: <53111711.1010907@laskoprinting.com> <5318DA3A.8090408@laskoprinting.com> <13A9A291-538E-4A62-B0B2-E6F43BEE7C5B@FreeBSD.org> In-Reply-To: <13A9A291-538E-4A62-B0B2-E6F43BEE7C5B@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org, portsmgr@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Mar 2014 02:05:19 -0000 On 3/6/2014 3:07 PM, Mark Felder wrote: > Hi Darren, > > I'm trying to understand exactly what we're looking at here. Is the > problem: > > "nginx always builds against OpenSSL in base (for FreeBSD 10+?)" ? > > If so, that's correct; it should not build against OpenSSL from ports > just because the version from ports happens to be installed. No, actually, that's exactly what it should do. If I install OpenSSL from ports and set WITH_OPENSSL_PORT in /etc/make.conf, the express intent is to require all OpenSSL-using ports to link to the ports version. Nginx with SPDY needs NPN, which means OpenSSL 1.0.1 or later. Thus for 9.x and earlier we need to set WITH_OPENSSL_PORT. For 10.0 and later, both versions will work, so the correct behaviour for nginx is to say it does not specifically require either by not setting either WITH_OPENSSL_* variable.