INSTALL.CVS

   1 Copyright (C) 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009
   2   Free Software Foundation, Inc.
   3 See the end of the file for license conditions.
   4
   5
   6               Building and Installing Emacs from CVS
   7
   8 If this is the first time you go through it, you'll need to configure
   9 before bootstrapping:
  10
  11   $ ./configure
  12
  13 Some of the files that are included in the Emacs tarball, such as
  14 byte-compiled Lisp files, are not stored in the CVS repository.
  15 Therefore, to build from CVS you must run "make bootstrap"
  16 instead of just "make":
  17
  18   $ cvs update -dP
  19   $ make bootstrap
  20
  21 Normally, it is not necessary to use "make bootstrap" after every CVS
  22 update.  "make" should work in 90% of the cases and be much quicker.
  23
  24   $ make
  25
  26 (If you want to install the Emacs binary, type "make install" instead
  27 of "make" in the last command.)
  28
  29 Occasionally the file "lisp/loaddefs.el" (and similar automatically
  30 generated files, such as esh-groups.el, and *-loaddefs.el in some
  31 subdirectories of lisp/, e.g. mh-e/ and calendar/) will need to be
  32 updated to reflect new autoloaded functions.  If you see errors (rather
  33 than warnings) about undefined lisp functions during compilation, that
  34 may be the reason.  Another symptom may be an error saying that
  35 "loaddefs.el" could not be found; this is due to a change in the way
  36 loaddefs.el was handled in CVS, and should only happen once, for users
  37 that are updating old CVS trees.  Finally, sometimes there can be build
  38 failures related to *loaddefs.el (e.g. "required feature `esh-groups'
  39 was not provided").  In that case, follow the instructions below.
  40
  41 To update loaddefs.el (and similar files), do:
  42
  43   $ cd lisp
  44   $ make autoloads
  45
  46 If either of the above partial procedures fails, try "make bootstrap".
  47 If CPU time is not an issue, the most thorough way to rebuild, and
  48 avoid any spurious problems, is always to use this method.
  49
  50 Users of non-Posix systems (MS-Windows etc.) should run the
  51 platform-specific configuration scripts (nt/configure.bat, config.bat,
  52 etc.) before "make bootstrap" or "make"; the rest of the procedure is
  53 applicable to those systems as well.
  54
  55 Questions, requests, and bug reports about the CVS versions of Emacs
  56 should be sent to emacs-pretest-bug@gnu.org rather than gnu.emacs.help
  57 or gnu.emacs.bug.  Ideally, use M-x report-emacs-bug RET which will
  58 send it to the proper place.
  59
  60 Because the CVS version of Emacs is a work in progress, it will
  61 sometimes fail to build.  Please wait a day or so (and check the bug
  62 and development mailing list archives) before reporting such problems.
  63 In most cases, the problem is known about and is just waiting for
  64 someone to fix it.
  65
  66
  67 Note on using SSH to access the CVS repository from inside Emacs
  68 ----------------------------------------------------------------
  69
  70 Write access to the CVS repository requires using SSH v2.
  71
  72 If you execute cvs commands inside Emacs, specifically if you use
  73 pcl-cvs, output from CVS may be lost due to a problem in the
  74 interface between ssh, cvs, and libc.  Corrupted checkins are
  75 also known to have happened.
  76
  77 To fix the problem, save the following script into a file, make it
  78 executable, and set CVS_RSH to the file name of the script:
  79
  80 #!/bin/bash
  81 exec 2> >(exec cat >&2 2>/dev/null)
  82 exec ssh "$@"
  83
  84 This may be combined with the following entry in ~/.ssh/config to
  85 simplify accessing the CVS repository:
  86
  87 Host subversions.gnu.org
  88      Protocol 2
  89      ForwardX11 no
  90      User YOUR_USERID
  91
  92 \f
  93 This file is part of GNU Emacs.
  94
  95 GNU Emacs is free software: you can redistribute it and/or modify
  96 it under the terms of the GNU General Public License as published by
  97 the Free Software Foundation, either version 3 of the License, or
  98 (at your option) any later version.
  99
 100 GNU Emacs is distributed in the hope that it will be useful,
 101 but WITHOUT ANY WARRANTY; without even the implied warranty of
 102 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 103 GNU General Public License for more details.
 104
 105 You should have received a copy of the GNU General Public License
 106 along with GNU Emacs.  If not, see <http://www.gnu.org/licenses/>.