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] [gdb/build] python 3.10 problems
Date: Sat, 02 Jul 2022 09:17:37 +0000 [thread overview]
Message-ID: <bug-29308-4717-R7DyxnCq6B@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29308-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29308
--- Comment #8 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Simon Marchi from comment #7)
> > FWIW, I need to install python3-devel to get python3-config, in addition to the python3 package, but that's not a problem of course. I need to install lots of -devel packages to be able to build gdb.
>
> I would expect that you need python3-devel anyway, since that's probably
> what provides Python.h?
>
True.
> > I guess this will break pre 3.4 python setup.
> >
> > So perhaps, it's an idea to first try python's python-config, and if that doesn't work, fall back on gdb's.
>
> I don't think it's a big deal to break pre-Python 3.4. We currently support
> Python pre-3.4, just because there wasn't a specific reason not to. It
> didn't require significantly more work to do so. This could be a good
> reason to start requiring Python >= 3.4, if doing so makes things
> significantly simpler.
Crossref https://sourceware.org/pipermail/gdb-patches/2022-January/184908.html
.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-07-02 9:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 17:01 [Bug build/29308] New: " vries at gcc dot gnu.org
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 [this message]
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-R7DyxnCq6B@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).