X-Git-Url: http://git.hcoop.net/bpt/emacs.git/blobdiff_plain/8bb25908552b44a425beb91d3035b1c091d2d6f2..3290526dde9b633b7a032de36fd961347f1bfe88:/INSTALL.BZR diff --git a/INSTALL.BZR b/INSTALL.BZR index 2ff6ca8c4a..93e53fd09a 100644 --- a/INSTALL.BZR +++ b/INSTALL.BZR @@ -1,20 +1,42 @@ -Copyright (C) 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009 - Free Software Foundation, Inc. +Copyright (C) 2002-2012 Free Software Foundation, Inc. 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 +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": - $ cvs update -dP + $ bzr pull $ make bootstrap Normally, it is not necessary to use "make bootstrap" after every @@ -31,13 +53,9 @@ generated files, such as esh-groups.el, and *-loaddefs.el in some subdirectories of lisp/, e.g. mh-e/ and calendar/) will need to be updated to reflect new autoloaded functions. If you see errors (rather than warnings) about undefined lisp functions during compilation, that -may be the reason. Another symptom may be an error saying that -"loaddefs.el" could not be found; this is due to a change in the way -loaddefs.el was handled in version control, and should only happen -once, for users that are updating old sources. Finally, sometimes -there can be build failures related to *loaddefs.el (e.g. "required -feature `esh-groups' was not provided"). In that case, follow the -instructions below. +may be the reason. Finally, sometimes there can be build failures +related to *loaddefs.el (e.g. "required feature `esh-groups' was not +provided"). In that case, follow the instructions below. To update loaddefs.el (and similar files), do: @@ -53,25 +71,13 @@ platform-specific configuration scripts (nt/configure.bat, config.bat, etc.) before "make bootstrap" or "make"; the rest of the procedure is applicable to those systems as well. -Questions, requests, and bug reports about the Bazaar versions of Emacs -should be sent to emacs-pretest-bug@gnu.org rather than gnu.emacs.help -or gnu.emacs.bug. Ideally, use M-x report-emacs-bug RET which will -send it to the proper place. - 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. - - -Note on accessing the Bazaar repository ---------------------------------------- - -Write access to the Bazaar repository is currently done via Bazaar's -sftp:// protocol; see http://www.emacswiki.org/emacs/BzrForEmacsDevs. -We plan to offer bzr+ssh:// access later. More discussion about that -is at https://savannah.gnu.org/support/?107077. +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.