Date: Sat, 29 Oct 2016 07:21:34 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 201523] lang/python27 on raspberry B, _ctypes libffi sysv.S 'invalid instruction' Message-ID: <bug-201523-21822-cVJ7n6XFR0@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-201523-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-201523-21822@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201523 --- Comment #14 from Kubilay Kocak <koobs@FreeBSD.org> --- Removing the option for LIBFFI is a workaround. It's preferable the root cause 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 follows: a) Add a BROKEN condition for LIBFFI=off & ARCH=foo||bar as we do for LIBFFI/i386 currently, OR b) Patch lang/python* portslocally referencing the upstream issues, eventually 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 -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-201523-21822-cVJ7n6XFR0>