From owner-freebsd-python@freebsd.org Sat Oct 29 07:21:36 2016 Return-Path: Delivered-To: freebsd-python@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 55081C2692F for ; Sat, 29 Oct 2016 07:21:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 3E14D307 for ; Sat, 29 Oct 2016 07:21:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 3A29DC2692E; Sat, 29 Oct 2016 07:21:36 +0000 (UTC) Delivered-To: python@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 39D57C2692D for ; Sat, 29 Oct 2016 07:21:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) 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 29018305 for ; Sat, 29 Oct 2016 07:21:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9T7LYl0072579 for ; Sat, 29 Oct 2016 07:21:36 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 201523] lang/python27 on raspberry B, _ctypes libffi sysv.S 'invalid instruction' Date: Sat, 29 Oct 2016 07:21:34 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: needs-qa, patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: koobs@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: python@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback+ X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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.23 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Oct 2016 07:21:36 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D201523 --- Comment #14 from Kubilay Kocak --- Removing the option for LIBFFI is a workaround. It's preferable the root ca= use is addressed. Since no-one addressed the reproduction/isolation questions in comment 6 (the reason this is still an open issue), we can proceed as follo= ws: a) Add a BROKEN condition for LIBFFI=3Doff & ARCH=3Dfoo||bar as we do for LIBFFI/i386 currently, OR b) Patch lang/python* portslocally referencing the upstream issues, eventua= lly resulting in the patch not being required once 3.3.x is released and Python= no longer bundles libffi (which they intend to do [1]) Option (b) is preferable (root cause fix), but in order to do that properly= , we need an answer to the following question: Q) Is this a problem only on lang/python2.7 or on every version up to and including lang/python35 (and the Python 3.6 port I intend to commit soon) I'm happy to commit (a) in the meantime until we have that answer, but the following is needed: a) Confirmation is needed from those who are having the issue that this is a acceptable response/resolution. b) A list of all python port versions and all architectures which this has = been reported to be, would be, or are affected. [1] http://bugs.python.org/issue28491 --=20 You are receiving this mail because: You are the assignee for the bug.=