One more tweak to py-m2crypto (ideally also upstream)

2018-09-24 Thread Viktor Dukhovni
On my system OpenSSL 1.1.0 is configured with no RIPEMD160 support. $ egrep '^OPT' /var/db/ports/security_openssl-devel/options | sort OPTIONS_FILE_SET+=ASM OPTIONS_FILE_SET+=DH OPTIONS_FILE_SET+=EC OPTIONS_FILE_SET+=MAN3 OPTIONS_FILE_SET+=SHARED OPTIONS_FILE_SET+=SSE

Re: py-m2crypto conflict with openssl-devel (really swig vs. system headers) resolved

2018-09-24 Thread Viktor Dukhovni
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-

py-m2crypto conflict with openssl-devel (really swig vs. system headers) resolved

2018-09-24 Thread Viktor Dukhovni
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