public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Christian Biesinger <cbiesinger@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] Update README
Date: Fri, 15 Nov 2019 00:47:00 -0000	[thread overview]
Message-ID: <20191115004740.13705.qmail@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=9a3516679ba2e0abdbc4467dbb46f526343efd13

commit 9a3516679ba2e0abdbc4467dbb46f526343efd13
Author: Christian Biesinger <cbiesinger@google.com>
Date:   Mon Nov 11 10:39:31 2019 -0800

    Update README
    
    Adds descriptions for some recent-ish configure options to README.
    
    Also updates the minimum Python version per commit
    6c28e44a359e9f6cf455ddff0009ca99406f7224.
    
    2019-11-14  Christian Biesinger  <cbiesinger@google.com>
    
    	* README (`configure' options): Update.
    
    Change-Id: I8ce8ca6935afbd130295e143802c585cf1e735f9

Diff:
---
 gdb/ChangeLog |  4 ++++
 gdb/README    | 21 ++++++++++++++++++++-
 2 files changed, 24 insertions(+), 1 deletion(-)

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 1a84242..134c883 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,7 @@
+2019-11-14  Christian Biesinger  <cbiesinger@google.com>
+
+	* README (`configure' options): Update.
+
 2019-11-14  Tom Tromey  <tromey@adacore.com>
 
 	* eval.c (evaluate_subexp_standard) <BINOP_ASSIGN>: Do not pass an
diff --git a/gdb/README b/gdb/README
index 8883a8a..be7fdcb 100644
--- a/gdb/README
+++ b/gdb/README
@@ -492,7 +492,7 @@ more obscure GDB `configure' options are not listed here.
      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
+     version of Python supported by GDB is 2.6.  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.
@@ -507,6 +507,16 @@ more obscure GDB `configure' options are not listed here.
      `pkg-config' executable, which will be queried to find the
      information needed to compile and link against Guile.
 
+`--enable-source-highlight'
+     When printing source code, use source highlighting.  This requires
+     libsource-highlight to be installed and is enabled by default
+     if the library is found.
+
+`--with-xxhash'
+     Use libxxhash for hashing.  This has no user-visible effect but
+     speeds up various GDB operations such as symbol loading.  Enabled
+     by default if libxxhash is found.
+
 `--without-included-regex'
      Don't use the regex library included with GDB (as part of the
      libiberty library).  This is the default on hosts with version 2
@@ -528,6 +538,15 @@ more obscure GDB `configure' options are not listed here.
      after being built, the location of the system-wide init file will
      be adjusted accordingly. 
 
+`--with-system-gdbinit-dir=DIR'
+     Configure GDB to automatically load system-wide init files from
+     a directory. Files with extensions `.gdb', `.py' (if Python
+     support is enabled) and `.scm' (if Guile support is enabled) are
+     supported.  DIR should be an absolute directory name.  If DIR is
+     in a directory under the configured prefix, and GDB is moved to
+     another location after being built, the location of the system-
+     wide init directory will be adjusted accordingly.
+
 `--enable-build-warnings'
      When building the GDB sources, ask the compiler to warn about any
      code which looks even vaguely suspicious.  It passes many


                 reply	other threads:[~2019-11-15  0:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20191115004740.13705.qmail@sourceware.org \
    --to=cbiesinger@sourceware.org \
    --cc=gdb-cvs@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).