日志更新记录：

[1] 增加 CentOS7.2 （内核版本：3.10.0-514.16.1.el7.x86_64）下 的安装过程，它与本文的步骤完全一样。

 

Emacs 版本：http://mirror.bjtu.edu.cn/gnu/emacs/emacs-24.5.tar.gz

CentOS 内核版本：2.6.32-573.el6.x86_64

参考资料：

[1] http://blog.itpub.net/7719012/viewspace-1163875/

[2] http://www.tuicool.com/articles/umAVzm

[3] /[Your Emacs Directory]/emacs-24.5/INSTALL

 

源码安装 Emacs 24.5 的步骤如下:

1 安装需要的软件

$ su yum -y groupinstall "Development Tools"yum -y install gtk+-devel gtk2-develyum -y install libXpm-develyum -y install libpng-develyum -y install giflib-develyum -y install libtiff-devel libjpeg-develyum -y install ncurses-develyum -y install gpm-devel dbus-devel dbus-glib-devel dbus-pythonyum -y install GConf2-devel pkgconfig yum -y install gnutls-devel

 

2 安装Emacs 24.5

tar xvf emacs-24.5.tar.gzcd emacs-24.5sudo ./configure --prefix=/usr/local --with-x-toolkit=gtk --without-gsettingssudo make src/emacs -Q    # 用来测试Emacs是否正常。如果能显示Emacs样例程序，则表示一切正常。sudo make install sudo make clean # 用来清除make产生的中间文件，释放空间（强迫症患者的必要步骤）

 

3 卸载 Emacs 24.5 

很简单，跳转到安装时的目录下，用一句命令即可：

tar xvf emacs-24.5.tar.gz cd emacs-24.5 sudo ./configure --prefix=/usr/local --with-x-toolkit=gtk --without-gsettings sudo make sudo make uninstall # 用来卸载Emacs。之前安装时的命令为 install

如果安装前的编译文件被删除了，则重复一遍解压及编译命令即可。

 

附原版安装指南

/[Your Emacs Directory]/emacs-24.5/INSTALL

