Date: Thu, 1 May 2014 07:33:58 -0700 From: Paul Hoffman <paul.hoffman@vpnc.org> To: Uwe Doering <gemini@geminix.org> Cc: freebsd-security@freebsd.org, "freebsd-ports@freebsd.org" <freebsd-ports@freebsd.org> Subject: Re: ports requiring OpenSSL not honouring OpenSSL from ports Message-ID: <15864901-C372-43A8-A6E6-BF0AF73F2EC6@vpnc.org> In-Reply-To: <53621BE0.4040704@geminix.org> References: <201404271508.s3RF8sMA014085@catnip.dyslexicfish.net> <CACdU%2Bf_Wo6VDcJkn6tmF8MTU49=rnJM7SB6XxofGZVdukSarHA@mail.gmail.com> <201404272250.s3RMo2NZ095771@catnip.dyslexicfish.net> <445CDD31-5A11-4F5E-92DE-CB11A10E9BDE@odo.in-berlin.de> <5361896C.7010703@bluerosetech.com> <53621BE0.4040704@geminix.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On May 1, 2014, at 3:03 AM, Uwe Doering <gemini@geminix.org> wrote: > I indeed wondered why this variable hadn't been mentioned so far. = Guys, > you do have "WITH_OPENSSL_PORT=3Dyes" in your "/etc/make.conf", = haven't you? >=20 > Because otherwise the whole thread might be considered a false alert. > The ports system does not link with the ports' OpenSSL of its own > accord. Or at least not in a reliable/predictable manner. You have to > explicitly tell it what you want. Please consider whether it is appropriate to chide people for not = knowing about an *undocumented* feature of make.conf. I'll turn in a pr for it. --Paul HOffman=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15864901-C372-43A8-A6E6-BF0AF73F2EC6>