Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Update gdb's configure instructions
Date: Fri, 28 Sep 2018 07:41:00 -0000	[thread overview]
Message-ID: <83ftxu6pdo.fsf@gnu.org> (raw)
In-Reply-To: <87y3bminvq.fsf@tromey.com> (message from Tom Tromey on Thu, 27	Sep 2018 16:20:09 -0600)

> From: Tom Tromey <tom@tromey.com>
> Cc: Tom Tromey <tom@tromey.com>,  gdb-patches@sourceware.org
> Date: Thu, 27 Sep 2018 16:20:09 -0600
> 
> I think this version addresses all the comments.

Thanks.  This LGTM, modulo 2 nits below.

> I hope so anyway, I tend to lose patience editing this text.

I know how you feel, thanks for doing this.

> +`--with-lzma'
> +     Build GDB with LZMA, a compression library.  (Done by default if
> +     liblzma is installed and found at configure time.)  LZMA is used
> +     by GDB's "mini debuginfo" feature, which is only useful on
> +     platforms using the ELF object file format..  If your host does
                                                  ^^
A typo.

> +`--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
> +     you can find it on `http://www.python.org/download/'.  The oldest
>       version of Python supported by GDB is 2.4.  The optional argument
> -     PATH says where to find the Python headers and libraries; the
> -     configure script will look in PATH/include for headers and in
> -     PATH/lib for the libraries.
> +     PYTHON names a Python executable, which will be queried to find
> +     the Python headers and libraries.

Did this change since GDB 8.2?  Because when I built GDB 8.2, the
argument to --with-python was the top-level directory of the Python
installation on my build system.


  reply	other threads:[~2018-09-28  7:41 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 [this message]
2018-09-28 20:01       ` Tom Tromey
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=83ftxu6pdo.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.com \
    /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