Bug 2245846

Summary: kernel-tools fails to build with Python 3.13: error: implicit declaration of function '_PyUnicode_AsString', 'PySys_SetArgv'
Product: [Fedora] Fedora Reporter: Karolina Surma <ksurma>
Component: kernel-toolsAssignee: Justin M. Forbes <jforbes>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: acaringi, jforbes, jwboyer, ksurma, lgoncalv, mhroncok, pbrobinson, ptalbert
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-02-15 14:32:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2244836    

Description Karolina Surma 2023-10-24 10:50:16 UTC
kernel-tools fails to build with Python 3.13.0a1.

/builddir/build/BUILD/kernel-6.5.fc40/linux-6.5/tools/perf/util/python.c: In function ‘get_tracepoint_field’:
/builddir/build/BUILD/kernel-6.5.fc40/linux-6.5/tools/perf/util/python.c:517:27: error: implicit declaration of function ‘_PyUnicode_AsString’; did you mean ‘PyUnicode_Substring’? [-Werror=implicit-function-declaration]
  517 |         const char *str = _PyUnicode_AsString(PyObject_Str(attr_name));
      |                           ^~~~~~~~~~~~~~~~~~~
      |                           PyUnicode_Substring

util/scripting-engines/trace-event-python.c: In function ‘python_start_script’:
util/scripting-engines/trace-event-python.c:1937:9: error: implicit declaration of function ‘PySys_SetArgv’ [-Werror=implicit-function-declaration]
 1937 |         PySys_SetArgv(argc + 1, command_line);
      |         ^~~~~~~~~~~~~

According to https://docs.python.org/3.13/whatsnew/3.13.html:
Remove the following old functions to configure the Python initialization, deprecated in Python 3.11:
    PySys_AddWarnOptionUnicode(): use PyConfig.warnoptions instead.
    PySys_AddWarnOption(): use PyConfig.warnoptions instead.
    PySys_AddXOption(): use PyConfig.xoptions instead.
    PySys_HasWarnOptions(): use PyConfig.xoptions instead.
    PySys_SetArgvEx(): set PyConfig.argv instead.
    PySys_SetArgv(): set PyConfig.argv instead.
    PySys_SetPath(): set PyConfig.module_search_paths instead.
    Py_SetPath(): set PyConfig.module_search_paths instead.
    Py_SetProgramName(): set PyConfig.program_name instead.
    Py_SetPythonHome(): set PyConfig.home instead.
    Py_SetStandardStreamEncoding(): set PyConfig.stdio_encoding instead, and set also maybe PyConfig.legacy_windows_stdio (on Windows).
    _Py_SetProgramFullPath(): set PyConfig.executable instead.


https://docs.python.org/3.13/whatsnew/3.13.html

For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.13/fedora-rawhide-x86_64/06546757-kernel-tools/

For all our attempts to build kernel-tools with Python 3.13, see:
https://copr.fedorainfracloud.org/coprs/g/python/python3.13/package/kernel-tools/

Testing and mass rebuild of packages is happening in copr.
You can follow these instructions to test locally in mock if your package builds with Python 3.13:
https://copr.fedorainfracloud.org/coprs/g/python/python3.13/

Let us know here if you have any questions.

Python 3.13 is planned to be included in Fedora 41.
To make that update smoother, we're building Fedora packages with all pre-releases of Python 3.13.
A build failure prevents us from testing all dependent packages (transitive [Build]Requires),
so if this package is required a lot, it's important for us to get it fixed soon.

We'd appreciate help from the people who know this package best,
but if you don't want to work on this now, let us know so we can try to work around it on our side.

Comment 1 Miro Hrončok 2024-02-05 16:16:21 UTC
For the record, the kernel-tools package was retired, but I assume this will be a problem in kernel as well, where the code was moved into. HEce keeping this open for now until we will verify.

Comment 2 Miro Hrončok 2024-02-15 14:32:42 UTC

*** This bug has been marked as a duplicate of bug 2264420 ***