From owner-freebsd-ports@FreeBSD.ORG Fri Mar 20 23:27:35 2015 Return-Path: Delivered-To: freebsd-ports@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 ACBBDA8D for ; Fri, 20 Mar 2015 23:27:35 +0000 (UTC) Received: from luigi.brtsvcs.net (luigi.brtsvcs.net [204.109.60.246]) (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 84C28C94 for ; Fri, 20 Mar 2015 23:27:35 +0000 (UTC) Received: from chombo.houseloki.net (c-71-59-211-166.hsd1.or.comcast.net [71.59.211.166]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by luigi.brtsvcs.net (Postfix) with ESMTPSA id CCD572D4F8D; Fri, 20 Mar 2015 23:27:33 +0000 (UTC) Received: from [IPv6:2601:7:2580:181:baca:3aff:fe83:bd29] (unknown [IPv6:2601:7:2580:181:baca:3aff:fe83:bd29]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by chombo.houseloki.net (Postfix) with ESMTPSA id 838FC8D7; Fri, 20 Mar 2015 16:27:31 -0700 (PDT) Message-ID: <550CACD8.5010604@bluerosetech.com> Date: Fri, 20 Mar 2015 16:27:20 -0700 From: list_freebsd@bluerosetech.com User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Naram Qashat Subject: Re: Is it possibly to detect which OpenSSL is used for a port? References: <1b89602a13f212214de4f70feaf3f11e.squirrel@www.cyberbotx.com> <550C7BD1.30005@bluerosetech.com> <600c966bf3ee8136f77b03fb39abcc95.squirrel@www.cyberbotx.com> In-Reply-To: <600c966bf3ee8136f77b03fb39abcc95.squirrel@www.cyberbotx.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Mar 2015 23:27:35 -0000 On 2015-03-20 14:49, Naram Qashat wrote: > I've looked at bsd.openssl.mk and from what it says, those WITH_OPENSSL_* > knobs are use-set, not port-set. So that doesn't help me. I'm not sure what you read, but lines 5 through 10 of ports/Mk/bsd.openssl.mk are: # Use of 'USE_OPENSSL=yes' includes this Makefile after bsd.ports.pre.mk # # the user/port can now set this options in the makefiles. # # WITH_OPENSSL_BASE=yes - Use the version in the base system. # WITH_OPENSSL_PORT=yes - Use the OpenSSL port, even if base is up to date I can confirm that setting or testing those variables is how you modify the OpenSSL linking behaviour of a port. There's currently 51 ports that do so. Off hand, an example is www/nginx-devel. It can't use OpenSSL 0.9.8 if you enable SPDY, so it sets WITH_OPENSSL_PORT=yes if OSVERSION < 1000028. >> On 2015-03-20 11:02, Naram Qashat wrote: >>> This isn't quite what I'm looking for. I want to be able to tell within >>> a >>> port's Makefile if the user wanted the base or ports OpenSSL to be used. >>> I've been trying to port TDE to FreeBSD, and tdelibs uses pkg-config to >>> check for OpenSSL. This would work if the only form of OpenSSL was in >>> ports, but the base OpenSSL doesn't have a pkg-config file to use, so I >>> need to know which is going to be used so I can determine when this >>> pkg-config check can be removed. >> >> `grep WITH_OPENSSL_ Makefile` >> >> If the port expresses an opinion about which OpenSSL to use, it has to >> use WITH_OPENSSL_PORT or WITH_OPENSSL_BASE. >> >> -- >> This message has been scanned for viruses and >> dangerous content by MailScanner, and is >> believed to be clean. >> >> > > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" >