GNU Emacs Installation GuideCopyright (C) 1992, 1994, 1996-1997, 2000-2015 Free Software Foundation,Inc.See the end of the file for license conditions.This file contains general information on building GNU Emacs.For more information specific to the MS-Windows, GNUstep/Mac OS X, andMS-DOS ports, also read the files nt/INSTALL, nextstep/INSTALL, andmsdos/INSTALL.  For information about building from a repository checkout(rather than a release), also read the file INSTALL.REPO.BASIC INSTALLATIONOn most Unix systems, you build Emacs by first running the `configure'shell script.  This attempts to deduce the correct values forvarious system-dependent variables and features, and find thedirectories where certain system headers and libraries are kept.In a few cases, you may need to explicitly tell configure where tofind some things, or what options to use.`configure' creates a `Makefile' in several subdirectories, and a`src/config.h' file containing system-dependent definitions.Running the `make' utility then builds the package for your system.Here's the procedure to build Emacs using `configure' on systems whichare supported by it.  In some cases, if the simplified procedure fails,you might need to use various non-default options, and maybe performsome of the steps manually.  The more detailed description in the othersections of this guide will help you do that, so please refer to thosesections if you need to.  1. Unpacking the Emacs 24 release requires about 200 MB of free  disk space.  Building Emacs uses about another 200 MB of space.  The final installed Emacs uses about 150 MB of disk space.  This includes the space-saving that comes from automatically  compressing the Lisp source files on installation.  2a. `cd' to the directory where you unpacked Emacs and invoke the      `configure' script:		 ./configure  2b. Alternatively, create a separate directory, outside the source      directory, where you want to build Emacs, and invoke `configure'      from there:		 SOURCE-DIR/configure      where SOURCE-DIR is the top-level Emacs source directory.      This may not work unless you use GNU make.  3. When `configure' finishes, it prints several lines of details     about the system configuration.  Read those details carefully     looking for anything suspicious, such as wrong CPU and operating     system names, wrong places for headers or libraries, missing     libraries that you know are installed on your system, etc.     If you find anything wrong, you may have to pass to `configure'     one or more options specifying the explicit machine configuration     name, where to find various headers and libraries, etc.     Refer to the section DETAILED BUILDING AND INSTALLATION below.     If `configure' didn't find some image support libraries, such as     Xpm and jpeg, refer to "Image support libraries" below.     If the details printed by `configure' don't make any sense to     you, but there are no obvious errors, assume that `configure' did     its job and proceed.  4. Invoke the `make' program:		 make  5. If `make' succeeds, it will build an executable program `emacs'     in the `src' directory.  You can try this program, to make sure     it works:		 src/emacs -Q  6. Assuming that the program `src/emacs' starts and displays its     opening screen, you can install the program and its auxiliary     files into their installation directories:		 make install  You are now ready to use Emacs.  If you wish to conserve disk space,  you may remove the program binaries and object files from the  directory where you built Emacs:		 make clean  You can delete the entire build directory if you do not plan to  build Emacs again, but it can be useful to keep for debugging.  If you want to build Emacs again with different configure options,  first clean the source directories:		make distclean  Note that the install automatically saves space by compressing  (provided you have the `gzip' program) those installed Lisp source (.el)  files that have corresponding .elc versions, as well as the Info files.ADDITIONAL DISTRIBUTION FILES* Complex Text Layout support librariesOn GNU and Unix systems, Emacs needs the optional libraries "m17n-db","libm17n-flt", "libotf" to correctly display such complex scripts asIndic and Khmer, and also for scripts that require Arabic shapingsupport (Arabic and Farsi).  On some systems, particularly GNU/Linux,these libraries may be already present or available as additionalpackages.  Note that if there is a separate `dev' or `devel' package,for use at compilation time rather than run time, you will need thatas well as the corresponding run time package; typically the devpackage will contain header files and a library archive.  Otherwise,you can download the libraries from 
     .Note that Emacs cannot support complex scripts on a TTY, unless theterminal includes such a support.* intlfonts-VERSION.tar.gzThe intlfonts distribution contains X11 fonts in various encodingsthat Emacs can use to display international characters.  If you see anon-ASCII character appear as a hollow box, that means you don't havea font for it.  You might find one in the intlfonts distribution.  Ifyou do have a font for a non-ASCII character, but some charactersdon't look right, or appear improperly aligned, a font from theintlfonts distribution might look better.The fonts in the intlfonts distribution are also used by the ps-printpackage for printing international characters.  The filelisp/ps-mule.el defines the *.bdf font files required for printingeach character set.The intlfonts distribution contains its own installation instructions,in the intlfonts/README file.* Image support librariesEmacs needs libraries to display images, with the exception of PBM andXBM images whose support is built-in.On some systems, particularly on GNU/Linux, these libraries mayalready be present or available as additional packages.  Ifthere is a separate `dev' or `devel' package, for use at compilationtime rather than run time, you will need that as well as thecorresponding run time package; typically the dev package willcontain header files and a library archive.  Otherwise, you candownload and build libraries from sources.  Although none of them areessential for running Emacs, some are important enough that'configure' will report an error if they are absent from a system thathas X11 support, unless 'configure' is specifically told to omit them.Here's a list of some of these libraries, and the URLs where theycan be found (in the unlikely event that your distribution does notprovide them).  By default, libraries marked with an X are required ifX11 is being used.    libXaw3d          http://directory.fsf.org/project/xaw3d/  X libxpm for XPM:   http://www.x.org/releases/current/src/lib/  X libpng for PNG:   http://www.libpng.org/    libz (for PNG):   http://www.zlib.net/  X libjpeg for JPEG: http://www.ijg.org/  X libtiff for TIFF: http://www.remotesensing.org/libtiff/  X libgif for GIF:   http://sourceforge.net/projects/giflib/If you supply the appropriate --without-LIB option, 'configure' willomit the corresponding library from Emacs, even if that makes for aless-pleasant user interface.  Otherwise, Emacs will configure itselfto build with these libraries if 'configure' finds them on yoursystem, and 'configure' will complain and exit if a library marked 'X'is not found on a system that uses X11.  Use --without-LIB if yourversion of a library won't work because some routines are missing.* Extra fontsThe Emacs distribution does not include fonts and does not installthem.On the GNU system, Emacs supports both X fonts and local fonts(i.e. fonts managed by the fontconfig library).  If you need morefonts than your distribution normally provides, you must install themyourself.  See 
      for a largenumber of free Unicode fonts.* GNU/Linux development packagesMany GNU/Linux systems do not come with development packages by default;they include the files that you need to run Emacs, but not those youneed to compile it.  For example, to compile Emacs with support for Xand graphics libraries, you may need to install the `X development'package(s), and development versions of the jpeg, png, etc. packages.The names of the packages that you need varies according to theGNU/Linux distribution that you use, and the options that you want toconfigure Emacs with.  On Debian-based systems, you can install all thepackages needed to build the installed version of Emacs with a commandlike `apt-get build-dep emacs24'.  On Red Hat systems, thecorresponding command is `yum-builddep emacs'.DETAILED BUILDING AND INSTALLATION:(This is for a Unix or Unix-like system.  For MS-DOS and MS Windows 3.X,see msdos/INSTALL.  For later versions of MS Windows, see the filent/INSTALL.  For GNUstep and Mac OS X, see nextstep/INSTALL.)1) See the basic installation summary above for the disk space requirements.2) In the unlikely event that `configure' does not detect your systemtype correctly, consult `./etc/MACHINES' to see what --host, --buildoptions you should pass to `configure'.  That file also offers hintsfor getting around some possible installation problems.3) You can build Emacs in the top-level Emacs source directoryor in a separate directory.3a) To build in the top-level Emacs source directory, go to thatdirectory and run the program `configure' as follows:    ./configure [--OPTION[=VALUE]] ...If `configure' cannot determine your system type, try againspecifying the proper --build, --host options explicitly.If you don't want X support, specify `--with-x=no'.  If you omit thisoption, `configure' will try to figure out for itself whether yoursystem has X, and arrange to use it if present.The `--x-includes=DIR' and `--x-libraries=DIR' options tell the buildprocess where the compiler should look for the include files andobject libraries used with the X Window System.  Normally, `configure'is able to find them; these options are necessary if you have your XWindow System files installed in unusual places.  These options alsoaccept a list of directories, separated with colons.To get more attractive menus, you can specify an X toolkit when youconfigure Emacs; use the option `--with-x-toolkit=TOOLKIT', whereTOOLKIT is `gtk' (the default), `athena', or `motif' (`yes' and`lucid' are synonyms for `athena').  Compiling with Motif causes astandard File Selection Dialog to pop up when you invoke file commandswith the mouse.  You can get fancy 3D-style scroll bars, even withoutGtk or Motif, if you have the Xaw3d library installed (see"Image support libraries" above for Xaw3d availability).You can tell configure where to search for GTK by specifying`--with-pkg-config-prog=PATH' where PATH is the pathname topkg-config.Emacs will autolaunch a D-Bus session bus, when the environmentvariable DISPLAY is set, but no session bus is running.  This might beinconvenient for Emacs when running as daemon or running via a remotessh connection.  In order to completely prevent the use of D-Bus, configureEmacs with the options `--without-dbus --without-gconf --without-gsettings'.The Emacs mail reader RMAIL is configured to be able to read mail froma POP3 server by default.  Versions of the POP protocol older thanPOP3 are not supported.  For Kerberos-authenticated POP add`--with-kerberos', for Hesiod support add `--with-hesiod'.  While POP3is always enabled, whether Emacs actually uses POP is controlled byindividual users--see the Rmail chapter of the Emacs manual.For image support you may have to download, build, and install theappropriate image support libraries for image types other than XBM andPBM, see the list of URLs in "Image support libraries" above.(Note that PNG support requires libz in addition to libpng.)To disable individual types of image support in Emacs for some reason,even though configure finds the libraries, you can configure with oneor more of these options:  --without-xpm        for XPM image support  --without-jpeg       for JPEG image support  --without-tiff       for TIFF image support  --without-gif        for GIF image support  --without-png        for PNG image supportUse --without-toolkit-scroll-bars to disable Motif or Xaw3d scroll bars.Use --without-xim to inhibit the default use of X Input Methods.In this case, the X resource useXIM can be used to turn on use of XIM.Use --disable-largefile to omit support for files larger than 2GB onsystems which support that.Use --without-sound to disable sound support.Use --without-all if you want to build a small executable with the minimaldependencies on external libraries, at the cost of disabling most of thefeatures that are normally enabled by default.  Using --without-all isequivalent to --without-sound --without-dbus --without-libotf--without-selinux --without-xft --without-gsettings --without-gnutls--without-rsvg --without-xml2 --without-gconf --without-imagemagick--without-m17n-flt --without-jpeg --without-tiff --without-gif--without-png --without-gpm --without-file-notification.  Note that--without-all leaves X support enabled, and using the GTK2 or GTK3toolkit creates a lot of library dependencies.  So if you want tobuild a small executable with very basic X support, use --without-all--with-x-toolkit=no.  For the smallest possible executable without X,use --without-all --without-x.  If you want to build with just a fewfeatures enabled, you can combine --without-all with --with-FEATURE.For example, you can use --without-all --with-dbus to build with DBussupport and nothing more.Use --with-wide-int to implement Emacs values with the type 'long long',even on hosts where a narrower type would do.  With this option, on atypical 32-bit host, Emacs integers have 62 bits instead of 30.Use --enable-gcc-warnings to enable compile-time checks that warnabout possibly-questionable C code.  This is intended for developersand is useful with GNU-compatible compilers.  On a recent GNU systemthere should be no warnings; on older and on non-GNU systems thegenerated warnings may still be useful.Use --enable-link-time-optimization to enable link-time optimizer, whichis available in GNU compiler since version 4.5.0.  If your compiler is notGNU or older than version 4.5.0, this option does nothing.  If `configure'can determine number of online CPUS on your system, final link-timeoptimization and code generation is executed in parallel using one jobper each available online CPU.The `--prefix=PREFIXDIR' option specifies where the installation processshould put emacs and its data files.  This defaults to `/usr/local'.- Emacs (and the other utilities users run) go in PREFIXDIR/bin  (unless the `--exec-prefix' option says otherwise).- The architecture-independent files go in PREFIXDIR/share/emacs/VERSION  (where VERSION is the version number of Emacs, like `23.2').- The architecture-dependent files go in  PREFIXDIR/libexec/emacs/VERSION/CONFIGURATION  (where CONFIGURATION is the configuration name, like  i686-pc-linux-gnu), unless the `--exec-prefix' option says otherwise.The `--exec-prefix=EXECDIR' option allows you to specify a separateportion of the directory tree for installing architecture-specificfiles, like executables and utility programs.  If specified,- Emacs (and the other utilities users run) go in EXECDIR/bin, and- The architecture-dependent files go in  EXECDIR/libexec/emacs/VERSION/CONFIGURATION.EXECDIR/bin should be a directory that is normally in users' PATHs.For example, the command    ./configure --build=i386-linux-gnu --without-soundconfigures Emacs to build for a 32-bit GNU/Linux distribution,without sound support.`configure' doesn't do any compilation or installation itself.It just creates the files that influence those things:`./Makefile' in the top-level directory and several subdirectories;and `./src/config.h'.  For details on exactly what it does, see thesection called `CONFIGURATION BY HAND', below.When it is done, `configure' prints a description of what it did andcreates a shell script `config.status' which, when run, recreates thesame configuration.  If `configure' exits with an error afterdisturbing the status quo, it removes `config.status'.  `configure'also creates a file `config.cache' that saves the results of its teststo make reconfiguring faster, and a file `config.log' containing compileroutput (useful mainly for debugging `configure').  You can give`configure' the option `--cache-file=FILE' to use the results of thetests in FILE instead of `config.cache'.  Set FILE to `/dev/null' todisable caching, for debugging `configure'.If the description of the system configuration printed by `configure'is not right, or if it claims some of the features or libraries are notavailable when you know they are, look at the `config.log' file forthe trace of the failed tests performed by `configure' to checkwhether these features are supported.  Typically, some test failsbecause the compiler cannot find some function in the systemlibraries, or some macro-processor definition in the system headers.Some tests might fail because the compiler should look in specialdirectories for some header files, or link against optionallibraries, or use special compilation options.  You can force`configure' and the build process which follows it to do that bysetting the variables CPPFLAGS, CFLAGS, LDFLAGS, LIBS, CPP and CCbefore running `configure'.  CPP is the command which invokes thepreprocessor, CPPFLAGS lists the options passed to it, CFLAGS arecompilation options, LDFLAGS are options used when linking, LIBS arelibraries to link against, and CC is the command which invokes thecompiler.  By default, gcc is used if available.Here's an example of a `configure' invocation, assuming a Bourne-likeshell such as Bash, which uses these variables: CPPFLAGS='-I/foo/myinclude' LDFLAGS='-L/bar/mylib' \  CFLAGS='-O3' LIBS='-lfoo -lbar' ./configure(this is all one long line).  This tells `configure' to instruct thepreprocessor to look in the `/foo/myinclude' directory for headerfiles (in addition to the standard directories), instruct the linkerto look in `/bar/mylib' for libraries, pass the -O3 optimizationswitch to the compiler, and link against libfoo and libbarlibraries in addition to the standard ones.For some libraries, like Gtk+, fontconfig and ALSA, `configure' usespkg-config to find where those libraries are installed.If you want pkg-config to look in special directories, you have to setthe environment variable PKG_CONFIG_PATH to point to the directorieswhere the .pc-files for those libraries are.For example: PKG_CONFIG_PATH='/usr/local/alsa/lib/pkgconfig:/opt/gtk+-2.8/lib/pkgconfig' \   ./configureThe work of `configure' can be done by editing various files in thedistribution, but using `configure' is easier.  See the section called"CONFIGURATION BY HAND" below if you want to do the configurationyourself.3b) To build in a separate directory, go to that directoryand run the program `configure' as follows:    SOURCE-DIR/configure CONFIGURATION-NAME [--OPTION[=VALUE]] ...SOURCE-DIR refers to the top-level Emacs source directory which iswhere Emacs's configure script is located.  `configure' looks for theEmacs source code in the directory that `configure' is in.To build in a separate directory, you must use a version of `make'that supports the `VPATH' variable, such as GNU `make'.(Do not try to build in a separate directory by creating many linksto the real source directory--there is no need, and installation willfail.)4) Put into `./lisp/site-init.el' or `./lisp/site-load.el' any EmacsLisp code you want Emacs to load before it is dumped out.  Usesite-load.el for additional libraries if you arrange for theirdocumentation strings to be in the etc/DOC file (seesrc/Makefile.in if you wish to figure out how to do that).  For allelse, use site-init.el.  Do not load byte-compiled code whichwas built with a non-nil value of `byte-compile-dynamic'.It is not a good idea to edit the normal .el files that come with Emacs.Instead, use a file like site-init.el to change settings.To change the value of a variable that is already defined in Emacs,you should use the Lisp function `setq', not `defvar'.  For example,     (setq news-inews-program "/usr/bin/inews")is how you would override the default value of the variablenews-inews-program.Before you override a variable this way, *look at the value* that thevariable gets by default!  Make sure you know what kind of value thevariable should have.  If you don't pay attention to what you aredoing, you'll make a mistake.The `site-*.el' files are nonexistent in the distribution.  You do notneed to create them if you have nothing to put in them.5) Refer to the file `./etc/TERMS' for information on fields you maywish to add to various termcap entries.  (This is unlikely to be necessary.)6) Run `make' in the top directory of the Emacs distribution to finishbuilding Emacs in the standard way.  The final executable file isnamed `src/emacs'.  You can execute this file "in place" withoutcopying it, if you wish; then it automatically uses the siblingdirectories ../lisp, ../lib-src, ../info.Or you can "install" the executable and the other files into theirinstalled locations, with `make install'.  By default, Emacs's filesare installed in the following directories:`/usr/local/bin' holds the executable programs users normally run -		`emacs', `etags', `ctags', `emacsclient', and		`grep-changelog'.`/usr/local/share/emacs/VERSION/lisp' holds the Emacs Lisp library;		`VERSION' stands for the number of the Emacs version		you are installing, like `23.1' or `23.2'.  Since the		Lisp library changes from one version of Emacs to		another, including the version number in the path		allows you to have several versions of Emacs installed		at the same time; in particular, you don't have to		make Emacs unavailable while installing a new version.`/usr/local/share/emacs/VERSION/etc' holds the Emacs tutorial, the DOC		file, and other architecture-independent files Emacs		might need while running.`/usr/local/libexec/emacs/VERSION/CONFIGURATION-NAME' contains executable		programs used by Emacs that users are not expected to		run themselves.		`VERSION' is the number of the Emacs version you are		installing, and `CONFIGURATION-NAME' is the value		deduced by the `configure' program to identify the		architecture and operating system of your machine,		like `i686-pc-linux-gnu' or `sparc-sun-sunos'.  Since		these files are specific to the version of Emacs,		operating system, and architecture in use, including		the configuration name in the path allows you to have		several versions of Emacs for any mix of machines and		operating systems installed at the same time; this is		useful for sites at which different kinds of machines		share the file system Emacs is installed on.`/usr/local/share/info' holds the on-line documentation for Emacs,		known as "info files".  Many other GNU programs are		documented using info files as well, so this directory		stands apart from the other, Emacs-specific directories.`/usr/local/share/man/man1' holds the man pages for the programs installed		in `/usr/local/bin'.Any version of Emacs, whether installed or not, also looks for Lispfiles in these directories.`/usr/local/share/emacs/VERSION/site-lisp' holds the local Emacs Lisp		files installed for Emacs version VERSION only.`/usr/local/share/emacs/site-lisp' holds the local Emacs Lisp		files installed for all Emacs versions.		When Emacs is installed, it searches for its Lisp files		in `/usr/local/share/emacs/VERSION/site-lisp', then in		`/usr/local/share/emacs/site-lisp', and finally in		`/usr/local/share/emacs/VERSION/lisp'.If these directories are not what you want, you can specify where toinstall Emacs's libraries and data files or where Emacs should searchfor its Lisp files by giving values for `make' variables as part ofthe command.  See the section below called `MAKE VARIABLES' for moreinformation on this.7) Check the file `dir' in your site's info directory (usually/usr/local/share/info) to make sure that it has a menu entry for theEmacs info files.8) If your system uses lock files to interlock access to mailer inbox files,then you might need to make the movemail program setuid or setgidto enable it to write the lock files.  We believe this is safe.9) You are done!  You can remove executables and object files fromthe build directory by typing `make clean'.  To also remove the filesthat `configure' created (so you can compile Emacs for a differentconfiguration), type `make distclean'.  If you don't need some, or allof the input methods from the Leim package, you can remove theunneeded files in the leim subdirectories of your site's lispdirectory (usually /usr/local/share/emacs/VERSION/).MAKE VARIABLESYou can change where the build process installs Emacs and its datafiles by specifying values for `make' variables as part of the `make'command line.  For example, if you type    make install bindir=/usr/local/gnubinthe `bindir=/usr/local/gnubin' argument indicates that the Emacsexecutable files should go in `/usr/local/gnubin', not`/usr/local/bin'.Here is a complete list of the variables you may want to set.`bindir' indicates where to put executable programs that users can	run.  This defaults to /usr/local/bin.`datadir' indicates where to put the architecture-independent	read-only data files that Emacs refers to while it runs; it	defaults to /usr/local/share.  We create the following	subdirectories under `datadir':	- `emacs/VERSION/lisp', containing the Emacs Lisp library, and	- `emacs/VERSION/etc', containing the tutorials, DOC file, etc.	`VERSION' is the number of the Emacs version you are installing,	like `23.1' or `23.2'.  Since these files vary from one version	of Emacs to another, including the version number in the path	allows you to have several versions of Emacs installed at the	same time; this means that you don't have to make Emacs	unavailable while installing a new version.`libexecdir' indicates where to put architecture-specific data files that	Emacs refers to as it runs; it defaults to `/usr/local/libexec'.	We create the following subdirectories under `libexecdir':	- `emacs/VERSION/CONFIGURATION-NAME', containing executable		programs used by Emacs that users are not expected to run		themselves.	`VERSION' is the number of the Emacs version you are installing,	and `CONFIGURATION-NAME' is the value deduced by the	`configure' program to identify the architecture and operating	system of your machine, like `i686-pc-linux-gnu' or `sparc-sun-sunos'.	Since these files are specific to the version of Emacs,	operating system, and architecture in use, including the	configuration name in the path allows you to have several	versions of Emacs for any mix of machines and operating	systems installed at the same time; this is useful for sites	at which different kinds of machines share the file system	Emacs is installed on.`infodir' indicates where to put the info files distributed with	Emacs; it defaults to `/usr/local/share/info'.`mandir' indicates where to put the man pages for Emacs and its	utilities (like `etags'); it defaults to	`/usr/local/share/man/man1'.`prefix' doesn't give a path for any specific part of Emacs; instead,	its value is used to determine the defaults for all the	architecture-independent path variables - `datadir',	`sharedstatedir', `infodir', and `mandir'.  Its default value is	`/usr/local'; the other variables add on `lib' or `man' to it	by default.	For example, suppose your site generally places GNU software	under `/usr/users/software/gnusoft' instead of `/usr/local'.	By including	    `prefix=/usr/users/software/gnusoft'	in the arguments to `make', you can instruct the build process	to place all of the Emacs data files in the appropriate	directories under that path.`exec_prefix' serves the same purpose as `prefix', but instead	determines the default values for the architecture-dependent	path variables - `bindir' and `libexecdir'.The above variables serve analogous purposes in the makefiles for allGNU software; the following variables are specific to Emacs.`archlibdir' indicates where Emacs installs and expects the executable	files and other architecture-dependent data it uses while	running.  Its default value, based on `libexecdir' (which	see), is `/usr/local/libexec/emacs/VERSION/CONFIGURATION-NAME'	(where VERSION and CONFIGURATION-NAME are as described above).`GZIP_PROG' is the name of the executable that compresses installed info,	manual, and .el files.  It defaults to gzip.  Setting it to	the empty string suppresses compression.Remember that you must specify any variable values you need each timeyou run `make' in the top directory.  If you run `make' once to buildemacs, test it, and then run `make' again to install the files, youmust provide the same variable settings each time.  To make thesettings persist, you can edit them into the `Makefile' in the topdirectory, but be aware that running the `configure' program erases`Makefile' and rebuilds it from `Makefile.in'.The path for finding Lisp files is specified in src/epaths.h,a file which is generated by running configure.  To change the path,you can edit the definition of PATH_LOADSEARCH in that filebefore you run `make'.The top-level Makefile stores the variable settings it used in theMakefiles for the subdirectories, so you don't have to specify themwhen running make in the subdirectories.CONFIGURATION BY HANDThis should not be necessary and is not recommended.  Instead ofrunning the `configure' program, you have to perform the following steps.1) Copy `./src/config.in' to `./src/config.h'.2) Edit `./src/config.h' to set the right options for your system.3) Create `Makefile' files in various directories from thecorresponding `Makefile.in' files.  This isn't so hard, just a matterof editing in appropriate substitutions for the @...@ constructs.The `configure' script is built from `configure.ac' by the`autogen.sh' script, which checks that `autoconf' and other buildtools are sufficiently up to date and then runs the build tools.BUILDING GNU EMACS BY HANDOnce Emacs is configured, running `make' in the top directory performsthe following steps.1) Run `make epaths-force' in the top directory.  This produces`./src/epaths.h' from the template file `./src/epaths.in', changingthe paths to the values specified in `./Makefile'.2) Go to directory `./lib' and run `make'.  This creates include filesand libraries used in later steps.3) Go to directory `./lib-src' and run `make'.  This createsexecutables named `etags', `make-docfile', and others.4) Go to directory `./src' and run `make'.  This refers to files inthe `./lisp', `./lib', and `./lib-src' subdirectories using names`../lisp', `../lib', and `../lib-src'.This creates a file `./src/emacs' which is the runnable Emacs,which has another name that contains a version number.Each time you do this, that version number increments in the last place.It also creates a file in `./etc' whose name is `DOC' followed by thecurrent Emacs version.  This file contains documentation strings forall the functions in Emacs.  Each time you run make to make a newemacs, a new DOC file with a new name is made.  You must keep the DOCfile for an Emacs version as long as you keep using that Emacs version.INSTALLATION BY HANDThe steps below are done by running `make install' in the maindirectory of the Emacs distribution.1) Copy `./lisp' and its subdirectories, `./etc', and the executablesin `./lib-src' to their final destinations, as selected in `./src/epaths.h'.Strictly speaking, not all of the executables in `./lib-src' need be copied.- The programs `hexl', `movemail', `profile', and `rcs2log'    are used by Emacs; they do need to be copied.- The programs `etags', `ctags', and `emacsclient' are intended to be    run by users; they are handled below.- The programs `make-docfile' and `test-distrib' were    used in building Emacs, and are not needed any more.2) Copy the files in `./info' to the place specified in`./lisp/site-init.el' or `./lisp/info.el'.  Note that if thedestination directory already contains a file named `dir', youprobably don't want to replace it with the `dir' file in the Emacsdistribution.  Instead, you should make sure that the existing `dir'file contains an appropriate menu entry for the Emacs info.3) Copy `./src/emacs' to `/usr/local/bin', or to some other directoryin users' search paths.  `./src/emacs' has an alternate name`./src/emacs-EMACSVERSION'; you may wish to make a symbolic link named`/usr/local/bin/emacs' pointing to that alternate name, as an easy wayof installing different versions.You can delete `./src/temacs'.4) Copy the programs `emacsclient', `ctags', and `etags' from `./lib-src'to `/usr/local/bin'.  These programs are intended for users to run.5) Copy the man pages in `./doc/man' into the appropriate man directory.6) The files in the `./src' subdirectory, except for `emacs', are notused by Emacs once it is built.  However, it is very desirable to keepthe source on line for debugging.PROBLEMSSee the file `./etc/PROBLEMS' for a list of various problems sometimesencountered, and what to do about them.This file is part of GNU Emacs.GNU Emacs is free software: you can redistribute it and/or modifyit under the terms of the GNU General Public License as published bythe Free Software Foundation, either version 3 of the License, or(at your option) any later version.GNU Emacs is distributed in the hope that it will be useful,but WITHOUT ANY WARRANTY; without even the implied warranty ofMERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See theGNU General Public License for more details.You should have received a copy of the GNU General Public Licensealong with GNU Emacs.  If not, see 
     .