From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Adrian Hunter <adrian.hunter@intel.com>,
Ian Rogers <irogers@google.com>,
James Clark <james.clark@linaro.org>,
Jiri Olsa <jolsa@kernel.org>,
Kan Liang <kan.liang@linux.intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH 1/1 v6.17] perf python: Stop using deprecated PyUnicode_AsString()
Date: Fri, 01 Aug 2025 10:24:36 -0700 [thread overview]
Message-ID: <175406907667.1475083.1184937311863486488.b4-ty@kernel.org> (raw)
In-Reply-To: <aIofXNK8QLtLIaI3@x1>
On Wed, 30 Jul 2025 10:34:20 -0300, Arnaldo Carvalho de Melo wrote:
> As noticed while building for Fedora 43:
>
> GEN /tmp/build/perf/python/perf.cpython-314-x86_64-linux-gnu.so
> /git/perf-6.16.0-rc3/tools/perf/util/python.c: In function ‘get_tracepoint_field’:
> /git/perf-6.16.0-rc3/tools/perf/util/python.c:340:9: error: ‘_PyUnicode_AsString’ is deprecated [-Werror=deprecated-declarations]
> 340 | const char *str = _PyUnicode_AsString(PyObject_Str(attr_name));
> | ^~~~~
> In file included from /usr/include/python3.14/unicodeobject.h:1022,
> from /usr/include/python3.14/Python.h:89,
> from /git/perf-6.16.0-rc3/tools/perf/util/python.c:2:
> /usr/include/python3.14/cpython/unicodeobject.h:648:1: note: declared here
> 648 | _PyUnicode_AsString(PyObject *unicode)
> | ^~~~~~~~~~~~~~~~~~~
> cc1: all warnings being treated as errors
> error: command '/usr/bin/gcc' failed with exit code 1
>
> [...]
Applied to perf-tools-next, thanks!
Best regards,
Namhyung
prev parent reply other threads:[~2025-08-01 17:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 13:34 Arnaldo Carvalho de Melo
2025-08-01 17:24 ` Namhyung Kim [this message]
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=175406907667.1475083.1184937311863486488.b4-ty@kernel.org \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®