https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201523
Kubilay Kocak <ko...@freebsd.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags| |merge-quarterly?
Status|Open |In Progress
Assignee|pyt...@freebsd.org |ko...@freebsd.org
--- Comment #17 from Kubilay Kocak <ko...@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/arch
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 issue
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 specific
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 people
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 greatly
diminished.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-python@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
