Linux Perf Users
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: linux-perf-users@vger.kernel.org
Subject: [BUG?] perf build: Fail to build perf source with Python 3.15
Date: Sat, 14 Nov 2026 16:48:31 -0800	[thread overview]
Message-ID: <avkBX8dfvxaBiyIb@z2> (raw)

Hello,

Recently I've upgrade my machine to Fedora 45 and I cannot build perf
from source anymore.  The error is like below

    GEN     python/perf.cpython-315-x86_64-linux-gnu.so
  In file included from /usr/include/python3.15/Python.h:68,
                   from linux/tools/perf/util/python.c:3:
  /usr/include/python3.15/pyport.h:494:9: error: ‘_Py_STDC_VERSION’ is not defined, evaluates to ‘0’ [-Werror=undef]
    494 | #  elif _Py_STDC_VERSION >= 201112L && !defined(__STDC_NO_THREADS__)
        |         ^~~~~~~~~~~~~~~~
  cc1: all warnings being treated as errors
  error: command '/usr/lib64/ccache/gcc' failed with exit code 1
  cp: cannot stat 'python_ext_build/lib/perf*.so': No such file or directory

Looks like a bug in the python code.  I found a bug report in Github.

https://github.com/python/cpython/issues/160719

Thanks,
Namhyung


                 reply	other threads:[~2026-11-15  0:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=avkBX8dfvxaBiyIb@z2 \
    --to=namhyung@kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox