[prev in list] [next in list] [prev in thread] [next in thread]
List: gdb-cvs
Subject: [binutils-gdb] gdb: remove trailing spaces in README
From: Simon Marchi via Gdb-cvs <gdb-cvs () sourceware ! org>
Date: 2022-09-28 18:59:20
Message-ID: 20220928190423.BE56F385740A () sourceware ! org
[Download RAW message or body]
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=e875475e19d13aa4283571f399848eab64f96ae0
commit e875475e19d13aa4283571f399848eab64f96ae0
Author: Simon Marchi <simon.marchi@efficios.com>
Date: Wed Sep 28 09:58:51 2022 -0400
gdb: remove trailing spaces in README
Change-Id: Ic7f8e415acd1bff6194cf08ed646bff45571f165
Diff:
---
gdb/README | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/gdb/README b/gdb/README
index bd5a88f348c..406df046053 100644
--- a/gdb/README
+++ b/gdb/README
@@ -39,7 +39,7 @@ You can build GDB right in the source directory:
However, we recommend that an empty directory be used instead.
This way you do not clutter your source tree with binary files
-and will be able to create different builds with different
+and will be able to create different builds with different
configuration options.
You can build GDB in any empty build directory:
@@ -141,7 +141,7 @@ use depends on your system; `lpr -d' is common; another (for PostScript
devices) is `dvips'. The DVI print command may require a file name
without any extension or a `.dvi' extension.
- TeX also requires a macro definitions file called `texinfo.tex'.
+ TeX also requires a macro definitions file called `texinfo.tex'.
This file tells TeX how to typeset a document written in Texinfo
format. On its own, TeX cannot read, much less typeset a Texinfo file.
`texinfo.tex' is distributed with GDB and is located in the
@@ -318,7 +318,7 @@ three pieces of information in the following pattern:
`sparc-sun-sunos4'.
The `configure' script accompanying GDB does not provide any query
-facility to list all supported host and target names or aliases.
+facility to list all supported host and target names or aliases.
`configure' calls the Bourne shell script `config.sub' to map
abbreviations to full names; you can read the script, if you wish, or
you can use it to test your guesses on abbreviations--for example:
@@ -550,7 +550,7 @@ more obscure GDB `configure' options are not listed here.
FILE should be an absolute file name. If FILE 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 file will
- be adjusted accordingly.
+ be adjusted accordingly.
`--with-system-gdbinit-dir=DIR'
Configure GDB to automatically load system-wide init files from
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic