public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/29308] New: [gdb/build] python 3.10 problems
Date: Thu, 30 Jun 2022 17:01:00 +0000 [thread overview]
Message-ID: <bug-29308-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29308
Bug ID: 29308
Summary: [gdb/build] python 3.10 problems
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: build
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
On openSUSE tumbleweed I build with --with-python=python3, and python3 has
recently been bumped to:
...
$ /usr/bin/python3 --version
Python 3.10.5
...
Consequently, I run into build failures, due to (reproducing outside build):
...
$ python3.10 ./gdb/python/python-config.py --includes
./gdb/python/python-config.py:7: DeprecationWarning: The distutils package is
deprecated and slated for removal in Python 3.12. Use setuptools or check PEP
632 for potential alternatives
from distutils import sysconfig
/data/vries/gdb_versions/devel/binutils-gdb.git/./gdb/python/python-config.py:7:
DeprecationWarning: The distutils.sysconfig module is deprecated, use sysconfig
instead
from distutils import sysconfig
-I/usr/include/python3.10 -I/usr/include/python3.10
...
The message suggests using module sysconfig, but there's no suppport for
get_python_inc in there.
The PEP also doesn't list a solution.
Also setuptools is mentioned, but that doesn't seem to provide a get_python_inc
replacement either.
Looking in python3-config, it's no longer a python script, but a shell script,
so we can't find an example there either.
For now working around it by using --with-python=/usr/bin/python3.8.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-06-30 17:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 17:01 vries at gcc dot gnu.org [this message]
2022-06-30 17:48 ` [Bug build/29308] " simark at simark dot ca
2022-07-01 9:27 ` vries at gcc dot gnu.org
2022-07-01 9:28 ` vries at gcc dot gnu.org
2022-07-01 9:35 ` vries at gcc dot gnu.org
2022-07-01 9:53 ` vries at gcc dot gnu.org
2022-07-01 15:14 ` kevinb at redhat dot com
2022-07-01 15:18 ` simark at simark dot ca
2022-07-02 9:17 ` vries at gcc dot gnu.org
2022-07-02 9:43 ` [Bug build/29308] [gdb/build] python 3.12 problems vries at gcc dot gnu.org
2022-09-01 9:09 ` vries at gcc dot gnu.org
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=bug-29308-4717@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).