On Mon, Sep 24, 2018 at 08:24:25PM +1000, Kubilay Kocak wrote:
> I also note that there is an open bug report for the issue:
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229019
Thanks. And it looks like the work-around I suggested has been
adopted, after "portsnap fetch update", my py-
On 24/09/2018 6:08 pm, Viktor Dukhovni wrote:
> In /etc/make.conf I have:
>
> DEFAULT_VERSIONS=python=2.7 python2=2.7 python3=3.3 ssl=openssl-devel
>
> since I want OpenSSL 1.1.0 for most of the ports I build. However, this
> disables the py2-m2crypto port, whose Makefile contains:
>
>
On 24/09/2018 6:08 pm, Viktor Dukhovni wrote:
> In /etc/make.conf I have:
>
> DEFAULT_VERSIONS=python=2.7 python2=2.7 python3=3.3 ssl=openssl-devel
>
> since I want OpenSSL 1.1.0 for most of the ports I build. However, this
> disables the py2-m2crypto port, whose Makefile contains:
>
>
In /etc/make.conf I have:
DEFAULT_VERSIONS=python=2.7 python2=2.7 python3=3.3 ssl=openssl-devel
since I want OpenSSL 1.1.0 for most of the ports I build. However, this
disables the py2-m2crypto port, whose Makefile contains:
BROKEN_SSL=openssl-devel
BROKEN_SSL_REASON_openssl-dev
