X-Git-Url: https://git.hcoop.net/bpt/emacs.git/blobdiff_plain/cafdcef32d55cbb44389d7e322e7f973cbb72dfd..acaf905b1130aae80fa59d2c861ffd4c8eb75486:/INSTALL.BZR

diff --git a/INSTALL.BZR b/INSTALL.BZR
index 3859e3cd4f..93e53fd09a 100644
--- a/INSTALL.BZR
+++ b/INSTALL.BZR
@@ -1,4 +1,4 @@
-Copyright (C) 2002-2011  Free Software Foundation, Inc.
+Copyright (C) 2002-2012  Free Software Foundation, Inc.
 See the end of the file for license conditions.
 
 
@@ -17,17 +17,21 @@ The `autogen.sh' script can help you figure out if you have the
 necessary tools.
 
 The first time you build, there are a couple of extra steps.
-First, generate the `configure' script:
+First, generate the `configure' script and some related files:
 
   $ ./autogen.sh
 
-(or you can just run `autoreconf -I m4').
+(or you can just run `autoreconf -i -I m4').
 
 You can then configure your build (use `./configure --help' to see
 options you can set):
 
   $ ./configure
 
+If you want later builds to go faster, at the expense of sometimes
+doing the wrong thing if you update the build procedure, you can
+invoke "./configure -C --disable-maintainer-mode" instead.
+
 Some of the files that are included in the Emacs tarball, such as
 byte-compiled Lisp files, are not stored in Bazaar.  Therefore, to
 build from Bazaar you must run "make bootstrap" instead of just "make":
@@ -68,10 +72,12 @@ etc.) before "make bootstrap" or "make"; the rest of the procedure is
 applicable to those systems as well.
 
 Because the Bazaar version of Emacs is a work in progress, it will
-sometimes fail to build.  Please wait a day or so (and check the bug
-and development mailing list archives) before reporting such problems.
-In most cases, the problem is known about and is just waiting for
-someone to fix it.
+sometimes fail to build.  Please wait a day or so (and check the
+archives of the emacs-buildstatus, emacs-devel, and bug-gnu-emacs
+mailing lists) before reporting such problems.  In most cases, the
+problem is known about and is just waiting for someone to fix it.
+This is especially true for Lisp compilation errors, which are almost
+never platform-specific.