From: Tom Tromey <tom@tromey.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [RFA] Update gdb's configure instructions
Date: Fri, 28 Sep 2018 20:01:00 -0000 [thread overview]
Message-ID: <87h8i9ie76.fsf@tromey.com> (raw)
In-Reply-To: <83ftxu6pdo.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 28 Sep 2018 10:40:51 +0300")
>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
Eli> Did this change since GDB 8.2? Because when I built GDB 8.2, the
Eli> argument to --with-python was the top-level directory of the Python
Eli> installation on my build system.
It can be either, it turns out. How's this text?
`--with-python[=PYTHON]'
Build GDB with Python scripting support. (Done by default if
libpython is present and found at configure time.) Python makes
GDB scripting much more powerful than the restricted CLI
scripting language. If your host does not have Python installed,
you can find it on `http://www.python.org/download/'. The oldest
version of Python supported by GDB is 2.4. The optional argument
PYTHON is used to find the Python headers and libraries. It can
be either the name of a Python executable, or the name of the
directory in which Python is installed.
and in gdb.texinfo:
@item Python
@value{GDBN} can be scripted using Python language. @xref{Python}.
By default, @value{GDBN} will be compiled if the Python libraries are
installed and are found by @file{configure}. You can use the
@code{--with-python} option to request Python, and pass either the
file name of the relevant @code{python} executable, or the name of the
directory in which Python is installed, to choose a particular
installation of Python.
Tom
next prev parent reply other threads:[~2018-09-28 20:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 4:30 Tom Tromey
2018-09-14 8:28 ` Eli Zaretskii
2018-09-27 22:20 ` Tom Tromey
2018-09-28 7:41 ` Eli Zaretskii
2018-09-28 20:01 ` Tom Tromey [this message]
2018-09-28 21:18 ` Eli Zaretskii
2018-09-14 16:17 ` John Baldwin
2018-09-27 22:21 ` Tom Tromey
2018-09-28 16:24 ` John Baldwin
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=87h8i9ie76.fsf@tromey.com \
--to=tom@tromey.com \
--cc=eliz@gnu.org \
--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