Date: Thu, 21 Jul 2016 17:13:32 +0100 From: tech-lists <tech-lists@zyxst.net> To: freebsd-ports@freebsd.org Subject: Re: stunnel fails to build Message-ID: <8a5d48e8-fa5c-5cd2-f209-2d634b6b7723@zyxst.net> In-Reply-To: <CAGnMC6oK7r_74Vfsgh3FEyvg8Eboc4f4nSdOaE8pWSGCvW5yJA@mail.gmail.com> References: <57d3d4e8-ed5b-ee6d-073e-81b7fe1afb30@zyxst.net> <CAGnMC6oK7r_74Vfsgh3FEyvg8Eboc4f4nSdOaE8pWSGCvW5yJA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 07/21/16 11:29, Dewayne Geraghty wrote: > After reading about your issue, I updated all of my ports, via svnlite, and > successfully built on yesterday's fresh FreeBSD 10.3 Stable for i386 using > openssl. Unfortunately on the amd64, which uses libressl, I receive: > ===> stunnel-5.35,1 may not be packaged: The stunnel license restricts > distribution when linked to non-OpenSSL non-base SSL-libraries. (A recent > enhancement) > > My customisations are: > i386 uses make.conf entry: ssl=openssl > amd64 uses make.conf: ssl=libressl > This may be significant to your situation? > > If there is a problem with the Makefile, please log a PR so everyone can > benefit. ;) I dunno if there's a problem with the makefile or with the software as suggested amendments had no effect. The "stunnel may not be packaged" message is one related to distribution and is not a problem with compilation per se. thanks, -- J.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8a5d48e8-fa5c-5cd2-f209-2d634b6b7723>