X-Git-Url: https://code.delx.au/gnu-emacs/blobdiff_plain/6e5fa6bfce1362c2ebf049fcfa1e6f2a4762ccef..7a91562ff0ea0033add100295a52ded5a8be0d9b:/INSTALL.BZR

diff --git a/INSTALL.BZR b/INSTALL.BZR
index 3859e3cd4f..4b6797ebc9 100644
--- a/INSTALL.BZR
+++ b/INSTALL.BZR
@@ -1,4 +1,4 @@
-Copyright (C) 2002-2011  Free Software Foundation, Inc.
+Copyright (C) 2002-2013 Free Software Foundation, Inc.
 See the end of the file for license conditions.
 
 
@@ -8,8 +8,9 @@ Building Emacs from Bazaar requires some tools that are not needed
 when building from a release.  You will need:
 
 autoconf  - at least the version specified near the start of
-  configure.in (in the AC_PREREQ command).
-automake  - we recommend at least version 1.11.
+  configure.ac (in the AC_PREREQ command).
+automake  - at least the version specified near the start of
+  configure.ac (in the AM_INIT_AUTOMAKE command).
 makeinfo  - not strictly necessary, but highly recommended, so that
   you can build the manuals.
 
@@ -17,17 +18,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" 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 +73,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.