From owner-freebsd-python@freebsd.org Mon Sep 24 14:09:23 2018 Return-Path: Delivered-To: freebsd-python@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1B6A110AD269 for ; Mon, 24 Sep 2018 14:09:23 +0000 (UTC) (envelope-from ietf-dane@dukhovni.org) Received: from straasha.imrryr.org (straasha.imrryr.org [100.2.39.101]) (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 C7FFC82254 for ; Mon, 24 Sep 2018 14:09:22 +0000 (UTC) (envelope-from ietf-dane@dukhovni.org) Received: by straasha.imrryr.org (Postfix, from userid 1001) id C31BD30402C; Mon, 24 Sep 2018 10:09:15 -0400 (EDT) Date: Mon, 24 Sep 2018 10:09:15 -0400 From: Viktor Dukhovni To: freebsd-python@freebsd.org Subject: Re: py-m2crypto conflict with openssl-devel (really swig vs. system headers) resolved Message-ID: <20180924140915.GL3589@straasha.imrryr.org> Reply-To: freebsd-python@freebsd.org References: <20180924080803.GK3589@straasha.imrryr.org> <0dab868d-d1bf-12db-40cb-47136dd4c7e1@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0dab868d-d1bf-12db-40cb-47136dd4c7e1@FreeBSD.org> User-Agent: Mutt/1.10.1 (2018-07-13) X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2018 14:09:23 -0000 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-m2crypto builds without any additional work-arounds on my part. The quick turn-around is much appreciated. -- Viktor.