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: Fri, 01 Jul 2022 09:53:45 +0000 [thread overview] Message-ID: <bug-29308-4717-Jn7Y55SWEC@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29308-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29308 Tom de Vries <vries at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kevinb at redhat dot com --- Comment #5 from Tom de Vries <vries at gcc dot gnu.org> --- Kevin, I saw you submit a patch for python 3.11 support ( https://sourceware.org/pipermail/gdb-patches/2022-June/190460.html ). Did you also run into this build issue? -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-07-01 9:53 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 [this message] 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-Jn7Y55SWEC@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: linkBe 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).