2000-12-22 Fernando Nasser <fnasser@redhat.com>

        * README: Suggest building in an empty directory.

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 99aeb486750818423e22846513373aa383dc8b28..21f60fed44fb16bee4a55e750db3c5f9ed43c0a3 100644 (file)
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,7 @@
+2000-12-22  Fernando Nasser  <fnasser@redhat.com>
+
+       * README: Suggest building in an empty directory.
+
 2000-12-21  Mark Kettenis  <kettenis@gnu.org>
 
        * i386-tdep.c: Add missing ')' in comment.

diff --git a/gdb/README b/gdb/README
index cd8c6c2da67ebb754ec02dc91de79659e881a3cb..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.)