... Checking if compiler accepts -fstack-clash-protection : no Checking linker accepts -Wl,-no-undefined : yes Checking linker accepts ['-undefined', 'dynamic_lookup', '-Werror'] : no Checking for program 'python3' : /usr/local/bin/python3.8 Checking for program 'python' : /usr/local/bin/python3.8 Checking for program 'python3' : not found Checking for python version >= 3.4.0 : 3.8.0 python-config : /usr/local/bin/python3.8-config Asking python-config for pyembed '--cflags --libs --ldflags' flags : yes Testing pyembed configuration : Could not build a python embedded interpreter Testing pyembed configuration : Could not build a python embedded interpreter The configuration failed (complete log in /wrkdirs/usr/ports/devel/talloc/work/talloc-2.2.0/bin/config.log) ===> Script "configure" failed unexpectedly. Full log: https://people.freebsd.org/~amdmi3/talloc-python38.log Note that talloc 2.3.0 is available, it may be that it has python 3. compatibility fixed.
Created attachment 209079 [details] Patch file I tried talloc 2.3.0 with attached patch and succeeded to build with Python 3.8.
Maintainer timeout
(In reply to Dmitry Marakasov from comment #2) Dmity, why on Earth you are touching things that you have no clue about?
A commit references this bug: Author: amdmi3 Date: Sat Nov 23 12:54:05 UTC 2019 New revision: 518227 URL: https://svnweb.freebsd.org/changeset/ports/518227 Log: - Update to 2.3.0, fixing build with python 3.8 PR: 241791 [1], 241793 [2] Submitted by: yasu@utahime.org [1], osidorkin@gmail.com [2] Reported by: amdmi3 [1] Approved by: maintainer timeout (timur, 2 weeks) Changes: head/devel/talloc/Makefile head/devel/talloc/distinfo head/devel/talloc/files/patch-buildtools_wafsamba_samba__autoconf.py
(In reply to Timur I. Bakeyev from comment #3) > Dmity, why on Earth you are touching things that you have no clue about? Please justify this accusation at once. These updates were reviewed, build tested with all dependees and run tested with samba410. Closing the PRs causing breakages for multiple people with incorrect resolution with no comment after weeks of inactivity is at least impolite on your side.