-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.
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.
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
$ ./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":
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