From owner-freebsd-python@FreeBSD.ORG  Tue Dec 23 17:04:45 2014
Return-Path: <owner-freebsd-python@FreeBSD.ORG>
Delivered-To: python@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 04B1DAA
 for <python@FreeBSD.org>; Tue, 23 Dec 2014 17:04:45 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (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 DFFCA1F44
 for <python@FreeBSD.org>; Tue, 23 Dec 2014 17:04:44 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sBNH4i2j027553
 for <python@FreeBSD.org>; Tue, 23 Dec 2014 17:04:44 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: python@FreeBSD.org
Subject: [Bug 196229] lang/python27 build fails with LIBFFI option off
Date: Tue, 23 Dec 2014 17:04:45 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Ports Tree
X-Bugzilla-Component: Individual Port(s)
X-Bugzilla-Version: Latest
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: mva@FreeBSD.org
X-Bugzilla-Status: Open
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: python@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: maintainer-feedback?
X-Bugzilla-Changed-Fields: bug_file_loc see_also bug_status
Message-ID: <bug-196229-21822-UkoVWtnVY9@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-196229-21822@https.bugs.freebsd.org/bugzilla/>
References: <bug-196229-21822@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-python@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: FreeBSD-specific Python issues <freebsd-python.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-python>,
 <mailto:freebsd-python-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-python/>
List-Post: <mailto:freebsd-python@freebsd.org>
List-Help: <mailto:freebsd-python-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-python>,
 <mailto:freebsd-python-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Dec 2014 17:04:45 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196229

Marcus von Appen <mva@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                URL|                            |http://bugs.python.org/issu
                   |                            |e22521
           See Also|                            |https://bugs.freebsd.org/bu
                   |                            |gzilla/show_bug.cgi?id=1946
                   |                            |84
             Status|New                         |Open

--- Comment #4 from Marcus von Appen <mva@FreeBSD.org> ---
Looks like some of the backports from 3.4 will cause 2.7 to break now, too. Bug
194684 and http://bugs.python.org/issue22521 contain those information.
Unfortunately there is no fix for that issue as of now.

The current recommendation is to keep LIBFFI enabled on the i386 arch. If there
are no news within the next few days, we will add a BROKEN message for i386, if
LIBFFI is disabled.

-- 
You are receiving this mail because:
You are the assignee for the bug.