* exec.c (xfer_memory): Add attrib argument.

[deliverable/binutils-gdb.git] / gdb / README

diff --git a/gdb/README b/gdb/README
index 801ad3fb12b6b892e89e8d5a18db4a21d112bbdd..c718b6f5b290ae383eee8e2b7d79031afb1d7385 100644 (file)
--- a/gdb/README
+++ b/gdb/README
@@ -35,13 +35,26 @@ called `gdb-5.0', which contains:
   config-ml.in  gdb           missing        mpw-install
   config.guess  include       mkinstalldirs  opcodes
 
-To build GDB, you can just do:
+You can build GDB right in the source directory:
 
        cd gdb-5.0
        ./configure
        make
        cp gdb/gdb /usr/local/bin/gdb   (or wherever you want)
 
+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 
+configuration options.
+
+You can build GDB in any empty build directory:
+
+     
+     mkdir build
+     cd build
+     <full path to your sources>/gdb-5.0/configure
+     make
+
 (Building GDB with DJGPP tools for MS-DOS/MS-Windows is slightly
 different; see the file gdb-5.0/gdb/config/djgpp/README for details.)
 
@@ -415,8 +428,7 @@ See the GDB manual (gdb/doc/gdb.texinfo) for information on this.
 Kernel debugging
 =================
 
-   I have't done this myself so I can't really offer any advice.
-Remote debugging over serial lines works fine, but the kernel
+   Remote debugging over serial lines works fine, but the kernel
 debugging code in here has not been tested in years.  Van Jacobson has
 better kernel debugging, but the UC lawyers won't let FSF have it.