More testing needs to be done on arm to see if our dtrace support is
compatible with what ruby needs. PowerPC may work as well, but needs
more testing.
Reviewed by: swills
As per lang/python27 (r377581):
- Add BROKEN for i386 without LIBFFI option, and add upstream
issue references.
While I'm here, clean up after the LIBFFI option addition:
- Sort options variables: OPTIONS_* and *_DESC
- Use OPTIONS helpers
- Reduce diffs between lang/python* ports
As per lang/python27 (r377581):
- Add BROKEN for i386 without LIBFFI option, and add upstream
issue references.
While I'm here, clean up after the LIBFFI option addition:
- Sort options variables: OPTIONS_* and *_DESC
- Use OPTIONS helpers
- Reduce diffs between lang/python* ports
Changes:
* Improved warmup time.
* Improved hitted code performance (+10% compared to v2.4).
* Passing objects between C and PyPy has been improved.
* Integrated numpy support gains GenericUfunc API.
* Dictionaries are ordered by default.
* More careful handling of errno.
from ports is able to handle unicode. Make sure that ruby does not provides its
own function to read the input but let libedit do it itself.
This allows the binary package to by default not be "tainted" by the readline
license.
Differential Revision: https://reviews.freebsd.org/D1547
Reviewed by: swills
Approved by: ruby (swills)
This module is an implementation of the "Promise/A+" pattern for
asynchronous programming. Promises are meant to be a way to
better deal with the resulting callback spaghetti that can often
result in asynchronous programs.
The bad news:
1. gcc is still required -- clang can build the binaries, but
some self-tests will fail, unless all optimization was
disabled. This is, probably, due to some suspect code in
bytenumb.c -- would be good to investigate.
2. Building this port in parallel is still not possible -- the
Makefile is too convoluted and same sources are recompiled
multiple times with different #defines set.
The good news:
1. Resolve a large number of warnings.
2. Fix build on ia64 and sparc64 (tested on pluto and flame
respectively). Other platforms (alpha, powerpc?) have a
better chance of working now...
libgcj-5.0.pc is now properly called libgcj-5.pc; adjust pkg-plist.
libffi is broken on FreeBSD i386 since 2015-01-11, cf.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64779, so disable it
for the time being.
- Added LICENSE (EGENIX)
- Changed MASTER_SITES from https to http to support downloading from behind proxy
Differential Revision: https://reviews.freebsd.org/D1635
Approved by: bapt(mentor)
Investigating the comment regarding a 'configure script bug' lead me
to a bug which manifested itself in 'm' not being added to ABIFLAGS
when PYMALLOC was enabled, not the inability to set
--without-pymalloc using PYMALLOC_CONFIGURE_WITH (options helpers).
The incorrect ABIFLAGS caused packaging failures with default options, so
I'm not sure how this wasn't picked up earlier:
Error: Orphaned: include/python3.2u/<file>
<snip>
Error: Missing: include/python3.2mu/<file>
- Backport an upstream commit [1] to correct the configure bug that never
made it to the 3.2 branch.
- Use options helpers for PYMALLOC accordingly
While I'm here, clean up after the LIBFFI option addition:
- Sort options variables: OPTIONS_* and *_DESC
- Use OPTIONS helpers
[1] https://hg.python.org/cpython/raw-rev/d158b0a78390
Approved by: python
