Date: Sat, 29 Oct 2016 07:45:19 +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-qe9UndG9NN@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/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D201523 Kubilay Kocak <koobs@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |merge-quarterly? Status|Open |In Progress Assignee|python@FreeBSD.org |koobs@FreeBSD.org --- Comment #17 from Kubilay Kocak <koobs@FreeBSD.org> --- (In reply to Chris Rees from comment #16) Removing the option when that becomes the default (3.7) is perfectly reasonable. Removing it prior is over-inclusive. A BROKEN for the option/ar= ch combination (option (a) in comment 14) addresses the issue as reported/isolated. If the issue affects more than just arm, or a case can be made that the iss= ue is a result of a single-ARCH-specific instruction being used and there is no practical workaround or fix, sure, limiting the LIBFFI option to that speci= fic ARCH then becomes an understandable request. In the meantime the libffi option (both in the port and upstreap) as well as the ability to switch between the default (bundled) and a system version via configure is entirely supported. All that is required is list of ARCHS and Python ports for which this is an issue, as we have a fix for the problem in attachment 158689 What won't happen is partial resolution, as that creates more work for peop= le down the track. In particular, given the issue is not reproducible in the OPTIONS_DEFAULT case, the urgency and warrant to workaround fix this is gre= atly diminished. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-201523-21822-qe9UndG9NN>