public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Andrew Burgess via Gdb-patches <gdb-patches@sourceware.org>
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: Re: [PATCH] gdb/python: look for python, then python 3 at configure time
Date: Fri, 15 Jul 2022 11:12:39 -0600	[thread overview]
Message-ID: <87ilnypaew.fsf@tromey.com> (raw)
In-Reply-To: <20220704162731.258145-1-aburgess@redhat.com> (Andrew Burgess via Gdb-patches's message of "Mon, 4 Jul 2022 17:27:31 +0100")

>>>>> "Andrew" == Andrew Burgess via Gdb-patches <gdb-patches@sourceware.org> writes:

Andrew> This commit updates GDB's configure.ac script to first look for
Andrew> 'python', and then 'python3'.  Now, on a system that only has a
Andrew> python3 executable, GDB will automatically find, and use that in order
Andrew> to provide python support, no user supplied configure arguments are
Andrew> needed.

This seems fine to me.  Thanks.

Tom

  reply	other threads:[~2022-07-15 17:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-04 16:27 Andrew Burgess
2022-07-15 17:12 ` Tom Tromey [this message]
2022-07-18 10:35   ` Andrew Burgess

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=87ilnypaew.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=aburgess@redhat.com \
    --cc=gdb-patches@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).