aboutsummaryrefslogtreecommitdiff
path: root/gdb
diff options
context:
space:
mode:
authorRoland Pesch <pesch@cygnus>1991-04-06 00:13:19 +0000
committerRoland Pesch <pesch@cygnus>1991-04-06 00:13:19 +0000
commitefd784ca05a0820ab74fea72bec63ba8d3e68bc7 (patch)
tree0b5e8f2af5a0670038ce0431fc4e0cfa3d62ed7b /gdb
parent52d9ccbbaef8f86ebdc3d31c3d0d1b6f37ec0ab0 (diff)
downloadgdb-efd784ca05a0820ab74fea72bec63ba8d3e68bc7.zip
gdb-efd784ca05a0820ab74fea72bec63ba8d3e68bc7.tar.gz
gdb-efd784ca05a0820ab74fea72bec63ba8d3e68bc7.tar.bz2
Added John Gilmore's advice on subdirs to installation appendix.
Diffstat (limited to 'gdb')
-rw-r--r--gdb/doc/gdb.texinfo18
1 files changed, 13 insertions, 5 deletions
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index a1d12ef..9c4bb28 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -5132,17 +5132,25 @@ things without first using the debugger to find the facts.
@cindex configuring _GDBN__
@cindex installation
-The script @samp{config.gdb} automates the process of preparing _GDBN__ for
-installation; you can then use @samp{make} to actually build it. For
-example,
+The script @samp{config.gdb} automates the process of preparing _GDBN__
+for installation; you can then use @samp{make} to actually build it.
+The best way to build GDB is in a subdirectory that records the
+configuration options used; this gives you a clean way of building
+_GDBN__ binaries with several different configuration options.
+@samp{config.gdb} doesn't depend on this---it's just a good habit. For
+example, assuming the _GDBN__ source is in a directory called
+``@code{gdb-4.0}'':
@example
-config.gdb sun3os4
+cd gdb-4.0
+mkdir =sun3os4
+cd =sun3os4
+../config.gdb sun3os4
make
@end example
@noindent
-is all that's required to install _GDBN__ on a Sun 3 running SunOS 4.
+will install _GDBN__ on a Sun 3 running SunOS 4.
@table @code
@kindex config.gdb