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:
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
`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:
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