lisp/window.el (frame-auto-delete, window-deletable-p): Doc fix.

[bpt/emacs.git] / INSTALL.BZR

diff --git a/INSTALL.BZR b/INSTALL.BZR
index dafd0b8..664aab1 100644 (file)
--- a/INSTALL.BZR
+++ b/INSTALL.BZR
@@ -1,12 +1,30 @@
-Copyright (C) 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010
-  Free Software Foundation, Inc.
+Copyright (C) 2002-2011  Free Software Foundation, Inc.

 See the end of the file for license conditions.
 
 
              Building and Installing Emacs from Bazaar
 
 See the end of the file for license conditions.
 
 
              Building and Installing Emacs from Bazaar
 

-If this is the first time you go through it, you'll need to configure
-before bootstrapping:
+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.
+makeinfo  - not strictly necessary, but highly recommended, so that
+  you can build the manuals.
+
+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 and some related files:
+
+  $ ./autogen.sh
+
+(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
 
 
   $ ./configure
 


@@ -50,10 +68,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
 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.

 
 
 \f
 
 
 \f