NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above. NOTE: This is a Python port. Instead of py312-cffi listed in the above command, you can pick from the names under the Packages section.
all: remove explicit versions in USES=python for "3.x+"
The logic in USES=python will automatically convert this to 3.8+ by
itself.
Adjust two ports that only had Python 3.7 mentioned but build fine
on Python 3.8 too.
finance/quickfix: mark BROKEN with PYTHON
libtool: compile: c++ -DHAVE_CONFIG_H -I. -I../.. -I -I. -I.. -I../.. -I../C++
-DLIBICONV_PLUG -DPYTHON_MAJOR_VERSION=3 -Wno-unused-variable
-Wno-maybe-uninitialized -O2 -pipe -DLIBICONV_PLUG -fstack-protector-strong
-fno-strict-aliasing -DLIBICONV_PLUG -Wall -ansi
-Wno-unused-command-line-argument -Wpointer-arith -Wwrite-strings
-Wno-overloaded-virtual -Wno-deprecated-declarations -Wno-deprecated -std=c++0x
-MT _quickfix_la-QuickfixPython.lo -MD -MP -MF
.deps/_quickfix_la-QuickfixPython.Tpo -c QuickfixPython.cpp -fPIC -DPIC -o
.libs/_quickfix_la-QuickfixPython.o
warning: unknown warning option '-Wno-maybe-uninitialized'; did you mean
'-Wno-uninitialized'? [-Wunknown-warning-option]
QuickfixPython.cpp:175:11: fatal error: 'Python.h' file not found
^~~~~~~~~~
1 warning and 1 error generated.
Reviewed by: portmgr, vishwin, yuri
Differential Revision: <https://reviews.freebsd.org/D40568>
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
devel: remove 'Created by' lines
A big Thank You to the original contributors of these ports:
* "Waitman Gobble" <uzimac@da3m0n8t3r.com>
* <jkoshy@FreeBSD.org>
* Aaron Dalton <aaron@FreeBSD.org>
* Aaron Dalton <aaron@daltons.ca>
* Aaron H. K. Diep <ahkdiep@gmail.com>
* Aaron Hurt <ahurt@anbcs.com>
* Abel Chow <abel_chow@yahoo.com>
* Adam McLaurin
* Adam Saponara <as@php.net>
* Adam Weinberger <adamw@FreeBSD.org>
* Ade Lovett <ade@FreeBSD.org>
(Only the first 15 lines of the commit message are shown above )
Relax hardcoded paths to fix build with Python 3.8.7
Since r558913 Python 3.8 incorporates BPO-42604 [1] which changed the
shared libs naming scheme. This means "EXT_SUFFIX" is now derived from
SOABI and yields with Python 3.8 to ".cpython-38.so" instead of ".so".
The affected ports strip the libaries in the "post-install" target via
hardcoded path(s) and the build fails at the end because the new extension
is not expected at this place.
Remedy the issue by adding wildcards to these paths. This should also
prepare the ports for future Python releases, which will use the new shared
libs naming scheme.
[1] https://bugs.python.org/issue42604
PR: 252057
Reported by: John Kennedy
Reviewed by: fluffy, koobs
Approved by: koobs (python)
Chanse update of devel/libffi
Chase the devel/libffi update
Bump portrevision of all dependent ports to chace shard library version bump
in libffi.
Update LIB_DEPENDS lines where needed to not require a specific version of
libffi.so.
PR: 247028 (for tracking)
Remove compatibility code for FreeBSD < 11.2 from all ports.
Simplify some ports where DragonFlyBSD no longer needs to be special-cased.
Submitted by: rene
Reviewed by: bapt, jbeich
Differential Revision: https://reviews.freebsd.org/D17724
Convert Python ports to FLAVORS.
Ports using USE_PYTHON=distutils are now flavored. They will
automatically get flavors (py27, py34, py35, py36) depending on what
versions they support.
There is also a USE_PYTHON=flavors for ports that do not use distutils
but need FLAVORS to be set. A USE_PYTHON=noflavors can be set if
using distutils but flavors are not wanted.
A new USE_PYTHON=optsuffix that will add PYTHON_PKGNAMESUFFIX has been
added to cope with Python ports that did not have the Python
PKGNAMEPREFIX but are flavored.
USES=python now also exports a PY_FLAVOR variable that contains the
(Only the first 15 lines of the commit message are shown above )
devel/py-cffi: Use OPSYS with OSVERSION, USES+= localbase
r419747 introduced OSVERSION with a ">" comparison without using coupling
with OPSYS, fix.
It also removed CFLAGS and LDFLAGS as "unnecessary", but the fact is they
are still required for non-standard localbases and compilers that don't
search /usr/local/include by default. Restore these flags with the
equivalent USES+=localbase
Approved by: OPVERSION/OPSYS blanket, just-fix-it
devel/py-cffi: Fix build warnings and test failures
CFLAGS contains -Wl,-rpath,${LOCALBASE}/lib, which causes the following
warnings:
warning: -Wl,-rpath,/usr/local/lib: 'linker' input unused
It also causes many tests to fail due to the same warning:
E VerificationError: CompileError: command 'cc' failed with exit status 1
cffi/ffiplatform.py:62: VerificationError
----------- Captured stderr call ----------
error: -Wl,-rpath,/usr/local/lib: 'linker' input unused
(Only the first 15 lines of the commit message are shown above )
Invoke pytest from within desired python version
When testing a port for a non-default python py.test may fail to find
dependencies for default version because they weren't built e.g.,
$ make test PYTHON_VERSION=python3.5 -C devel/py-apscheduler
[...]
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.5/site-packages/_pytest/config.py", line 319, in
_importconftest
mod = conftestpath.pyimport()
File "/usr/local/lib/python3.5/site-packages/py/_path/local.py", line 650, in
pyimport
__import__(modname)
File
"/usr/ports/devel/py-apscheduler/work/APScheduler-3.2.0/tests/conftest.py", line
8, in <module>
from apscheduler.job import Job
File
"/usr/ports/devel/py-apscheduler/work/APScheduler-3.2.0/apscheduler/job.py",
line 4, in <module>
import six
ImportError: No module named 'six'
ERROR: could not load
/usr/ports/devel/py-apscheduler/work/APScheduler-3.2.0/tests/conftest.py
Approved by: portmgr blanket
devel/py-cffi: Backport upstream pull request #56
Backport upstream pull request #56 [1] which fixes (double) building for
Python packackges that use py-cffi to compile their modules.
This issue manifested itself in the 'install' target (stage) of Python
port building, causing the module that was already built at the 'build'
stage to be built again, except *without* the build arguments provided
in the build stage.
These symptoms were observable in security/py-cryptography [2]
While I'm here:
- Add regression-test target and TEST_DEPENDS
(Only the first 15 lines of the commit message are shown above )
devel/py-cffi: Foreign Function Interface for Python calling C code
Foreign Function Interface for Python calling C code.
WWW: http://cffi.readthedocs.org/
