[Bug 243610] sysutils/py-salt failed to build with python 3.8
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Fri Feb 7 07:19:24 UTC 2020
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243610
--- Comment #8 from Tommy P <tommyhp2 at gmail.com> ---
(In reply to Kubilay Kocak from comment #7)
When I tried to build sysutils/py-salt with python 3.7 and the selected option:
RAET=on: Install dependencies required for RAET transport
It failed because the two dependent ports net/py-raet and devel/py-ioflo as
seen sysutils/py-salt/Makefile:
RAET_RUN_DEPENDS=
${PYTHON_PKGNAMEPREFIX}libnacl>=1.0.0:security/py-libnacl@${PY_FLAVOR} \
${PYTHON_PKGNAMEPREFIX}ioflo>=1.1.7:devel/py-ioflo@${PY_FLAVOR} \
${PYTHON_PKGNAMEPREFIX}raet>=0.6.0:net/py-raet@${PY_FLAVOR}
were configured for python 2.7 in the Makefiles at the time of this report.
The only way I could get successful build was make the changes as seen in the
patches. As for other ports using devel/py-ioflo and/or net/py-raet, I've
found only sysutils/py-salt in the entire ports tree:
# grep -Rn 'py-raet' * |grep Makefile
net/Makefile:1106: SUBDIR += py-raet
net/py-raet/Makefile:2:# $FreeBSD: head/net/py-raet/Makefile 483068 2018-10-27
00:42:41Z swills $
net/py-raet/Makefile.ori:2:# $FreeBSD: head/net/py-raet/Makefile 483068
2018-10-27 00:42:41Z swills $
sysutils/py-salt/Makefile:77:
${PYTHON_PKGNAMEPREFIX}raet>=0.6.0:net/py-raet@${PY_FLAVOR}
# grep -Rn 'py-ioflo' *|grep Makefile
devel/Makefile:4504: SUBDIR += py-ioflo
devel/py-ioflo/Makefile:2:# $FreeBSD: head/devel/py-ioflo/Makefile 483079
2018-10-27 00:55:31Z swills $
devel/py-ioflo/Makefile.ori:2:# $FreeBSD: head/devel/py-ioflo/Makefile 483079
2018-10-27 00:55:31Z swills $
sysutils/py-salt/Makefile:76:
${PYTHON_PKGNAMEPREFIX}ioflo>=1.1.7:devel/py-ioflo@${PY_FLAVOR} \
Currently, sysutils/py-salt is configured to build all versions of python
(except 3.8 as I've found out and upstream does not fully support 3.8 yet)
except with option RAET (as I've also found out).
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the freebsd-python
mailing list