Commit | Line | Data |
---|---|---|
067d23c9 | 1 | GNU Emacs Installation Guide |
ba318903 PE |
2 | Copyright (C) 1992, 1994, 1996-1997, 2000-2014 Free Software Foundation, |
3 | Inc. | |
067d23c9 KY |
4 | See the end of the file for license conditions. |
5 | ||
6 | ||
7 | This file contains general information on building GNU Emacs. | |
8 | For more information specific to the MS-Windows, GNUstep/Mac OS X, and | |
9 | MS-DOS ports, also read the files nt/INSTALL, nextstep/INSTALL, and | |
10 | msdos/INSTALL. For information about building from a Bazaar checkout | |
11 | (rather than a release), also read the file INSTALL.BZR. | |
12 | ||
13 | ||
14 | BASIC INSTALLATION | |
15 | ||
16 | On most Unix systems, you build Emacs by first running the `configure' | |
17 | shell script. This attempts to deduce the correct values for | |
18 | various system-dependent variables and features, and find the | |
19 | directories where certain system headers and libraries are kept. | |
20 | In a few cases, you may need to explicitly tell configure where to | |
21 | find some things, or what options to use. | |
22 | ||
23 | `configure' creates a `Makefile' in several subdirectories, and a | |
24 | `src/config.h' file containing system-dependent definitions. | |
25 | Running the `make' utility then builds the package for your system. | |
26 | ||
27 | Here's the procedure to build Emacs using `configure' on systems which | |
28 | are supported by it. In some cases, if the simplified procedure fails, | |
29 | you might need to use various non-default options, and maybe perform | |
30 | some of the steps manually. The more detailed description in the other | |
31 | sections of this guide will help you do that, so please refer to those | |
32 | sections if you need to. | |
33 | ||
1c889bf6 GM |
34 | 1. Unpacking the Emacs 24.1 release requires about 180 MB of free |
35 | disk space. Building Emacs uses about another 70 MB of space. | |
36 | The final installed Emacs uses about 110 MB of disk space. | |
067d23c9 KY |
37 | This includes the space-saving that comes from automatically |
38 | compressing the Lisp source files on installation. | |
39 | ||
40 | 2a. `cd' to the directory where you unpacked Emacs and invoke the | |
41 | `configure' script: | |
42 | ||
43 | ./configure | |
44 | ||
45 | 2b. Alternatively, create a separate directory, outside the source | |
46 | directory, where you want to build Emacs, and invoke `configure' | |
47 | from there: | |
48 | ||
49 | SOURCE-DIR/configure | |
50 | ||
51 | where SOURCE-DIR is the top-level Emacs source directory. | |
52 | This may not work unless you use GNU make. | |
53 | ||
54 | 3. When `configure' finishes, it prints several lines of details | |
55 | about the system configuration. Read those details carefully | |
56 | looking for anything suspicious, such as wrong CPU and operating | |
57 | system names, wrong places for headers or libraries, missing | |
58 | libraries that you know are installed on your system, etc. | |
59 | ||
60 | If you find anything wrong, you may have to pass to `configure' | |
61 | one or more options specifying the explicit machine configuration | |
62 | name, where to find various headers and libraries, etc. | |
63 | Refer to the section DETAILED BUILDING AND INSTALLATION below. | |
64 | ||
062727ce PE |
65 | If `configure' didn't find some image support libraries, such as |
66 | Xpm and jpeg, refer to "Image support libraries" below. | |
067d23c9 KY |
67 | |
68 | If the details printed by `configure' don't make any sense to | |
69 | you, but there are no obvious errors, assume that `configure' did | |
70 | its job and proceed. | |
71 | ||
c54c978e | 72 | 4. Invoke the `make' program: |
067d23c9 KY |
73 | |
74 | make | |
75 | ||
c54c978e | 76 | 5. If `make' succeeds, it will build an executable program `emacs' |
067d23c9 KY |
77 | in the `src' directory. You can try this program, to make sure |
78 | it works: | |
79 | ||
80 | src/emacs -Q | |
81 | ||
c54c978e | 82 | 6. Assuming that the program `src/emacs' starts and displays its |
067d23c9 KY |
83 | opening screen, you can install the program and its auxiliary |
84 | files into their installation directories: | |
85 | ||
86 | make install | |
87 | ||
88 | You are now ready to use Emacs. If you wish to conserve disk space, | |
89 | you may remove the program binaries and object files from the | |
90 | directory where you built Emacs: | |
91 | ||
92 | make clean | |
93 | ||
94 | You can delete the entire build directory if you do not plan to | |
95 | build Emacs again, but it can be useful to keep for debugging. | |
c54c978e GM |
96 | If you want to build Emacs again with different configure options, |
97 | first clean the source directories: | |
98 | ||
99 | make distclean | |
067d23c9 KY |
100 | |
101 | Note that the install automatically saves space by compressing | |
102 | (provided you have the `gzip' program) those installed Lisp source (.el) | |
103 | files that have corresponding .elc versions, as well as the Info files. | |
104 | ||
105 | ||
106 | ADDITIONAL DISTRIBUTION FILES | |
107 | ||
108 | * Complex Text Layout support libraries | |
109 | ||
e1504b9b EZ |
110 | On GNU and Unix systems, Emacs needs the optional libraries "m17n-db", |
111 | "libm17n-flt", "libotf" to correctly display such complex scripts as | |
112 | Indic and Khmer, and also for scripts that require Arabic shaping | |
113 | support (Arabic and Farsi). On some systems, particularly GNU/Linux, | |
114 | these libraries may be already present or available as additional | |
115 | packages. Note that if there is a separate `dev' or `devel' package, | |
116 | for use at compilation time rather than run time, you will need that | |
117 | as well as the corresponding run time package; typically the dev | |
118 | package will contain header files and a library archive. Otherwise, | |
525540c0 | 119 | you can download the libraries from <http://www.nongnu.org/m17n/>. |
067d23c9 | 120 | |
e1504b9b EZ |
121 | Note that Emacs cannot support complex scripts on a TTY, unless the |
122 | terminal includes such a support. | |
123 | ||
067d23c9 KY |
124 | * intlfonts-VERSION.tar.gz |
125 | ||
126 | The intlfonts distribution contains X11 fonts in various encodings | |
127 | that Emacs can use to display international characters. If you see a | |
128 | non-ASCII character appear as a hollow box, that means you don't have | |
129 | a font for it. You might find one in the intlfonts distribution. If | |
130 | you do have a font for a non-ASCII character, but some characters | |
131 | don't look right, or appear improperly aligned, a font from the | |
132 | intlfonts distribution might look better. | |
133 | ||
134 | The fonts in the intlfonts distribution are also used by the ps-print | |
135 | package for printing international characters. The file | |
136 | lisp/ps-mule.el defines the *.bdf font files required for printing | |
137 | each character set. | |
138 | ||
139 | The intlfonts distribution contains its own installation instructions, | |
140 | in the intlfonts/README file. | |
141 | ||
142 | * Image support libraries | |
143 | ||
062727ce PE |
144 | Emacs needs libraries to display images, with the exception of PBM and |
145 | XBM images whose support is built-in. | |
067d23c9 KY |
146 | |
147 | On some systems, particularly on GNU/Linux, these libraries may | |
062727ce | 148 | already be present or available as additional packages. If |
067d23c9 KY |
149 | there is a separate `dev' or `devel' package, for use at compilation |
150 | time rather than run time, you will need that as well as the | |
151 | corresponding run time package; typically the dev package will | |
152 | contain header files and a library archive. Otherwise, you can | |
062727ce PE |
153 | download and build libraries from sources. Although none of them are |
154 | essential for running Emacs, some are important enough that | |
155 | 'configure' will report an error if they are absent from a system that | |
156 | has X11 support, unless 'configure' is specifically told to omit them. | |
157 | ||
158 | Here's a list of some of these libraries, and the URLs where they | |
159 | can be found (in the unlikely event that your distribution does not | |
160 | provide them). By default, libraries marked with an X are required if | |
161 | X11 is being used. | |
162 | ||
163 | libXaw3d http://directory.fsf.org/project/xaw3d/ | |
164 | X libxpm for XPM: http://www.x.org/releases/current/src/lib/ | |
165 | X libpng for PNG: http://www.libpng.org/ | |
166 | libz (for PNG): http://www.zlib.net/ | |
167 | X libjpeg for JPEG: http://www.ijg.org/ | |
168 | X libtiff for TIFF: http://www.remotesensing.org/libtiff/ | |
169 | X libgif for GIF: http://sourceforge.net/projects/giflib/ | |
170 | ||
171 | If you supply the appropriate --without-LIB option, 'configure' will | |
172 | omit the corresponding library from Emacs, even if that makes for a | |
173 | less-pleasant user interface. Otherwise, Emacs will configure itself | |
174 | to build with these libraries if 'configure' finds them on your | |
175 | system, and 'configure' will complain and exit if a library marked 'X' | |
176 | is not found on a system that uses X11. Use --without-LIB if your | |
177 | version of a library won't work because some routines are missing. | |
067d23c9 KY |
178 | |
179 | * Extra fonts | |
180 | ||
181 | The Emacs distribution does not include fonts and does not install | |
182 | them. | |
183 | ||
184 | On the GNU system, Emacs supports both X fonts and local fonts | |
185 | (i.e. fonts managed by the fontconfig library). If you need more | |
186 | fonts than your distribution normally provides, you must install them | |
187 | yourself. See <URL:http://www.gnu.org/software/freefont/> for a large | |
188 | number of free Unicode fonts. | |
189 | ||
190 | * GNU/Linux development packages | |
191 | ||
192 | Many GNU/Linux systems do not come with development packages by default; | |
193 | they include the files that you need to run Emacs, but not those you | |
194 | need to compile it. For example, to compile Emacs with support for X | |
195 | and graphics libraries, you may need to install the `X development' | |
196 | package(s), and development versions of the jpeg, png, etc. packages. | |
197 | ||
198 | The names of the packages that you need varies according to the | |
199 | GNU/Linux distribution that you use, and the options that you want to | |
200 | configure Emacs with. On Debian-based systems, you can install all the | |
201 | packages needed to build the installed version of Emacs with a command | |
9dbd3bb1 | 202 | like `apt-get build-dep emacs24'. On Red Hat systems, the |
1d8d4d70 | 203 | corresponding command is `yum-builddep emacs'. |
067d23c9 KY |
204 | |
205 | ||
206 | DETAILED BUILDING AND INSTALLATION: | |
207 | ||
208 | (This is for a Unix or Unix-like system. For MS-DOS and MS Windows 3.X, | |
209 | see msdos/INSTALL. For later versions of MS Windows, see the file | |
210 | nt/INSTALL. For GNUstep and Mac OS X, see nextstep/INSTALL.) | |
211 | ||
212 | 1) Make sure your system has enough swapping space allocated to handle | |
213 | a program whose pure code is 1.5 MB and whose data area is at | |
214 | least 2.8 MB and can reach 100 MB or more. If the swapping space is | |
215 | insufficient, you will get an error in the command `temacs -batch -l | |
216 | loadup dump', found in `./src/Makefile.in', or possibly when | |
217 | running the final dumped Emacs. (This should not be an issue | |
218 | on any recent system.) | |
219 | ||
220 | Building Emacs requires about 230 MB of disk space (including the | |
221 | Emacs sources). Once installed, Emacs occupies about 120 MB in the file | |
222 | system where it is installed; this includes the executable files, Lisp | |
223 | libraries, miscellaneous data files, and on-line documentation. If | |
224 | the building and installation take place in different directories, | |
225 | then the installation procedure momentarily requires 230+120 MB. | |
226 | ||
227 | 2) In the unlikely event that `configure' does not detect your system | |
228 | type correctly, consult `./etc/MACHINES' to see what --host, --build | |
229 | options you should pass to `configure'. That file also offers hints | |
230 | for getting around some possible installation problems. | |
231 | ||
232 | 3) You can build Emacs in the top-level Emacs source directory | |
233 | or in a separate directory. | |
234 | ||
235 | 3a) To build in the top-level Emacs source directory, go to that | |
236 | directory and run the program `configure' as follows: | |
237 | ||
238 | ./configure [--OPTION[=VALUE]] ... | |
239 | ||
240 | If `configure' cannot determine your system type, try again | |
241 | specifying the proper --build, --host options explicitly. | |
242 | ||
243 | If you don't want X support, specify `--with-x=no'. If you omit this | |
244 | option, `configure' will try to figure out for itself whether your | |
245 | system has X, and arrange to use it if present. | |
246 | ||
247 | The `--x-includes=DIR' and `--x-libraries=DIR' options tell the build | |
248 | process where the compiler should look for the include files and | |
249 | object libraries used with the X Window System. Normally, `configure' | |
250 | is able to find them; these options are necessary if you have your X | |
251 | Window System files installed in unusual places. These options also | |
252 | accept a list of directories, separated with colons. | |
253 | ||
254 | To get more attractive menus, you can specify an X toolkit when you | |
255 | configure Emacs; use the option `--with-x-toolkit=TOOLKIT', where | |
256 | TOOLKIT is `gtk' (the default), `athena', or `motif' (`yes' and | |
257 | `lucid' are synonyms for `athena'). On some systems, it does not work | |
258 | to use a toolkit with shared libraries. A free implementation of | |
259 | Motif, called LessTif, is available from <http://www.lesstif.org>. | |
260 | Compiling with LessTif or Motif causes a standard File Selection | |
261 | Dialog to pop up when you invoke file commands with the mouse. You | |
262 | can get fancy 3D-style scroll bars, even without Gtk or LessTif/Motif, | |
263 | if you have the Xaw3d library installed (see "Image support libraries" | |
264 | above for Xaw3d availability). | |
265 | ||
266 | You can tell configure where to search for GTK by specifying | |
267 | `--with-pkg-config-prog=PATH' where PATH is the pathname to | |
268 | pkg-config. Note that GTK version 2.6 or newer is required for Emacs. | |
269 | ||
68b0c113 MA |
270 | Emacs will autolaunch a D-Bus session bus, when the environment |
271 | variable DISPLAY is set, but no session bus is running. This might be | |
272 | inconvenient for Emacs when running as daemon or running via a remote | |
a4fe5376 GM |
273 | ssh connection. In order to completely prevent the use of D-Bus, configure |
274 | Emacs with the options `--without-dbus --without-gconf --without-gsettings'. | |
68b0c113 | 275 | |
067d23c9 KY |
276 | The Emacs mail reader RMAIL is configured to be able to read mail from |
277 | a POP3 server by default. Versions of the POP protocol older than | |
278 | POP3 are not supported. For Kerberos-authenticated POP add | |
279 | `--with-kerberos', for Hesiod support add `--with-hesiod'. While POP3 | |
280 | is always enabled, whether Emacs actually uses POP is controlled by | |
281 | individual users--see the Rmail chapter of the Emacs manual. | |
282 | ||
283 | For image support you may have to download, build, and install the | |
284 | appropriate image support libraries for image types other than XBM and | |
062727ce | 285 | PBM, see the list of URLs in "Image support libraries" above. |
067d23c9 KY |
286 | (Note that PNG support requires libz in addition to libpng.) |
287 | ||
288 | To disable individual types of image support in Emacs for some reason, | |
289 | even though configure finds the libraries, you can configure with one | |
290 | or more of these options: | |
291 | ||
292 | --without-xpm for XPM image support | |
293 | --without-jpeg for JPEG image support | |
294 | --without-tiff for TIFF image support | |
295 | --without-gif for GIF image support | |
296 | --without-png for PNG image support | |
297 | ||
298 | Use --without-toolkit-scroll-bars to disable LessTif/Motif or Xaw3d | |
299 | scroll bars. | |
300 | ||
301 | Use --without-xim to inhibit the default use of X Input Methods. | |
302 | In this case, the X resource useXIM can be used to turn on use of XIM. | |
303 | ||
304 | Use --disable-largefile to omit support for files larger than 2GB on | |
305 | systems which support that. | |
306 | ||
307 | Use --without-sound to disable sound support. | |
308 | ||
da3d2105 DA |
309 | Use --without-all if you want to build a small executable with the minimal |
310 | dependencies on external libraries, at the cost of disabling most of the | |
311 | features that are normally enabled by default. Using --without-all is | |
312 | equivalent to --without-sound --without-dbus --without-libotf | |
313 | --without-selinux --without-xft --without-gsettings --without-gnutls | |
314 | --without-rsvg --without-xml2 --without-gconf --without-imagemagick | |
315 | --without-m17n-flt --without-jpeg --without-tiff --without-gif | |
7bddb120 MA |
316 | --without-png --without-gpm --without-file-notification. Note that |
317 | --without-all leaves X support enabled, and using the GTK2 or GTK3 | |
318 | toolkit creates a lot of library dependencies. So if you want to | |
319 | build a small executable with very basic X support, use --without-all | |
320 | --with-x-toolkit=no. For the smallest possible executable without X, | |
321 | use --without-all --without-x. If you want to build with just a few | |
322 | features enabled, you can combine --without-all with --with-FEATURE. | |
323 | For example, you can use --without-all --with-dbus to build with DBus | |
324 | support and nothing more. | |
c30d4aef | 325 | |
81eafe29 PE |
326 | Use --with-wide-int to implement Emacs values with the type 'long long', |
327 | even on hosts where a narrower type would do. With this option, on a | |
328 | typical 32-bit host, Emacs integers have 62 bits instead of 30. | |
329 | ||
67546201 PE |
330 | Use --enable-gcc-warnings to enable compile-time checks that warn |
331 | about possibly-questionable C code. This is intended for developers | |
332 | and is useful with GNU-compatible compilers. On a recent GNU system | |
333 | there should be no warnings; on older and on non-GNU systems the | |
334 | generated warnings may still be useful. | |
335 | ||
94eb8e0a DA |
336 | Use --enable-link-time-optimization to enable link-time optimizer, which |
337 | is available in GNU compiler since version 4.5.0. If your compiler is not | |
338 | GNU or older than version 4.5.0, this option does nothing. If `configure' | |
339 | can determine number of online CPUS on your system, final link-time | |
340 | optimization and code generation is executed in parallel using one job | |
341 | per each available online CPU. | |
342 | ||
067d23c9 KY |
343 | The `--prefix=PREFIXDIR' option specifies where the installation process |
344 | should put emacs and its data files. This defaults to `/usr/local'. | |
345 | - Emacs (and the other utilities users run) go in PREFIXDIR/bin | |
346 | (unless the `--exec-prefix' option says otherwise). | |
347 | - The architecture-independent files go in PREFIXDIR/share/emacs/VERSION | |
348 | (where VERSION is the version number of Emacs, like `23.2'). | |
349 | - The architecture-dependent files go in | |
350 | PREFIXDIR/libexec/emacs/VERSION/CONFIGURATION | |
351 | (where CONFIGURATION is the configuration name, like | |
352 | i686-pc-linux-gnu), unless the `--exec-prefix' option says otherwise. | |
353 | ||
354 | The `--exec-prefix=EXECDIR' option allows you to specify a separate | |
355 | portion of the directory tree for installing architecture-specific | |
356 | files, like executables and utility programs. If specified, | |
357 | - Emacs (and the other utilities users run) go in EXECDIR/bin, and | |
358 | - The architecture-dependent files go in | |
359 | EXECDIR/libexec/emacs/VERSION/CONFIGURATION. | |
360 | EXECDIR/bin should be a directory that is normally in users' PATHs. | |
361 | ||
362 | For example, the command | |
363 | ||
364 | ./configure --build=i386-linux-gnu --without-sound | |
365 | ||
366 | configures Emacs to build for a 32-bit GNU/Linux distribution, | |
367 | without sound support. | |
368 | ||
369 | `configure' doesn't do any compilation or installation itself. | |
370 | It just creates the files that influence those things: | |
371 | `./Makefile' in the top-level directory and several subdirectories; | |
372 | and `./src/config.h'. For details on exactly what it does, see the | |
373 | section called `CONFIGURATION BY HAND', below. | |
374 | ||
375 | When it is done, `configure' prints a description of what it did and | |
376 | creates a shell script `config.status' which, when run, recreates the | |
377 | same configuration. If `configure' exits with an error after | |
378 | disturbing the status quo, it removes `config.status'. `configure' | |
379 | also creates a file `config.cache' that saves the results of its tests | |
380 | to make reconfiguring faster, and a file `config.log' containing compiler | |
381 | output (useful mainly for debugging `configure'). You can give | |
382 | `configure' the option `--cache-file=FILE' to use the results of the | |
383 | tests in FILE instead of `config.cache'. Set FILE to `/dev/null' to | |
384 | disable caching, for debugging `configure'. | |
385 | ||
386 | If the description of the system configuration printed by `configure' | |
387 | is not right, or if it claims some of the features or libraries are not | |
388 | available when you know they are, look at the `config.log' file for | |
389 | the trace of the failed tests performed by `configure' to check | |
390 | whether these features are supported. Typically, some test fails | |
391 | because the compiler cannot find some function in the system | |
392 | libraries, or some macro-processor definition in the system headers. | |
393 | ||
394 | Some tests might fail because the compiler should look in special | |
395 | directories for some header files, or link against optional | |
396 | libraries, or use special compilation options. You can force | |
397 | `configure' and the build process which follows it to do that by | |
398 | setting the variables CPPFLAGS, CFLAGS, LDFLAGS, LIBS, CPP and CC | |
399 | before running `configure'. CPP is the command which invokes the | |
400 | preprocessor, CPPFLAGS lists the options passed to it, CFLAGS are | |
401 | compilation options, LDFLAGS are options used when linking, LIBS are | |
402 | libraries to link against, and CC is the command which invokes the | |
403 | compiler. By default, gcc is used if available. | |
404 | ||
405 | Here's an example of a `configure' invocation, assuming a Bourne-like | |
406 | shell such as Bash, which uses these variables: | |
407 | ||
408 | CPPFLAGS='-I/foo/myinclude' LDFLAGS='-L/bar/mylib' \ | |
409 | CFLAGS='-O3' LIBS='-lfoo -lbar' ./configure | |
410 | ||
411 | (this is all one long line). This tells `configure' to instruct the | |
412 | preprocessor to look in the `/foo/myinclude' directory for header | |
413 | files (in addition to the standard directories), instruct the linker | |
414 | to look in `/bar/mylib' for libraries, pass the -O3 optimization | |
415 | switch to the compiler, and link against libfoo and libbar | |
416 | libraries in addition to the standard ones. | |
417 | ||
418 | For some libraries, like Gtk+, fontconfig and ALSA, `configure' uses | |
419 | pkg-config to find where those libraries are installed. | |
420 | If you want pkg-config to look in special directories, you have to set | |
421 | the environment variable PKG_CONFIG_PATH to point to the directories | |
422 | where the .pc-files for those libraries are. | |
423 | For example: | |
424 | ||
425 | PKG_CONFIG_PATH='/usr/local/alsa/lib/pkgconfig:/opt/gtk+-2.8/lib/pkgconfig' \ | |
426 | ./configure | |
427 | ||
428 | The work of `configure' can be done by editing various files in the | |
429 | distribution, but using `configure' is easier. See the section called | |
430 | "CONFIGURATION BY HAND" below if you want to do the configuration | |
431 | yourself. | |
432 | ||
433 | 3b) To build in a separate directory, go to that directory | |
434 | and run the program `configure' as follows: | |
435 | ||
436 | SOURCE-DIR/configure CONFIGURATION-NAME [--OPTION[=VALUE]] ... | |
437 | ||
438 | SOURCE-DIR refers to the top-level Emacs source directory which is | |
439 | where Emacs's configure script is located. `configure' looks for the | |
440 | Emacs source code in the directory that `configure' is in. | |
441 | ||
442 | To build in a separate directory, you must use a version of `make' | |
443 | that supports the `VPATH' variable, such as GNU `make'. | |
444 | ||
445 | (Do not try to build in a separate directory by creating many links | |
446 | to the real source directory--there is no need, and installation will | |
447 | fail.) | |
448 | ||
1ba6038a GM |
449 | 4) Put into `./lisp/site-init.el' or `./lisp/site-load.el' any Emacs |
450 | Lisp code you want Emacs to load before it is dumped out. Use | |
451 | site-load.el for additional libraries if you arrange for their | |
452 | documentation strings to be in the etc/DOC file (see | |
453 | src/Makefile.in if you wish to figure out how to do that). For all | |
454 | else, use site-init.el. Do not load byte-compiled code which | |
455 | was built with a non-nil value of `byte-compile-dynamic'. | |
456 | ||
457 | It is not a good idea to edit the normal .el files that come with Emacs. | |
458 | Instead, use a file like site-init.el to change settings. | |
459 | ||
460 | To change the value of a variable that is already defined in Emacs, | |
461 | you should use the Lisp function `setq', not `defvar'. For example, | |
067d23c9 KY |
462 | |
463 | (setq news-inews-program "/usr/bin/inews") | |
464 | ||
465 | is how you would override the default value of the variable | |
466 | news-inews-program. | |
467 | ||
468 | Before you override a variable this way, *look at the value* that the | |
469 | variable gets by default! Make sure you know what kind of value the | |
470 | variable should have. If you don't pay attention to what you are | |
471 | doing, you'll make a mistake. | |
472 | ||
067d23c9 KY |
473 | The `site-*.el' files are nonexistent in the distribution. You do not |
474 | need to create them if you have nothing to put in them. | |
475 | ||
1ba6038a | 476 | 5) Refer to the file `./etc/TERMS' for information on fields you may |
067d23c9 KY |
477 | wish to add to various termcap entries. (This is unlikely to be necessary.) |
478 | ||
1ba6038a | 479 | 6) Run `make' in the top directory of the Emacs distribution to finish |
067d23c9 KY |
480 | building Emacs in the standard way. The final executable file is |
481 | named `src/emacs'. You can execute this file "in place" without | |
482 | copying it, if you wish; then it automatically uses the sibling | |
483 | directories ../lisp, ../lib-src, ../info. | |
484 | ||
485 | Or you can "install" the executable and the other files into their | |
486 | installed locations, with `make install'. By default, Emacs's files | |
487 | are installed in the following directories: | |
488 | ||
489 | `/usr/local/bin' holds the executable programs users normally run - | |
418cd726 GM |
490 | `emacs', `etags', `ctags', `emacsclient', and |
491 | `grep-changelog'. | |
067d23c9 KY |
492 | |
493 | `/usr/local/share/emacs/VERSION/lisp' holds the Emacs Lisp library; | |
494 | `VERSION' stands for the number of the Emacs version | |
495 | you are installing, like `23.1' or `23.2'. Since the | |
496 | Lisp library changes from one version of Emacs to | |
497 | another, including the version number in the path | |
498 | allows you to have several versions of Emacs installed | |
499 | at the same time; in particular, you don't have to | |
500 | make Emacs unavailable while installing a new version. | |
501 | ||
502 | `/usr/local/share/emacs/VERSION/etc' holds the Emacs tutorial, the DOC | |
503 | file, and other architecture-independent files Emacs | |
504 | might need while running. | |
505 | ||
506 | `/usr/local/libexec/emacs/VERSION/CONFIGURATION-NAME' contains executable | |
507 | programs used by Emacs that users are not expected to | |
508 | run themselves. | |
509 | `VERSION' is the number of the Emacs version you are | |
510 | installing, and `CONFIGURATION-NAME' is the value | |
511 | deduced by the `configure' program to identify the | |
512 | architecture and operating system of your machine, | |
513 | like `i686-pc-linux-gnu' or `sparc-sun-sunos'. Since | |
514 | these files are specific to the version of Emacs, | |
515 | operating system, and architecture in use, including | |
516 | the configuration name in the path allows you to have | |
517 | several versions of Emacs for any mix of machines and | |
518 | operating systems installed at the same time; this is | |
519 | useful for sites at which different kinds of machines | |
520 | share the file system Emacs is installed on. | |
521 | ||
522 | `/usr/local/share/info' holds the on-line documentation for Emacs, | |
523 | known as "info files". Many other GNU programs are | |
524 | documented using info files as well, so this directory | |
525 | stands apart from the other, Emacs-specific directories. | |
526 | ||
527 | `/usr/local/share/man/man1' holds the man pages for the programs installed | |
528 | in `/usr/local/bin'. | |
529 | ||
530 | Any version of Emacs, whether installed or not, also looks for Lisp | |
531 | files in these directories. | |
532 | ||
533 | `/usr/local/share/emacs/VERSION/site-lisp' holds the local Emacs Lisp | |
534 | files installed for Emacs version VERSION only. | |
535 | ||
536 | `/usr/local/share/emacs/site-lisp' holds the local Emacs Lisp | |
537 | files installed for all Emacs versions. | |
538 | ||
539 | When Emacs is installed, it searches for its Lisp files | |
540 | in `/usr/local/share/emacs/VERSION/site-lisp', then in | |
541 | `/usr/local/share/emacs/site-lisp', and finally in | |
542 | `/usr/local/share/emacs/VERSION/lisp'. | |
543 | ||
544 | If these directories are not what you want, you can specify where to | |
545 | install Emacs's libraries and data files or where Emacs should search | |
546 | for its Lisp files by giving values for `make' variables as part of | |
547 | the command. See the section below called `MAKE VARIABLES' for more | |
548 | information on this. | |
549 | ||
1ba6038a | 550 | 7) Check the file `dir' in your site's info directory (usually |
067d23c9 KY |
551 | /usr/local/share/info) to make sure that it has a menu entry for the |
552 | Emacs info files. | |
553 | ||
1ba6038a | 554 | 8) If your system uses lock files to interlock access to mailer inbox files, |
067d23c9 KY |
555 | then you might need to make the movemail program setuid or setgid |
556 | to enable it to write the lock files. We believe this is safe. | |
557 | ||
1ba6038a | 558 | 9) You are done! You can remove executables and object files from |
067d23c9 KY |
559 | the build directory by typing `make clean'. To also remove the files |
560 | that `configure' created (so you can compile Emacs for a different | |
561 | configuration), type `make distclean'. If you don't need some, or all | |
562 | of the input methods from the Leim package, you can remove the | |
563 | unneeded files in the leim subdirectories of your site's lisp | |
564 | directory (usually /usr/local/share/emacs/VERSION/). | |
565 | ||
566 | ||
567 | ||
568 | MAKE VARIABLES | |
569 | ||
570 | You can change where the build process installs Emacs and its data | |
571 | files by specifying values for `make' variables as part of the `make' | |
572 | command line. For example, if you type | |
573 | ||
574 | make install bindir=/usr/local/gnubin | |
575 | ||
576 | the `bindir=/usr/local/gnubin' argument indicates that the Emacs | |
577 | executable files should go in `/usr/local/gnubin', not | |
578 | `/usr/local/bin'. | |
579 | ||
580 | Here is a complete list of the variables you may want to set. | |
581 | ||
582 | `bindir' indicates where to put executable programs that users can | |
583 | run. This defaults to /usr/local/bin. | |
584 | ||
585 | `datadir' indicates where to put the architecture-independent | |
586 | read-only data files that Emacs refers to while it runs; it | |
587 | defaults to /usr/local/share. We create the following | |
588 | subdirectories under `datadir': | |
589 | - `emacs/VERSION/lisp', containing the Emacs Lisp library, and | |
590 | - `emacs/VERSION/etc', containing the tutorials, DOC file, etc. | |
591 | `VERSION' is the number of the Emacs version you are installing, | |
592 | like `23.1' or `23.2'. Since these files vary from one version | |
593 | of Emacs to another, including the version number in the path | |
594 | allows you to have several versions of Emacs installed at the | |
595 | same time; this means that you don't have to make Emacs | |
596 | unavailable while installing a new version. | |
597 | ||
598 | `libexecdir' indicates where to put architecture-specific data files that | |
599 | Emacs refers to as it runs; it defaults to `/usr/local/libexec'. | |
600 | We create the following subdirectories under `libexecdir': | |
601 | - `emacs/VERSION/CONFIGURATION-NAME', containing executable | |
602 | programs used by Emacs that users are not expected to run | |
603 | themselves. | |
604 | `VERSION' is the number of the Emacs version you are installing, | |
605 | and `CONFIGURATION-NAME' is the value deduced by the | |
606 | `configure' program to identify the architecture and operating | |
607 | system of your machine, like `i686-pc-linux-gnu' or `sparc-sun-sunos'. | |
608 | Since these files are specific to the version of Emacs, | |
609 | operating system, and architecture in use, including the | |
610 | configuration name in the path allows you to have several | |
611 | versions of Emacs for any mix of machines and operating | |
612 | systems installed at the same time; this is useful for sites | |
613 | at which different kinds of machines share the file system | |
614 | Emacs is installed on. | |
615 | ||
616 | `infodir' indicates where to put the info files distributed with | |
617 | Emacs; it defaults to `/usr/local/share/info'. | |
618 | ||
619 | `mandir' indicates where to put the man pages for Emacs and its | |
620 | utilities (like `etags'); it defaults to | |
621 | `/usr/local/share/man/man1'. | |
622 | ||
623 | `prefix' doesn't give a path for any specific part of Emacs; instead, | |
624 | its value is used to determine the defaults for all the | |
625 | architecture-independent path variables - `datadir', | |
626 | `sharedstatedir', `infodir', and `mandir'. Its default value is | |
627 | `/usr/local'; the other variables add on `lib' or `man' to it | |
628 | by default. | |
629 | ||
630 | For example, suppose your site generally places GNU software | |
631 | under `/usr/users/software/gnusoft' instead of `/usr/local'. | |
632 | By including | |
633 | `prefix=/usr/users/software/gnusoft' | |
634 | in the arguments to `make', you can instruct the build process | |
635 | to place all of the Emacs data files in the appropriate | |
636 | directories under that path. | |
637 | ||
638 | `exec_prefix' serves the same purpose as `prefix', but instead | |
639 | determines the default values for the architecture-dependent | |
640 | path variables - `bindir' and `libexecdir'. | |
641 | ||
642 | The above variables serve analogous purposes in the makefiles for all | |
04765824 | 643 | GNU software; the following variables are specific to Emacs. |
067d23c9 KY |
644 | |
645 | `archlibdir' indicates where Emacs installs and expects the executable | |
646 | files and other architecture-dependent data it uses while | |
647 | running. Its default value, based on `libexecdir' (which | |
648 | see), is `/usr/local/libexec/emacs/VERSION/CONFIGURATION-NAME' | |
649 | (where VERSION and CONFIGURATION-NAME are as described above). | |
650 | ||
04765824 PE |
651 | `GZIP_PROG' is the name of the executable that compresses installed info, |
652 | manual, and .el files. It defaults to gzip. Setting it to | |
653 | the empty string suppresses compression. | |
654 | ||
067d23c9 KY |
655 | Remember that you must specify any variable values you need each time |
656 | you run `make' in the top directory. If you run `make' once to build | |
657 | emacs, test it, and then run `make' again to install the files, you | |
658 | must provide the same variable settings each time. To make the | |
659 | settings persist, you can edit them into the `Makefile' in the top | |
660 | directory, but be aware that running the `configure' program erases | |
661 | `Makefile' and rebuilds it from `Makefile.in'. | |
662 | ||
663 | The path for finding Lisp files is specified in src/epaths.h, | |
664 | a file which is generated by running configure. To change the path, | |
665 | you can edit the definition of PATH_LOADSEARCH in that file | |
666 | before you run `make'. | |
667 | ||
668 | The top-level Makefile stores the variable settings it used in the | |
669 | Makefiles for the subdirectories, so you don't have to specify them | |
670 | when running make in the subdirectories. | |
671 | ||
672 | ||
673 | CONFIGURATION BY HAND | |
674 | ||
675 | This should not be necessary and is not recommended. Instead of | |
676 | running the `configure' program, you have to perform the following steps. | |
677 | ||
678 | 1) Copy `./src/config.in' to `./src/config.h'. | |
679 | ||
1f492003 | 680 | 2) Edit `./src/config.h' to set the right options for your system. |
067d23c9 KY |
681 | |
682 | 3) Create `Makefile' files in various directories from the | |
683 | corresponding `Makefile.in' files. This isn't so hard, just a matter | |
684 | of editing in appropriate substitutions for the @...@ constructs. | |
685 | ||
b8b0239f PE |
686 | The `configure' script is built from `configure.ac' by the |
687 | `autogen.sh' script, which checks that `autoconf' and other build | |
688 | tools are sufficiently up to date and then runs the build tools. | |
067d23c9 KY |
689 | |
690 | BUILDING GNU EMACS BY HAND | |
691 | ||
692 | Once Emacs is configured, running `make' in the top directory performs | |
693 | the following steps. | |
694 | ||
695 | 1) Run `make epaths-force' in the top directory. This produces | |
696 | `./src/epaths.h' from the template file `./src/epaths.in', changing | |
697 | the paths to the values specified in `./Makefile'. | |
698 | ||
9a514d4a PE |
699 | 2) Go to directory `./lib' and run `make'. This creates include files |
700 | and libraries used in later steps. | |
701 | ||
702 | 3) Go to directory `./lib-src' and run `make'. This creates | |
067d23c9 KY |
703 | executables named `etags', `make-docfile', and others. |
704 | ||
9a514d4a PE |
705 | 4) Go to directory `./src' and run `make'. This refers to files in |
706 | the `./lisp', `./lib', and `./lib-src' subdirectories using names | |
707 | `../lisp', `../lib', and `../lib-src'. | |
067d23c9 KY |
708 | |
709 | This creates a file `./src/emacs' which is the runnable Emacs, | |
710 | which has another name that contains a version number. | |
711 | Each time you do this, that version number increments in the last place. | |
712 | ||
713 | It also creates a file in `./etc' whose name is `DOC' followed by the | |
714 | current Emacs version. This file contains documentation strings for | |
715 | all the functions in Emacs. Each time you run make to make a new | |
716 | emacs, a new DOC file with a new name is made. You must keep the DOC | |
717 | file for an Emacs version as long as you keep using that Emacs version. | |
718 | ||
719 | ||
720 | INSTALLATION BY HAND | |
721 | ||
722 | The steps below are done by running `make install' in the main | |
723 | directory of the Emacs distribution. | |
724 | ||
725 | 1) Copy `./lisp' and its subdirectories, `./etc', and the executables | |
726 | in `./lib-src' to their final destinations, as selected in `./src/epaths.h'. | |
727 | ||
728 | Strictly speaking, not all of the executables in `./lib-src' need be copied. | |
276d5f5d | 729 | - The programs `hexl', `movemail', `profile', and `rcs2log' |
c136e5cd | 730 | are used by Emacs; they do need to be copied. |
418cd726 GM |
731 | - The programs `etags', `ctags', and `emacsclient' are intended to be |
732 | run by users; they are handled below. | |
067d23c9 KY |
733 | - The programs `make-docfile' and `test-distrib' were |
734 | used in building Emacs, and are not needed any more. | |
735 | ||
736 | 2) Copy the files in `./info' to the place specified in | |
1ba6038a | 737 | `./lisp/site-init.el' or `./lisp/info.el'. Note that if the |
067d23c9 KY |
738 | destination directory already contains a file named `dir', you |
739 | probably don't want to replace it with the `dir' file in the Emacs | |
740 | distribution. Instead, you should make sure that the existing `dir' | |
741 | file contains an appropriate menu entry for the Emacs info. | |
742 | ||
743 | 3) Copy `./src/emacs' to `/usr/local/bin', or to some other directory | |
744 | in users' search paths. `./src/emacs' has an alternate name | |
745 | `./src/emacs-EMACSVERSION'; you may wish to make a symbolic link named | |
746 | `/usr/local/bin/emacs' pointing to that alternate name, as an easy way | |
747 | of installing different versions. | |
748 | ||
749 | You can delete `./src/temacs'. | |
750 | ||
418cd726 GM |
751 | 4) Copy the programs `emacsclient', `ctags', and `etags' from `./lib-src' |
752 | to `/usr/local/bin'. These programs are intended for users to run. | |
067d23c9 KY |
753 | |
754 | 5) Copy the man pages in `./doc/man' into the appropriate man directory. | |
755 | ||
756 | 6) The files in the `./src' subdirectory, except for `emacs', are not | |
757 | used by Emacs once it is built. However, it is very desirable to keep | |
758 | the source on line for debugging. | |
759 | ||
760 | ||
761 | PROBLEMS | |
762 | ||
763 | See the file `./etc/PROBLEMS' for a list of various problems sometimes | |
764 | encountered, and what to do about them. | |
765 | \f | |
766 | This file is part of GNU Emacs. | |
767 | ||
768 | GNU Emacs is free software: you can redistribute it and/or modify | |
769 | it under the terms of the GNU General Public License as published by | |
770 | the Free Software Foundation, either version 3 of the License, or | |
771 | (at your option) any later version. | |
772 | ||
773 | GNU Emacs is distributed in the hope that it will be useful, | |
774 | but WITHOUT ANY WARRANTY; without even the implied warranty of | |
775 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the | |
776 | GNU General Public License for more details. | |
777 | ||
778 | You should have received a copy of the GNU General Public License | |
779 | along with GNU Emacs. If not, see <http://www.gnu.org/licenses/>. |