head	1.1;
branch	1.1.1;
access;
symbols
	EMACS_21_3:1.1.1.22
	EMACS_21_2:1.1.1.21
	EMACS_21_1:1.1.1.21
	EMACS_21_0_106:1.1.1.21
	EMACS_21_0_105:1.1.1.21
	EMACS_21_0_103:1.1.1.20
	EMACS_20_7:1.1.1.19
	EMACS_20_6:1.1.1.19
	EMACS_20_5:1.1.1.19
	EMACS_20_4:1.1.1.19
	EMACS_20_3:1.1.1.18
	EMACS_20_2:1.1.1.17
	EMACS_20_1:1.1.1.17
	EMACS_19_34:1.1.1.16
	EMACS_19_33:1.1.1.16
	EMACS_19_32:1.1.1.15
	EMACS_19_31:1.1.1.14
	EMACS_19_30:1.1.1.13
	EMACS_19_29:1.1.1.12
	EMACS_19_28:1.1.1.11
	EMACS_19_27:1.1.1.11
	EMACS_19_26:1.1.1.11
	EMACS_19_25:1.1.1.10
	EMACS_19_24:1.1.1.10
	EMACS_19_23:1.1.1.9
	EMACS_19_22:1.1.1.8
	EMACS_19_21:1.1.1.8
	EMACS_19_20:1.1.1.8
	EMACS_19_19:1.1.1.7
	EMACS_19_18:1.1.1.7
	EMACS_19_17:1.1.1.6
	EMACS_19_16:1.1.1.6
	EMACS_19_15:1.1.1.6
	EMACS_19_14:1.1.1.6
	EMACS_19_13:1.1.1.5
	EMACS_19_12:1.1.1.5
	EMACS_19_11:1.1.1.4
	EMACS_19_10:1.1.1.4
	EMACS_19_9:1.1.1.4
	EMACS_19_8:1.1.1.3
	EMACS_19_7:1.1.1.2
	EMACS_18_59:1.1.1.1
	FSF_DIST:1.1.1;
locks; strict;
comment	@# @;


1.1
date	2004.11.05.07.57.13;	author Ben Wing;	state Exp;
branches
	1.1.1.1;
next	;

1.1.1.1
date	2004.11.05.07.57.13;	author Ben Wing;	state Exp;
branches;
next	1.1.1.2;

1.1.1.2
date	2004.11.05.07.57.41;	author Ben Wing;	state Exp;
branches;
next	1.1.1.3;

1.1.1.3
date	2004.11.05.08.00.25;	author Ben Wing;	state Exp;
branches;
next	1.1.1.4;

1.1.1.4
date	2004.11.05.08.03.22;	author Ben Wing;	state Exp;
branches;
next	1.1.1.5;

1.1.1.5
date	2004.11.05.08.12.03;	author Ben Wing;	state Exp;
branches;
next	1.1.1.6;

1.1.1.6
date	2004.11.05.08.17.50;	author Ben Wing;	state Exp;
branches;
next	1.1.1.7;

1.1.1.7
date	2004.11.05.08.30.25;	author Ben Wing;	state Exp;
branches;
next	1.1.1.8;

1.1.1.8
date	2004.11.05.08.37.17;	author Ben Wing;	state Exp;
branches;
next	1.1.1.9;

1.1.1.9
date	2004.11.05.08.47.16;	author Ben Wing;	state Exp;
branches;
next	1.1.1.10;

1.1.1.10
date	2004.11.05.08.51.39;	author Ben Wing;	state Exp;
branches;
next	1.1.1.11;

1.1.1.11
date	2004.11.05.08.58.50;	author Ben Wing;	state Exp;
branches;
next	1.1.1.12;

1.1.1.12
date	2004.11.05.09.09.58;	author Ben Wing;	state Exp;
branches;
next	1.1.1.13;

1.1.1.13
date	2004.11.05.09.15.24;	author Ben Wing;	state Exp;
branches;
next	1.1.1.14;

1.1.1.14
date	2004.11.05.09.21.02;	author Ben Wing;	state Exp;
branches;
next	1.1.1.15;

1.1.1.15
date	2004.11.05.09.27.56;	author Ben Wing;	state Exp;
branches;
next	1.1.1.16;

1.1.1.16
date	2004.11.05.09.33.15;	author Ben Wing;	state Exp;
branches;
next	1.1.1.17;

1.1.1.17
date	2004.11.05.09.42.44;	author Ben Wing;	state Exp;
branches;
next	1.1.1.18;

1.1.1.18
date	2004.11.05.09.55.29;	author Ben Wing;	state Exp;
branches;
next	1.1.1.19;

1.1.1.19
date	2004.11.05.10.03.24;	author Ben Wing;	state Exp;
branches;
next	1.1.1.20;

1.1.1.20
date	2004.11.05.10.29.43;	author Ben Wing;	state Exp;
branches;
next	1.1.1.21;

1.1.1.21
date	2004.11.05.10.39.18;	author Ben Wing;	state Exp;
branches;
next	1.1.1.22;

1.1.1.22
date	2004.11.05.11.14.48;	author Ben Wing;	state Exp;
branches;
next	;


desc
@@


1.1
log
@Initial revision
@
text
@GNU Emacs Installation Guide
Copyright (c) 1988 Free software Foundation, Inc.

   Permission is granted to anyone to make or distribute verbatim copies
   of this document as received, in any medium, provided that the
   copyright notice and permission notice are preserved,
   and that the distributor grants the recipient permission
   for further redistribution as permitted by this notice.

   Permission is granted to distribute modified versions
   of this document, or of portions of it,
   under the above conditions, provided also that they
   carry prominent notices stating who last changed them,
   and that any new or changed statements about the activities
   of the Free Software Foundation are approved by the Foundation.


PREPARATION

0) Make sure your system has enough swapping space allocated
 to handle a program whose pure code is 400k bytes or
 and whose data area is at least 150k and can reach 600k
 bytes or much more.  If the swapping space is insufficient, you
 will get an error in the command temacs -l loadup inc dump,
 found in $BUILD/src/ymakefile, or possibly when running the
 final dumped Emacs.
 
1) Choose a place in the file structure for the main directory
 of Emacs code to reside.  This will ultimately have
 subdirectories named src, lisp, etc, etc.  Call this name
 $EMACS.  Let $BUILD stand for the name the directory has now.

2) Copy $BUILD/src/config.h-dist to $BUILD/src/config.h,
 and edit it to set the right options for your system.  The file
 $BUILD/etc/MACHINES may help you decide what to put there.
 If you need to override any of the definitions in the s- and m-
 files for your system and machine, do so by editing config.h,
 not by changing the s- and m- files.  Occasionally you may
 need to redefine parameters used in etc/movemail.c.

3) Declare the place in the file system where Emacs will
 be once installed.  This is done in the file `src/paths.h'.
 But you don't have to change it yourself.  `build-install' and `make'
 edit `src/paths.h' automatically.

 If you are using the shell-script `build-install'
 edit the assignment that sets the variable `EMACS'.
 If you are using `make' in the main Emacs directory to do
 the installation, edit the definition of `LIBDIR' in `Makefile'
 in that directory.

 If you are doing the building by hand (not using `build-install' or
 `make') then you yourself must copy $BUILD/src/paths.h-dist to
 paths.h, and edit it to contain the correct directory names:
 $EMACS/lisp for the directory for Lisp libraries, and $EMACS/etc for
 the directory for executables and text files.

 Emacs will use these names once it has been built.
 During building, Emacs searches the directory ../lisp for
 Lisp files before the directories specified in paths.h, and
 executable files are found in ../etc.  So the main Emacs
 directory $BUILD can be anywhere while Emacs is built, but
 must be renamed to $EMACS afterwards in order for Emacs to
 work properly.

4) Look at $BUILD/lisp/paths.el; if some of those values
 are not right for your system, create a file
 $BUILD/lisp/site-init.el containing Lisp code to override them.
 You would use the Lisp function `setq'.  For example,

     (setq news-inews-program "/usr/bin/inews")

 is how you would override the default value of the
 variable news-inews-program (which is "/usr/local/inews").

5) Put into $BUILD/lisp/site-init.el any Lisp code
 you want loaded into Emacs before it is dumped out.

 This file is nonexistent in the distribution.
 You do not need to create it, if you have nothing
 to put in it.

6) Decide what compiler switches to use.
 For example, if you would like to compile with optimization, 
 you might want to change the definition of CFLAGS in
 the file $BUILD/src/ymakefile to use C_OPTIMIZE_SWITCH
 instead of C_DEBUG_SWITCH.

 Note that many Unix compilers have bugs that affect -O; if you use
 -O, be prepared to recompile without -O if you have any trouble.

 Note that many (most?) versions of debuggers
 other than GDB do not know how to handle programs like Emacs
 that use raw or cbreak mode, change other terminal status bits,
 and use asynchronous SIGIO signals for terminal input.
 However, most debuggers may work if Emacs uses a separate terminal
 from the one being used by the debugger, or if Emacs is using
 its own X window.

 If you do have a debugger that works, it is probably best to use `-g'
 so that you are not helpless in the face of a problem.

 With GCC, you can use -O and -g together.  The easiest way to do this
 is to change C_DEBUG_SWITCH to include both -O and -g.  GCC is probably
 more reliable with -O than without, as it is tested more with -O.

 The way to specify use of GCC is to set the environment variable CC
 to `gcc' before you do `make install'

7) If you wish to compile with GCC, you may need to use -traditional
 or run fixincludes.  This is needed if your system's header files
 are incompatible with ANSI C.  If your system header files are designed
 for ANSI C, then GCC should handle them properly.  For more info, refer
 the INSTALL file of GCC.

 If your system header files are non-ANSI and you don't use -traditional
 or fixincludes to compensate, the usual effect is that the ioctl
 system call does not work.  The result is an Emacs that almost completely
 fails to work.  

8) Refer to the file $BUILD/etc/TERMS for information on
 fields you may wish to add to various termcap entries.

9) Run `make install' in the main directory of the Emacs distribution
 to finish building and installing Emacs in the standard way.
 You are done!

(On system V, you need to use `make install.sysv' instead of `make install'.
On Xenix, use `make install.xenix'.
On AIX, use `make install.aix'.
You can also try `make INSTALL=./install.sh install'
on any kind of system.)

The last step of building Emacs involves running Emacs in a special
way.  At this time, if the directories that Emacs will refer to during
use for Lisp code and executables do not already exist, Emacs will
print a warning to this effect.  If you plan to have `make' create
these directories while it installs Emacs, then do not be alarmed by
the warnings.

The shell script `build-install' is an alternative to `make install'.
It is a little less sophisticated than the makefile, but probably
easier to customize for nonstandard kinds of installation.  If you
want to install in precisely the usual fashion, we recommend using
`make' rather than `build-install'.


BUILDING GNU EMACS
`make install' and its variants start with these steps to compile Emacs.

1) Cd to $BUILD/etc and run `make'.
 This creates files named `ctags' and `etags' and `wakeup'
 and `make-docfile' and `digest-doc' and `test-distrib'.  And others.

2) Cd to $BUILD/src and Run `make'
 This refers to files in the $BUILD/lisp and $BUILD/etc subdirectories
 using names ../lisp and ../etc.

 This creates a file $BUILD/src/xemacs which is the runnable Emacs,
 assigning it a new version number by incrementing the version
 stored in $BUILD/lisp/version.el.

 It also creates a file in $BUILD/etc, whose name is
 DOC followed by the current Emacs version.
 This file contains documentation strings for all the
 functions in Emacs.  Each time you run make to make a new xemacs,
 a new DOC file with a new name is made.  You must keep
 the DOC file for an Emacs version as long as you keep using
 that Emacs version.


INSTALLATION

After compilation, `make install' and its variants continue with these steps
to install the Emacs already compiled.

0) Move files from $BUILD to $EMACS if they are not the same directory.
 The files that you need include at least the subdirectories
 lisp, etc and info.  After this, the directory in which you said
 (in paths.h) Emacs would be installed actually contains the necessary
 parts of Emacs.

1) Move the file $EMACS/xemacs to /usr/local/bin/emacs,
 or some other name in users' search paths.
 `xemacs' has an alternate name $EMACS/src/emacs-EMACSVERSION;
 you may wish to make a symbolic link
 named /usr/local/bin/emacs pointing to that alternate name,
 as an easy way of installing different versions.

 You can delete $EMACS/src/temacs.

3) Move the programs ctags, etags and emacsclient from $EMACS/etc
 to /usr/local/bin.  These programs are run by users as shell commands.

 The program $EMACS/etc/wakeup is invoked by Emacs when appropriate.

 The programs $EMACS/etc/make-docfile and $EMACS/etc/test-distrib
 are not used any more; they were used in building Emacs.

 $EMACS/etc/digest-doc can be used to convert DOC into a
 file for users to read.  There is no important reason to move it.

4) The files in $EMACS/src subdirectory, except for xemacs,
 are not used by Emacs once it is built.


See the file PROBLEMS in this directory for a list of various
problems sometimes encountered, and what to do about them.
@


1.1.1.1
log
@import emacs-18.59
@
text
@@


1.1.1.2
log
@import emacs-19.7
@
text
@d2 1
a2 1
Copyright (c) 1992 Free software Foundation, Inc.
d18 1
a18 1
BUILDING AND INSTALLATION:
d20 7
a26 6
1) Make sure your system has enough swapping space allocated to handle
a program whose pure code is 900k bytes and whose data area is at
least 400k and can reach 8Mb or more.  If the swapping space is
insufficient, you will get an error in the command `temacs -batch -l
loadup dump', found in `./src/ymakefile', or possibly when running the
final dumped Emacs.
d28 42
a69 78
Building Emacs requires about 30 Mb of disk space.  Installed, Emacs
occupies about 20 Mb; this includes the executable files, lisp
libraries, miscellaneous data files, and on-line documentation.

2) Consult `./etc/MACHINES' to see what configuration name you should
give to the `configure' program.  That file sometimes offers hints for
getting around some possible installation problems.

3) In the top directory of the Emacs distribution, run the program
`configure' as follows:

    ./configure CONFIGURATION-NAME [--OPTION[=VALUE]] ...

The CONFIGURATION-NAME argument should be a configuration name given
in `./etc/MACHINES'.

The `--with-x', `--with-x11', and `--with-x10' options specify which
window system Emacs should support.  If you don't want X support,
specify `--with-x=no'.  If all of these options are omitted,
`configure' will try to figure out for itself whether your system has
X11, and arrange to use it if present.

The `--x-includes=DIR' and `--x-libraries=DIR' options tell the build
process where the compiler should look for the include files and
object libraries used with the X Window System.  Normally, your
compiler should be able to find these by default; these options should
only be necessary if you have your X Window System files installed in
unusual places.

The --run-in-place option sets up default values for the path
variables in `./Makefile' so that Emacs will expect to find its data
files (lisp libraries, runnable programs, and the like) in the same
locations they occupy while Emacs builds.  This means that you don't
have to install Emacs in order to run it; it uses its data files as
they were unpacked.

The `--with-gcc' option specifies that the build process should
compile Emacs using GCC.  If you don't want to use GCC, specify
`--with-gcc=no'.  If this option is omitted, `configure' will search
for GCC in your load path, and use it if present.

The --srcdir=DIR option specifies that the configuration and build
processes should look for the Emacs source code in DIR, when DIR is
not the current directory.


For example, the command

    ./configure mips-dec-ultrix --with-x11

configures Emacs to build for a DECstation running Ultrix, with
support for the X11 window system.

The `configure' program does not accept abbreviations for its
options.

Note that `configure' doesn't do any compilation or installation
itself.  It just creates the files that influence those things:
`./Makefile', `build-install', and `./src/config.h'.  For details on
exactly what it does, see the section called `CONFIGURATION BY HAND',
below.

When it is done, `configure' prints a description of what it did and
leaves a copy in the file `config.status'.  That file is also a shell
script which, when run, recreates the same configuration; it contains
the verbal description as a comment.  If `configure' exits with an
error after disturbing the status quo, it removes `config.status'.

The work of `configure' can be done by editing various files in the
distribution, but using `configure' is supposed to be simpler.  See
the section called "CONFIGURATION BY HAND" below if you want to do the
configuration yourself.

4) Look at `./lisp/paths.el'; if some of those values are not right
for your system, edit the file `./lisp/site-init.el' containing Emacs
Lisp code to override them; you probably don't want to edit paths.el
itself.  YOU MUST USE THE LISP FUNCTION `setq' TO ASSIGN VALUES,
rather than `defvar', as used by `./lisp/paths.el'.  For example,
d73 2
a74 2
is how you would override the default value of the variable
news-inews-program (which is "/usr/local/inews").
d76 2
a77 350
Note that, on some systems, the code you place in site-init.el must
not use expand-file-name or any other function which may look
something up in the system's password and user information database.
See `./PROBLEMS' for more details on which systems this affects.

5) Put into `./lisp/site-init.el' any Emacs Lisp code you want Emacs
to load before it is dumped out.  

Note that, on some systems, the code you place in site-init.el must
not use expand-file-name or any other function which may look
something up in the system's password and user information database.
See `./PROBLEMS' for more details on which systems this affects.

This file is nonexistent in the distribution.  You do not need to
create it if you have nothing to put in it.

6) Refer to the file `./etc/TERMS' for information on fields you may
wish to add to various termcap entries.  The files `./etc/termcap.ucb'
and `./etc/termcap.dat' may already contain appropriately-modified
entries.

7) Run `make' in the top directory of the Emacs distribution to finish
building Emacs in the standard way.  The final executable file will be
named `src/emacs'.  If you want to have Emacs's executable programs
and data files installed as well, run `make install'.

By default, Emacs installs its files in the following directories:

`/usr/local/bin' holds the executable programs users normally run -
		`emacs', `etags', `ctags', `b2m', and `emacsclient'.

`/usr/local/lib/emacs/VERSION/lisp' holds the Emacs Lisp library;
		`VERSION' stands for the number of the Emacs version
		you are installing, like `18.59' or `19.0'.  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; this means that you don't have to
		make Emacs unavailable while installing a new
		version.

		Emacs searches for its lisp files in
		`/usr/local/lib/emacs/site-lisp', then in this
		directory.

`/usr/local/lib/emacs/VERSION/etc' holds the Emacs tutorial, the DOC
		file, the `yow' database, and other
		architecture-independent files Emacs might need while
		running.  VERSION is as specified for `.../lisp'.

`/usr/local/lib/emacs/lock' contains files indicating who is editing
		what, so Emacs can detect editing clashes between
		users.

`/usr/local/lib/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 argument
		you gave to the `configure' program to identify the
		architecture and operating system of your machine,
		like `mips-dec-ultrix' 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/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/man/man1' holds the man pages for the programs installed
		in `/usr/local/bin'.

If these directories are not what you want, you can specify where to
install Emacs's libraries and data files or where Emacs should search
for its lisp files by giving values for `make' variables as part of
the command.  See the section below called `MAKE VARIABLES' for more
information on this.

8) Check the file `dir' in your site's info directory (usually
/usr/local/info) to make sure that it has a menu entry for the Emacs
info files.

9) You are done!


MAKE VARIABLES

You can change where the build process installs Emacs and its data
files by specifying values for `make' variables as part of the `make'
command line.  For example, if you type

    make install bindir=/usr/local/gnubin

the `bindir=/usr/local/gnubin' argument indicates that the Emacs
executable 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/lib.  We create the following
	subdirectories under `datadir':
	- `emacs/VERSION/lisp', containing the Emacs lisp library, and
	- `emacs/VERSION/etc', containing the Emacs tutorial, the DOC
		file, and the `yow' database.
	`VERSION' is the number of the Emacs version you are installing,
	like `18.59' or `19.0'.  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.

`statedir' indicates where to put architecture-independent data files
	that Emacs modifies while it runs; it defaults to
	/usr/local/lib as well.  We create the following
	subdirectories under `statedir':
	- `emacs/lock', containing files indicating who is editing
		what, so Emacs can detect editing clashes between
		users.

`libdir' indicates where to put architecture-specific data files that
	Emacs refers to as it runs; it too defaults to `/usr/local/lib'.
	We create the following subdirectories under `libdir':
	- `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 argument you gave to the
	`configure' program to identify the architecture and operating
	system of your machine, like `mips-dec-ultrix' 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/info'.

`mandir' indicates where to put the man pages for Emacs and its
	utilities (like `etags'); it defaults to
	`/usr/local/man/man1'.

`manext' gives the extension the man pages should be installed with.
	It should contain a period, followed by the appropriate
	digit.  It defaults to `.1'.  For example given the default
	values for `mandir' and `manext', the Emacs man page would be
	installed as `/usr/local/man/man1/emacs.1'.

`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',
	`statedir', `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 `libdir'.

The above variables serve analogous purposes in the makefiles for all
GNU software; here are some variables specific to Emacs.

`lispdir' indicates where Emacs installs and expects its lisp
	library.  Its default value, based on `datadir' (which see),
	is `/usr/local/lib/emacs/VERSION/lisp' (where `VERSION' is as
	described above).

`locallisppath' indicates where Emacs should search for lisp files
	specific to your site.  It should be a colon-separated list of
	directories; Emacs checks them in order before checking
	`lispdir'.

`lisppath' is the complete list of directories Emacs should search for
	its lisp files; its default value is the concatenation of
	`lispdir' and `locallisppath'.  It should be a colon-separated
	list of directories; Emacs checks them in the order they
	appear.

`etcdir' indicates where Emacs should install and expect the rest of
	its architecture-independent data, like the tutorial, DOC
	file, and yow database.  Its default value, based on `datadir'
	(which see), is `/usr/local/lib/emacs/VERSION/etc'.

`lockdir' indicates the directory where Emacs keeps track of its
	locking information.  Its default value, based on `statedir'
	(which see), is `/usr/local/lib/emacs/lock'.

`archlibdir' indicates where Emacs installs and expects the
	executable files and other architecture-dependent data it uses
	while running.  Its default value, based on `libdir' (which
	see), is `/usr/local/lib/emacs/VERSION/CONFIGURATION-NAME'
	(where VERSION and CONFIGURATION-NAME are as described above).

Remember that you must specify any variable values you need each time
you run `make' in the top directory.  If you run `make' once to build
emacs, test it, and then run `make' again to install the files, you
must provide the same variable settings each time.  To make the
settings persist, you can edit them into the `Makefile' in the top
directory, but be aware that running the `configure' program erases
`Makefile' and rebuilds it from `Makefile.in'.

The top-level Makefile stores the variable settings it used in the
Makefiles for the subdirectories, so you don't have to specify them
when running make in the subdirectories.


CONFIGURATION BY HAND

Running the `configure' program performs the following steps.

1) Copy `./src/config.h.in' to `./src/config.h'.

2) Consult `./etc/MACHINES' to see what configuration name you should
use for your system.  Look at the code of the `configure' script to
see which operating system and architecture description files from
`src/s' and `src/m' should be used for that configuration name.  Edit
`src/config.h', and change the two `#include' directives to include
the appropriate system and architecture description files.

2) Edit `./src/config.h' to set the right options for your system.  If
you need to override any of the definitions in the s/*.h and m/*.h
files for your system and machine, do so by editing config.h, not by
changing the s/*.h and m/*.h files.  Occasionally you may need to
redefine parameters used in `./lib-src/movemail.c'.

3) If you're going to use the make utility to build Emacs, copy
`./Makefile.in' to `./Makefile', and then edit that to specify the
appropriate values for the variables in the sections entitled "Things
`configure' Might Edit" and "Where To Install Things."  Note that you
may only need to change the variables `prefix' and `exec_prefix',
since the rest of the variables have reasonable defaults based on
them.

4) Typing `make src/Makefile lib-src/Makefile' builds the
makefiles for the subdirectories, editing in the values for the path
variables you establed in step 3.

-- or --

4) If you're going to use the build-install script to build Emacs,
copy `./build-install.in' to `./build-install', and edit the similar
definitions found at the top of the script.


The `configure' script is built from `configure.in' by the `autoconf'
program.  However, since Emacs has configuration requirements that
autoconf can't meet, `configure.in' uses an unholy marriage of
custom-baked configuration code and autoconf macros.  New versions of
autoconf could very well break this arrangement, so it may be wise to
avoid rebuilding `configure' from `configure.in' when possible.


BUILDING GNU EMACS BY HAND

Once Emacs is configured, running `make' or running the shell script
`build-install' in the top directory performs the following steps.

1) Run `make src/paths.h' in the top directory.  This produces
`./src/paths.h' from the template file `./src/paths.h.in', changing
the paths to the values specified in `./Makefile'.

2) Cd to `./lib-src' and run `make'.  This creates executables named
`ctags' and `etags' and `wakeup' and `make-docfile' and `digest-doc'
and `test-distrib'.  And others.

3) Cd to `./src' and Run `make'.  This refers to files in the `./lisp'
and `./lib-src' subdirectories using names `../lisp' and
`../lib-src'.

This creates a file `./src/emacs' which is the runnable Emacs,
assigning it a new version number by incrementing the version stored
in `./lisp/version.el'.

It also creates a file in `./etc' whose name is `DOC' followed by the
current Emacs version.  This file contains documentation strings for
all the functions in Emacs.  Each time you run make to make a new
emacs, a new DOC file with a new name is made.  You must keep the DOC
file for an Emacs version as long as you keep using that Emacs
version.


INSTALLATION BY HAND

The steps below are done by the shell script `build-install' or by
running `make install' in the main directory of the Emacs
distribution.

1) Copy `./lisp' and its subdirectories, `./etc', and the executables
in `./lib-src' to their final destinations, as selected in `./src/paths.h'.

Strictly speaking, not all of the executables in `./lib-src' need be copied.
- The programs `cvtmail', `emacsserver', `env', `fakemail', `hexl',
    `movemail', `timer', `vcdiff', `wakeup', and `yow' are used by
    Emacs; they do need to be copied.
- The programs `etags', `ctags', `emacsclient', `b2m', and `rcs2log'
    are intended to be run by users; they are handled below.
- The programs `make-docfile', `make-path', and `test-distrib' were
    used in building Emacs, and are not needed any more.
- The programs `digest-doc' and `sorted-doc' convert a `DOC' file into
    a file for users to read.  There is no important reason to move them.

2) Copy the files in `./info' to the place specified in
`./lisp/site-init.el' or `./lisp/paths.el'.  Note that if the
destination directory already contains a file named `dir', you
probably don't want to replace it with the `dir' file in the Emacs
distribution.  Instead, you should make sure that the existing `dir'
file contains an appropriate menu entry for the Emacs info.

3) Create a directory for Emacs to use for clash detection, named as
indicated by the PATH_LOCK macro in `./src/paths.h'.

4) Copy `./src/emacs' to `/usr/local/bin', or to some other directory
in 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 way
of installing different versions.

You can delete `./src/temacs'.

5) Copy the programs `b2m', `emacsclient', `ctags', `etags', and
`rcs2log' from `./lib-src' to `/usr/local/bin'.  These programs are
intended for users to run.

6) Copy the man pages in `./etc' for emacs, ctags, and etags into the
appropriate man directories.

7) The files in the `./src' subdirectory, except for `emacs', are not
used by Emacs once it is built.  The source would be handy for
debugging.
d79 126
a205 1
PROBLEMS
a208 2


@


1.1.1.3
log
@import emacs-19.8
@
text
@d56 1
a56 1
The `--run-in-place' option sets up default values for the path
d68 1
a68 1
The `--srcdir=DIR' option specifies that the configuration and build
a71 18
The `--prefix=PREFIXDIR' option specifies where the installation process
should 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/lib/emacs/VERSION
  (where VERSION is the version number of Emacs, like `19.7').
- The architecture-dependent files go in
  PREFIXDIR/lib/emacs/VERSION/CONFIGURATION
  (where CONFIGURATION is the configuration name, like mips-dec-ultrix4.2),
  unless the `--exec-prefix' option says otherwise.

The `--exec-prefix=EXECDIR' option allows you to specify a separate
portion of the directory tree for installing architecture-specific
files, 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/lib/emacs/VERSION/CONFIGURATION.
EXECDIR/bin should be a directory that is normally in users' PATHs.
@


1.1.1.4
log
@import emacs-19.9
@
text
@d41 1
a41 4
in `./etc/MACHINES'.  If omitted, `configure' will try to guess your
system type by inspecting its environment; if it cannot, you must find
the appropriate configuration name in `./etc/MACHINES' and specify it
explicitly.
@


1.1.1.5
log
@import emacs-19.12
@
text
@d220 1
a220 5
9) If your system uses lock files to interlock access to mailer inbox files,
then you might need to make the program arch-lib/movemail setuid or setgid
to enable it to write the lock files.  We believe this is safe.

10) You are done!
@


1.1.1.6
log
@import emacs-19.14
@
text
@d392 1
a392 1
variables you established in step 3.
@


1.1.1.7
log
@import emacs-19.18
@
text
@d27 3
a29 6
Building Emacs requires about 30 Mb of disk space (including the Emacs
sources).  Once installed, Emacs occupies about 20 Mb in the file
system where it is installed; this includes the executable files, Lisp
libraries, miscellaneous data files, and on-line documentation.  If
the building and installation take place in different directories,
then the installation procedure momentarily requires 30+20 Mb.
a74 5
You can use `--srcdir' to build Emacs for several different machine
types from a single source directory.  Make separate build directories
for the different configuration types, and in each one, build Emacs
specifying the common source directory with `--srcdir'.

@


1.1.1.8
log
@import emacs-19.20
@
text
@d24 2
a25 2
loadup dump', found in `./src/Makefile.in.in', or possibly when
running the final dumped Emacs.
d390 11
a400 8
3) If you're going to use the make utility to build Emacs, you will
still need to run `configure' first, giving theappropriate values for
the variables in the sections entitled "Things `configure' Might Edit"
and "Where To Install Things."  Note that you may only need to change
the variables `prefix' and `exec_prefix', since the rest of the
variables have reasonable defaults based on them.  For each Makefile
variable of this type, there is a corresponding configure option; for
example, to change the location of the lock directory, you might use
d402 1
a402 1
	 ./configure --lockdir=/nfs/emacslock
d405 1
a405 1
copy `./build-ins.in' to `./build-install', and edit the
d408 1
d411 4
a414 4
autoconf can't meet, `configure.in' uses an marriage of custom-baked
configuration code and autoconf macros.  New versions of autoconf
could very well break this arrangement, so it may be wise to avoid
rebuilding `configure' from `configure.in' when possible.
d435 2
a436 2
assigning it a new build version number by incrementing the build
version stored in `./lisp/version.el'.
@


1.1.1.9
log
@import emacs-19.23
@
text
@d2 1
a2 1
Copyright (c) 1992, 1994 Free software Foundation, Inc.
a18 2
(This is for a Unix or Unix-like system.  For MSDOS, see below;
search for MSDOG.)
d27 1
a27 1
Building Emacs requires about 50 Mb of disk space (including the Emacs
d32 1
a32 1
then the installation procedure momentarily requires 50+20 Mb.
a61 3
You can specify toolkit operation when you configure Emacs; use the
option --with-x-toolkit.

d145 2
a146 6
5) Put into `./lisp/site-init.el' or `./lisp/site-load.el' any Emacs
Lisp code you want Emacs to load before it is dumped out.  Use
site-load.el for additional libraries if you arrange for their
documentation strings to be in the etc/DOC file (see
src/Makefile.in.in if you wish to figure out how to do that).  For all
else, use site-init.el.
d328 1
a328 1
	library.  Its default value, based on `datadir' (see above),
d335 1
a335 2
	`lispdir'.  Its default value, based on `datadir' (see above),
	is `/usr/local/lib/emacs/site-lisp'.
a497 15
Installation on MSDOG (a.k.a. MSDOS)

To install on MSDOG, you need to have the GNU C compiler (also known
as djgpp), GNU Make, rm, mv, chmod, and sed.  Type these commands:

config msdos
make install

To save disk space, Emacs is built in-place.  As the /usr/local/
subtree does not exist on most MSDOG systems, the executables are
placed in /emacs/bin/.

MSDOG is a not a multi-tasking operating system, so Emacs features
that depend on multitasking will not work.  Synchronous subprocesses
do work.
@


1.1.1.10
log
@import emacs-19.24
@
text
@a66 3
Note: on some systems, it does not work to use the toolkit with shared
libraries.

d162 2
a163 2
The `site-*.el' files are nonexistent in the distribution.  You do not
need to create them if you have nothing to put in them.
d462 1
a462 1
- The programs `cvtmail', `emacsserver', `fakemail', `hexl',
d510 2
a511 3
To install on MSDOG, you need to have the GNU C compiler for MSDOG
(also known as djgpp), GNU Make, rm, mv, chmod, and sed.  Type these
commands:
d516 7
a522 8
To save disk space, Emacs is built with the idea that you will execute
it from the same place in the file system where you built it.  As the
/usr/local/ subtree does not exist on most MSDOG systems, the
executables are placed in /emacs/bin/.

MSDOG is a not a multitasking operating system, so Emacs features such
as asynchronous subprocesses that depend on multitasking will not
work.  Synchronous subprocesses do work.
@


1.1.1.11
log
@import emacs-19.26
@
text
@d73 3
a75 8
locations they occupy while Emacs builds.  If you use `--run-in-place'
then you don't need to do `make install'.

`--run-in-place' is pretty much obsolete now.  If you put the Emacs
executable in a subdirectory named src, which has siblings named lisp,
lib-src, etc, info and so on, Emacs automatically uses those sibling
directories if the standard installation directory names don't contain
what Emacs needs.
d181 1
a181 2
		`emacs', `etags', `ctags', `b2m', `emacsclient',
		and `rcs-checkin'.
d386 1
a386 2
Instead of running the `configure' program, you have to perform the
following steps.
d403 10
a412 9
3) Create src/Makefile and lib-src/Makefile from the corresponding
`Makefile.in.in' files.  First copy `Makefile.in.in' to `Makefile.in',
then edit in appropriate substituions for the @@...@@ constructs,
and then copy the shell commands near the end of `configure'
that run cpp to construct `Makefile'.

4) Create `Makefile' files in various other directories
from the corresponding `Makefile.in' files.  This isn't so hard,
just a matter of substitution.
d414 1
a414 1
5) If you're going to use the build-install script to build Emacs,
d435 3
a437 3
2) Go to directory `./lib-src' and run `make'.  This creates
executables named `ctags' and `etags' and `wakeup' and `make-docfile'
and `digest-doc' and `test-distrib'.  And others.
d439 2
a440 2
3) Go to directory `./src' and Run `make'.  This refers to files in
the `./lisp' and `./lib-src' subdirectories using names `../lisp' and
d444 2
a445 2
which has another name that contains a version number.
Each time you do this, that version number increments in the last place.
d466 3
a468 3
    `movemail', `profile', `rcs2log', `timer', `vcdiff', `wakeup',
    and `yow' are used by Emacs; they do need to be copied.
- The programs `etags', `ctags', `emacsclient', `b2m', and `rcs-checkin'
d494 1
a494 1
`rcs-checkin' from `./lib-src' to `/usr/local/bin'.  These programs are
d501 2
a502 2
used by Emacs once it is built.  However, it is very desirable to keep
the source on line for debugging.
@


1.1.1.12
log
@import emacs-19.29
@
text
@d20 1
a20 1
search for MSDOG.  For Windows NT, see the file nt/install.)
d37 1
a37 1
give to the `configure' program.  That file offers hints for
d47 9
a55 6
system type; if it cannot, you must find the appropriate configuration
name in `./etc/MACHINES' and specify it explicitly.

If you don't want X support, specify `--with-x=no'.  If you omit this
option, `configure' will try to figure out for itself whether your
system has X, and arrange to use it if present.
d59 22
a80 10
object libraries used with the X Window System.  Normally, `configure'
is able to find them; these options are necessary if you have your X
Window System files installed in unusual places.  These options also
accept a list of directories, separated with colons.

To get more attractive menus, you can specify an X toolkit when you
configure Emacs; use the option `--with-x-toolkit=TOOLKIT', where
TOOLKIT is `athena' or `motif' (`yes' and `lucid' are synonyms for
`athena').  On some systems, it does not work to use a toolkit with
shared libraries.
d84 2
a85 2
`--with-gcc=no'.  If you omit this option, `configure' will search
for GCC in your path, and use it if present.
d87 8
a94 6
You can build Emacs for several different machine types from a single
source directory.  To do this, you must use a version of `make' that
supports the `VPATH' variable, such as GNU `make'.  Make separate
build directories for the different configuration types, and in each
one, run the Emacs `configure' script.  `configure' looks for the
Emacs source code in the directory that `configure' is in.
d100 2
a101 2
- The architecture-independent files go in PREFIXDIR/share/emacs/VERSION
  (where VERSION is the version number of Emacs, like `19.27').
d103 1
a103 1
  PREFIXDIR/libexec/emacs/VERSION/CONFIGURATION
d112 1
a112 1
  EXECDIR/libexec/emacs/VERSION/CONFIGURATION.
d122 4
a125 1
`configure' doesn't do any compilation or installation
d127 3
a129 4
`./Makefile', `lib-src/Makefile', `oldXMenu/Makefile',
`lwlib/Makefile', `src/Makefile', and `./src/config.h'.  For details
on exactly what it does, see the section called `CONFIGURATION BY
HAND', below.
d132 4
a135 9
creates a shell script `config.status' which, when run, recreates the
same configuration.  If `configure' exits with an error after
disturbing the status quo, it removes `config.status'.  `configure'
also creates a file `config.cache' that saves the results of its tests
to make reconfiguring faster, and a file `config.log' containing compiler
output (useful mainly for debugging `configure').  You can give
`configure' the option `--cache-file=FILE' to use the results of the
tests in FILE instead of `config.cache'.  Set FILE to `/dev/null' to
disable caching, for debugging `configure'.
d143 2
a144 2
for your system, set up the file `./lisp/site-init.el' with Emacs
Lisp code to override them; it is not a good idea to edit paths.el
a152 5
Before you override a variable this way, *look at the value* that the
variable gets by default!  Make sure you know what kind of value the
variable should have.  If you don't pay attention to what you are
doing, you'll make a mistake.

a164 4
If you set load-path to a different value in site-init.el or
site-load.el, Emacs will use *precisely* that value when it starts up
again.  If you do this, you are on your own!

d179 5
a183 8
building Emacs in the standard way.  The final executable file is
named `src/emacs'.  You can execute this file "in place" without
copying it, if you wish; then it automatically uses the sibling
directories ../lisp, ../lib-src, ../info.

Or you can "install" the executable and the other Emacs into their
installed locations, with `make install'.  By default, Emacs's files
are installed in the following directories:
d189 1
a189 1
`/usr/local/share/emacs/VERSION/lisp' holds the Emacs Lisp library;
d191 1
a191 1
		you are installing, like `18.59' or `19.27'.  Since the
d200 1
a200 1
		`/usr/local/share/emacs/site-lisp', then in this
d203 1
a203 1
`/usr/local/share/emacs/VERSION/etc' holds the Emacs tutorial, the DOC
d208 1
a208 1
`/usr/local/com/emacs/lock' contains files indicating who is editing
d212 1
a212 1
`/usr/local/libexec/emacs/VERSION/CONFIGURATION-NAME' contains executable
d247 1
a247 1
then you might need to make the movemail program setuid or setgid
d272 1
a272 1
	defaults to /usr/local/share.  We create the following
d284 1
a284 1
`sharedstatedir' indicates where to put architecture-independent data files
d286 2
a287 2
	/usr/local/com.  We create the following
	subdirectories under `sharedstatedir':
d292 3
a294 3
`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':
d326 1
a326 1
	`sharedstatedir', `infodir', and `mandir'.  Its default value is
d340 1
a340 1
	path variables - `bindir' and `libexecdir'.
d368 1
a368 1
	locking information.  Its default value, based on `sharedstatedir'
d373 1
a373 1
	while running.  Its default value, based on `libexecdir' (which
d420 4
d425 6
a430 1
program.  You need version 2.0 or newer of `autoconf' to rebuild `configure'.
d434 2
a435 2
Once Emacs is configured, running `make' in the top directory performs
the following steps.
d463 3
a465 2
The steps below are done by running `make install' in the main
directory of the Emacs distribution.
d476 1
a476 1
- The programs `make-docfile' and `test-distrib' were
d520 2
a521 1
(also known as djgpp), GNU Make, rm, mv, chmod, and sed.
d523 2
a524 20
Some users report that running Emacs 19.29 requires dpmi memory
management.  We do not know why this is so, since 19.28 did not need
it.  If we find out what change introduced this requirement, we will
try to eliminate it.  It is possible that this problem happens only
when there is not enough physical memory on the machine.

You can find out if you have a dpmi host by running go32 (part of
djgpp) without arguments; it will tell you if it uses dpmi memory.
For more information about dpmi memory, consult the djgpp FAQ.

To build and install Emacs, type these commands:

    config msdos
    make install

You may need to work around a type conflict between gmalloc.c and the
header file djgppstd.h regarding declarations of memalign and valloc.
Temporarily deleting those declarations from djgppstd.h while compiling
Emacs or while compiling gmalloc.c should do it.  We found out about this
problem too late to include a more convenient fix--sorry.
@


1.1.1.13
log
@import emacs-19.30
@
text
@d29 2
a30 2
Building Emacs requires about 70 Mb of disk space (including the Emacs
sources).  Once installed, Emacs occupies about 35 Mb in the file
d34 1
a34 1
then the installation procedure momentarily requires 70+35 Mb.
d144 5
d248 1
a248 5
10) You are done!  You can remove executables and object files from
the build directory by typing `make clean'.  To also remove the files
that `configure' created (so you can compile Emacs for a different
configuration), type `make distclean'.

d343 3
a345 3
`lispdir' indicates where Emacs installs and expects its lisp library.
	Its default value, based on `datadir' (see above), is
	`/usr/local/share/emacs/VERSION/lisp' (where `VERSION' is as
d352 1
a352 1
	is `/usr/local/share/emacs/site-lisp'.
d363 1
a363 1
	(which see), is `/usr/local/share/emacs/VERSION/etc'.
d366 2
a367 2
	locking information.  Its default value, based on
	`sharedstatedir' (which see), is `/usr/local/com/emacs/lock'.
d369 4
a372 4
`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'
@


1.1.1.14
log
@import emacs-19.31
@
text
@d19 2
a20 3

(This is for a Unix or Unix-like system.  For MSDOS, see below; search
for MSDOG.  For Windows NT or Windows 95, see the file nt/INSTALL.)
d26 1
a26 1
loadup dump', found in `./src/Makefile.in', or possibly when
d148 1
a148 1
src/Makefile.in if you wish to figure out how to do that).  For all
d185 1
a185 1
		Lisp library changes from one version of Emacs to
d188 7
a194 13
		at the same time; in particular, you don't have to
		make Emacs unavailable while installing a new version.

`/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'.
d231 1
a231 1
for its Lisp files by giving values for `make' variables as part of
d271 1
a271 1
	- `emacs/VERSION/lisp', containing the Emacs Lisp library, and
d342 1
a342 1
`lispdir' indicates where Emacs installs and expects its Lisp library.
d347 1
a347 1
`locallisppath' indicates where Emacs should search for Lisp files
d350 2
a351 2
	`lispdir'.  Its default value, based on `datadir' (see above), is
	`/usr/local/share/emacs/VERSION/site-lisp:/usr/local/share/emacs/site-lisp'.
d354 2
a355 2
	its Lisp files; its default value is the concatenation of
	`locallisppath' and `lispdir'.  It should be a colon-separated
d392 1
a392 1
1) Copy `./src/config.in' to `./src/config.h'.
d408 2
a409 2
`Makefile.in' files.  First copy `Makefile.in' to `Makefile.c',
then edit in appropriate substitutions for the @@...@@ constructs,
d426 1
a426 1
`./src/paths.h' from the template file `./src/paths.in', changing
d507 1
a507 13
(also known as djgpp), GNU Make, rm, mv, chmod, and sed.  See the
remarks in config.bat for more information about locations and
versions.

If you are compiling on an MSDOG-like system which has long file
names, you may need to do `SET LFN=y' for some of the commands,
especially the compilation commands.  It might be more convenient to
unpack the Emacs distribution with djtar, which comes with djgpp; if
you do `SET LFN=n' before unpacking, djtar truncates file names to 8.3
naming as it extracts files, even if the system allows long file
names, and this ensures that build procedures designed for 8.3 file
names still work.  Use djtar with the command `djtar -x foo.tar' or
`djtar -x foo.tgz'.
d511 3
a513 6
it.  If we find out what change introduced this requirement, we may
try to eliminate it.  ("May" because perhaps djgpp version 2's
improved dpmi handling means this is no longer a problem.)

It is possible that this problem happens only when there is not enough
physical memory on the machine.
d524 10
a533 13
Building Emacs creates executable files in the src and lib-src
directories.  Installing Emacs on MSDOS moves these executables to a
sibling directory called bin.  For example, if you build in directory
/emacs, installing moves the executables from /emacs/src and
/emacs/lib-src to the directory /emacs/bin, so you can then delete the
subdirectories /emacs/src and /emacs/lib-src if you wish.  The only
subdirectories you need to keep are bin, lisp, etc and info.

Emacs on MSDOS finds the lisp, etc and info directories by looking in
../lisp, ../etc and ../info, starting from the directory where the
Emacs executable was run from.  You can override this by setting the
environment variable HOME; if you do that, the directories lisp, etc
and info are accessed as subdirectories of the HOME directory.
@


1.1.1.15
log
@import emacs-19.32
@
text
@d514 28
a541 56
(also known as djgpp), GNU Make, rm, mv, and sed.  See the remarks in
config.bat for more information about locations and versions.  The
file etc/FAQ includes pointers to Internet sites where you can find
the necessary utilities; search for "MS-DOS".  The configuration step
(see below) will test for these utilities and will refuse to continue
if any of them isn't found.

If you are building the MSDOG version of Emacs on an MSDOG-like system
which supports long file names (e.g. Windows 95), you need to make
sure that long file names are handled consistently both when you
unpack the distribution and compile it.  If you intend to compile with
DJGPP v2.0 or later, and long file names support is enabled (LFN=y in
the environment), you need to unpack Emacs distribution in a way that
doesn't truncate the original long filenames to the DOS 8.3 namespace;
the easiest way to do this is to use djtar program which comes with
DJGPP, since it will note the LFN setting and behave accordingly.
DJGPP v1 doesn't support long filenames, so you must unpack Emacs with
a program that truncates the filenames to 8.3 naming as it extracts
files; again, using djtar after setting LFN=n is the recommended way.
You can build Emacs with LFN=n even if you use DJGPP v2, if some of
your tools don't support long file names: just ensure that LFN is set
to `n' during both unpacking and compiling.

(By the time you read this, you have already unpacked the Emacs
distribution, but if the explanations above imply that you should have
done it differently, it's safer to delete the directory tree created
by the unpacking program and unpack Emacs again, than to risk running
into problems during the build process.)

It is important to understand that the runtime support of long file
names by the Emacs binary is NOT affected by the LFN setting during
compilation; Emacs compiled with DJGPP v2.0 or later will always
support long file names on Windows 95 no matter what was the setting
of LFN at compile time.  However, if you compiled with LFN disabled
and want to enable LFN support after Emacs was already built, you need
to make sure that the support files in the lisp, etc and info
directories are called by their original long names as found in the
distribution.  You can do this either by renaming the files manually,
or by extracting them from the original distribution archive with
djtar after you set LFN=y in the environment.

To unpack Emacs with djtar, type this command:

    djtar -x emacs.tgz

(This assumes that the Emacs distribution is called `emacs.tgz' on
your system.)  There are a few files in the archive whose names
collide with other files under the 8.3 DOS naming.  On native MSDOS,
or if you have set LFN=n on Win95, djtar will ask you to supply
alternate names for these files; you can just press `Enter' when this
happens (which makes djtar skip these files) because they aren't
required for MS-DOS.

When unpacking is done, a directory called `emacs-XX.YY' will be
created, where XX.YY is the Emacs version.  To build and install
Emacs, chdir to that directory and type these commands:
d552 1
a552 4
subdirectories you need to keep are bin, lisp, etc and info.  The bin
subdirectory should be added to your PATH.  The msdos subdirectory
includes a PIF and an icon file for Emacs which you might find useful
if you run Emacs under MS Windows.
a562 6

The current version of djgpp 2.0 (as of August 1996) has two bugs that
affect Emacs.  We've included corrected versions of two files from
djgpp in the msdos subdirectory: is-exec.c and sigaction.c.  To work
around the bugs, compile these files and link them into temacs.  The
next version of djgpp should have these bugs fixed.
@


1.1.1.16
log
@import emacs-19.33
@
text
@d562 1
a562 1
or if you have set LFN=n on Windows 95, djtar will ask you to supply
d597 1
a597 1
djgpp in the msdos subdirectory: is_exec.c and sigaction.c.  To work
@


1.1.1.17
log
@import emacs-20.1
@
text
@d2 1
a2 1
Copyright (c) 1992, 1994, 1996, 1997 Free software Foundation, Inc.
a17 31
ADDITIONAL DISTRIBUTION FILES

* leim-M.N.tar.gz

The Emacs Lisp code for input methods for various international
character scripts is distributed in a separate tar file because of its
large size.  This file is called leim-M.N.tar.gz, with the same
version number as Emacs, and it unpacks into the directory
emacs-M.N/leim.  Thus, if you unpack it in the same directory where
you unpacked the Emacs distribution, it fills in a subdirectory
of the Emacs distribution.

If you have already unpacked the Leim tar file into a subdirectory of
the Emacs sources, building and installing Emacs automatically
installs the input method support as well.  If you unpack the Leim tar
file into the Emacs sources after building and installing Emacs, just
build Emacs again and install it again.

* intlfonts-VERSION.tar.gz

The intlfonts distribution contains X11 fonts that Emacs needs in
order to display international characters.  If you see a non-ASCII
character appear as a hollow box, that means you don't have a font for
it.  You might find a font in the intlfonts distribution.  If some
characters don't look right, or appear improperly aligned, a font
fron the intlfonts distribution might look better.

The intlfonts distribution contains its own installation instructions,
in the intlfonts/README file.


d41 2
a42 5
3) You can build Emacs in the top-level Emacs source directory
or in a separate directory.

3a) To build in the top-level Emacs source directory, go to that
directory and run the program `configure' as follows:
d73 6
a78 7
If you want the Emacs mail reader RMAIL to read mail from a POP
server, you must specify `--with-pop'.  This provides support for the
POP3 protocol; older versions are not supported.  For
Kerberos-authenticated POP add `--with-kerberos', for Hesiod support
add `--with-hesiod'.  These options enable Emacs to use POP; whether
Emacs uses POP is controlled by individual users--see the Rmail
chapter of the Emacs manual.
d125 3
a127 15
distribution, but using `configure' is easier.  See the section called
"CONFIGURATION BY HAND" below if you want to do the configuration
yourself.

3b) To build in a separate directory, go to that directory
and run the program `configure' as follows:

    SOURCE-DIR/configure CONFIGURATION-NAME [--OPTION[=VALUE]] ...

SOURCE-DIR refers to the top-level Emacs source directory which is
where Emacs's configure script is located.  `configure' looks for the
Emacs 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'.
d560 6
a565 1
your system.)
d588 2
a589 3
environment variables EMACSDATA (for the location of `etc' directory),
EMACSLOADPATH (for the location of `lisp' directory) and INFOPATH (for
the location of the `info' directory).
d595 5
a599 5
Version 2.0 of djgpp has two bugs that affect Emacs.  We've included
corrected versions of two files from djgpp in the msdos subdirectory:
is_exec.c and sigaction.c.  To work around the bugs, compile these
files and link them into temacs.  Djgpp version 2.01 have these bugs
fixed, so upgrade if you can before building Emacs.
@


1.1.1.18
log
@import emacs-20.3
@
text
@d43 1
a43 1
from the intlfonts distribution might look better.
d78 1
a78 1
    ./configure [CONFIGURATION-NAME] [--OPTION[=VALUE]] ...
d81 3
a83 6
in `./etc/MACHINES', with the system version number added at the end.

You should try first omitting CONFIGURATION-NAME.  This way,
`configure' will try to guess your system type.  If it cannot guess,
or if something goes wrong in building or installing Emacs this way,
try again specifying the proper CONFIGURATION-NAME explicitly.
a175 9
3c) Some people try to build in a separate directory by filling
it full of symlinks to the files in the real source directory.
If you do that, `make all' does work, but `make install' fails:
it copies the symbolic links rather than the actual files.

As far as is known, there is no particular reason to use
a directory full of links rather than use the standard GNU
facilities to build in a separate directory (see 3b above).

d206 1
a206 1
See `./etc/PROBLEMS' for more details on which systems this affects.
d394 27
a420 1
GNU software; this variable is specific to Emacs.
a435 5
The path for finding Lisp files is specified in src/paths.h,
a file which is generated by running configure.  To change the path,
you can edit the definition of PATH_LOADSEARCH in that file
before you run `make'.

d554 1
a554 1
See the file PROBLEMS in etc subdirectory for a list of various
@


1.1.1.19
log
@import emacs-20.4
@
text
@d23 12
a34 14
character scripts is distributed in a separate tar file because it
amounts to a significant fraction of the size of the distribution.
This tar file is called leim-M.N.tar.gz, with the same version number
as Emacs, and it unpacks into the directory emacs-M.N/leim.

You should unpack leim-M.N.tar.gz into the same directory where you
have previously unpacked the main Emacs distribution.  It fills in the
contents of one subdirectory, which is present in the main Emacs
distribution only in dummy form.

Once you have unpacked the Leim tar file into the Emacs source tree,
building and installing Emacs automatically installs the input method
support as well.  If you have built Emacs without unpacking Leim
first, just unpack Leim, build Emacs again, and install it again.
a44 5
The fonts in the intlfonts distribution are also used by the ps-print
package for printing international characters.  The file
lisp/ps-mule.el defines the .bdf font files required for printing
each character set.

d209 1
a209 2
else, use site-init.el.  Do not load byte-compiled code which
was build with a non-nil value of `byte-compile-dynamic'.
d267 4
d347 8
d520 4
a523 1
3) Copy `./src/emacs' to `/usr/local/bin', or to some other directory
d531 1
a531 1
4) Copy the programs `b2m', `emacsclient', `ctags', `etags', and
d535 1
a535 1
5) Copy the man pages in `./etc' for emacs, ctags, and etags into the
d538 1
a538 1
6) The files in the `./src' subdirectory, except for `emacs', are not
a599 16
If you need to type international characters, you will need to unpack
the Leim distribution (see the description near the beginning of this
file).  You unpack it from the same directory where you unpacked
Emacs.  To unpack Leim with djtar, assuming the Leim distribution is
called `leim.tgz', type this command:

    djtar -x leim.tgz

If you want to print international characters, install the intlfonts
distribution.  For this, create a directory called `fonts' under the
Emacs top-level directory (usually called `emacs-XX.YY') created by
unpacking emacs.tgz, chdir into the directory emacs-XX.YY/fonts, and
type this:

    djtar -x intlfonts.tgz

a606 12
To install the international fonts, chdir to the intlfonts-X.Y
directory created when you unpacked the intlfonts distribution (X.Y is
the version number of the fonts' distribution), and type the following
command:

    make bdf INSTALLDIR=..

After Make finishes, you may remove the directory intlfonts-X.Y; the
fonts are installed into the fonts/bdf subdirectory of the top-level
Emacs directory, and that is where Emacs will look for them by
default.

d613 4
a616 6
subdirectories you need to keep are bin, lisp, etc and info.  (If you
installed Leim, keep the leim subdirectory, and if you installed
intlfonts, keep the fonts directory and all its sibdirectories as well.)
The bin subdirectory should be added to your PATH.  The msdos
subdirectory includes a PIF and an icon file for Emacs which you might
find useful if you run Emacs under MS Windows.
@


1.1.1.20
log
@import emacs-21.0.103
@
text
@d2 1
a2 2
Copyright (c) 1992, 1994, 1996, 1997, 2000 Free software Foundation, Inc.
See the end of the file for copying permissions.
d4 5
d10 6
a15 91
BASIC INSTALLATION

The simplest way to build Emacs is to use the `configure' shell script
which attempts to guess correct values for various system-dependent
variables and features and find the directories where various system
headers and libraries are kept.  It then creates a `Makefile' in each
subdirectory and a `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 which
are supported by it.  If this simplified procedure fails, or if you
are using a platform such as MS-Windows, where `configure' script
doesn't work, you might need to use various non-default options, and
maybe perform some of the steps manually.  The more detailed
description in the rest of the sections of this guide will help you do
that, so please refer to them if the simple procedure does not work.

  1. If you want to be able to input international characters which
     your keyboard doesn't support directly (i.e. you cannot type
     them at the shell prompt), download the leim-M.N.tar.gz
     distribution and unpack it into the same directory where you have
     unpacked the main Emacs distribution.  See ADDITIONAL
     DISTRIBUTION FILES, below, for more about this.

  2. Make sure your system has at least 120 MB of free disk space.

  3a. `cd' to the directory where you unpacked Emacs and invoke the
      `configure' script:

		 ./configure

  3b. 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.

  4. 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 will have to pass to `configure'
     explicit machine configuration name, and one or more options
     which tell it where to find various headers and libraries; refer
     to DETAILED BUILDING AND INSTALLATION section below.

     If `configure' didn't find some image support libraries, such as
     Xpm, jpeg, etc., and you want to use them refer to the subsection
     "Image support libraries", below.

     If the details printed by `configure' don't make any sense to
     you, assume that `configure' did its job and proceed.

  5. If you need to run the `configure' script more than once (e.g.,
     with some non-default options), always clean the source
     directories before running `configure' again:

		make distclean 
		./configure

  6. Invoke the `make' program:

		 make

  7. 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

  8. 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 also save some space by compressing (with `gzip') Info files
  and installed Lisp source (.el) files which have corresponding .elc
  versions.
d23 4
a26 6
character scripts allows you to input characters in scripts which are
not directly supported by your keyboard. It is distributed in a
separate tar file because it amounts to a significant fraction of the
size of the distribution.  This tar file is called leim-M.N.tar.gz,
with the same version number as Emacs, and it unpacks into the
directory emacs-M.N/leim.
d43 3
a45 4
it.  You might find a font in the intlfonts distribution.  If you do
have a font for a non-ASCII character, but some characters don't look
right, or appear improperly aligned, a font from the intlfonts
distribution might look better.
d49 1
a49 1
lisp/ps-mule.el defines the *.bdf font files required for printing
a54 1
* elisp-manual-M.N.tar.gz
d56 4
a59 84
This distribution contains the Emacs Lisp Reference Manual which
complements the Emacs Manual.  (The Emacs Manual is accessible from
within the editor by typing "C-h i", then selecting the "Emacs" item
from the menu, or by clicking "Help" in the menu bar and selecting
"Read Emacs Manual".)  It is a good idea to install the Emacs Lisp
Reference Manual after installing Emacs, to complete the on-line
documentation of Emacs in Info.

If you have installed Texinfo, you can install the Emacs Lisp
Reference Manual this way (after unpacking the elisp-manual-M.N.tar.gz
file):

     cd elisp-manual-M.N
     ./configure --prefix=PREFIXDIR
     make install

Otherwise, you can install it manually.  Just copy the files elisp and
elisp-* from the elisp-manual-M.N directory to your site's info
directory (see the description of `infodir', below), and make sure
that file `dir' in this directory contains an entry like this:

    * Elisp: (elisp).	The Emacs Lisp Reference Manual.

* Image support libraries

Emacs needs optional libraries to be able to display images (with the
exception of PBM and XBM images whose support is built-in).

On some systems, particularly on GNU/Linux, these libraries may
already be present or available as additional packages.  Note that if
there is a separate `dev' or `devel' package, for use at compilation
time rather than run time, you will need that as well as the
corresponding run time package; typically the dev package will
contain header files and a library archive.  Otherwise, you can
download and build libraries from sources.  None of them are vital for
running Emacs; however, note that Emacs will not be able to use
colored icons in the toolbar if XPM support is not compiled in.

Here's the list of these optional libraries, and the URLs where they
can be found:

  . libXaw3d for fancy 3D-style 
      scroll bars:    ftp://ftp.x.org/contrib/widgets/Xaw3d/
  . libxpm for XPM:   ftp://ftp.x.org/contrib/libraries/
  . libpng for PNG:   ftp://www.libpng.org/pub/png/
  . libz (for PNG):   http://www.info-zip.org/pub/infozip/zlib/
  . libjpeg for JPEG: ftp://ftp.uu.net/graphics/jpeg/
                      Get version 6b -- 6a is reported to fail in
                      Emacs.
  . libtiff for TIFF: http://www.libtiff.org/
  . libungif for GIF: 
      http://prtr-13.ucsc.edu/~badger/software/libungif/index.shtml
      Ensure you get version 4.1.0b1 or higher of libungif -- a bug in
      4.1.0 can crash Emacs.

Emacs will configure itself to build with these libraries if the
`configure' script finds them on your system, unless you supply the
appropriate --without-LIB option.  In some cases, older versions of
these libraries won't work because some routines are missing, and
configure should avoid such old versions.  If that happens, use the
--without-LIB options to `configure'.  See below for more details.

* Extra fonts

To take proper advantage of Emacs 21's mule-unicode charsets, you need
a Unicode font.  For information on Unicode fonts for X, see
<URL:http://czyborra.com/unifont/>,
<URL:http://openlab.ring.gr.jp/efont/> and
<URL:http://www.cl.cam.ac.uk/%7Emgk25/ucs-fonts.html>.
<URL:http://czyborra.com/charsets/> has basic fonts for Emacs's
ISO-8859 charsets.

XFree86 release 4 (from <URL:ftp://ftp.xfree86.org/> and mirrors)
contains font support for most, if not all, of the charsets that Emacs
supports.  The font files should be usable separately with older X
releases.


DETAILED BUILDING AND INSTALLATION:

(This is for a Unix or Unix-like system.  For MS-DOS and Windows 3.X,
see below; search for MSDOG.  For Windows 9X, Windows ME, Windows NT,
and Windows 2000, see the file nt/INSTALL.  For the Mac, see the file
mac/INSTALL.)
d62 2
a63 2
a program whose pure code is 1.5 MB and whose data area is at
least 2.5 MB and can reach 80 MB or more.  If the swapping space is
d68 6
a73 7
Building Emacs requires about 95 MB of disk space (including the Emacs
sources), or 130 MB if Leim is used.  Once installed, Emacs occupies
about 60 MB (70 MB with Leim) in the file system where it is
installed; this includes the executable files, Lisp libraries,
miscellaneous data files, and on-line documentation.  If the building
and installation take place in different directories, then the
installation procedure momentarily requires 95+60 MB (130+70 MB).
d77 1
a77 4
getting around some possible installation problems.  The file lists
many different configurations, but only the part for your machine and
operating system is relevant.  (The list is arranged in alphabetical
order by the vendor name.)
d110 1
a110 7
shared libraries.  A free implementation of Motif, called LessTif, is
available ftom <http://www.lesstif.org>.  Compiling with LessTif or
Motif causes a standard File Selection Dialog to pop up when you type
"C-x C-f" and similar commands.  You can get fancy 3D-style scroll
bars, even without LessTif/Motif, if you have the Xaw3d library
installed (see "Image support libraries" above for Xaw3d
availability).
d117 7
a123 26
The Emacs mail reader RMAIL is configured to be able to read mail from
a POP3 server by default.  Versions of the POP protocol older than
POP3 are not supported.  For Kerberos-authenticated POP add
`--with-kerberos', for Hesiod support add `--with-hesiod'.  While POP3
is always enabled, whether Emacs actually uses POP is controlled by
individual users--see the Rmail chapter of the Emacs manual.

For image support you may have to download, build, and install the
appropriate image support libraries for image types other than XBM and
PBM, see the list of URLs in "ADDITIONAL DISTRIBUTION FILES" 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 one
or 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 support

Use --without-toolkit-scroll-bars to disable LessTif/Motif or Xaw3d
scroll bars.  --without-xim disables the use of X Input Methods, and
--disable-largefile omits support for files larger than 2GB on systems
which support that.
a168 31
If the description of the system configuration printed by `configure'
is not right, or if it claims some of the fatures or libraries are not
available when you know they are, look at the `config.log' file for
the trace of the failed tests performed by `configure' to check
whether these features are supported.  Typically, some test fails
because the compiler cannot find some function in the system
libraries, or some macro-processor definition in the system headers.

Some tests might fail because the compiler should look in special
directories for some header files, or link against optional
libraries, or use special compilation options.  You can force
`configure' and the build process which follows it to do that by
setting the variables CPPFLAGS, CFLAGS, LDFLAGS, LIBS, and CC before
running `configure'.  CPPFLAGS lists the options passed to the
preprocessor, CFLAGS are compilation options, LDFLAGS are options used
when linking, LIBS are libraries to link against, and CC is the
command which invokes the compiler.

Here's an example of a `configure' invocation, assuming a Bourne-like
shell 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 the
preprocessor to look in the `/foo/myinclude' directory for header
files (in addition to the standard directories), instruct the linker
to look in `/bar/mylib' for libraries, pass the -O3 optimization
switch to the compiler, and link against libfoo.a and libbar.a
libraries in addition to the standard ones.

d316 1
a316 5
configuration), type `make distclean'.  If you don't need some, or all
of the input methods from the Leim package, you can remove the
unneeded files in the leim/quail, leim/skk, and leim/skk-dic
subdirectories of your site's lisp directory (usually
/usr/local/share/emacs/VERSION/).
d459 1
a459 2
program.  You need version 2.8 or newer of `autoconf' to rebuild
`configure'.
a551 8
Recompiling Lisp files in the `lisp' subdirectory using the various
targets in the lisp/Makefile file requires additional utilities:
`find' and `xargs' (from Findutils), `touch' (from Fileutils) GNU
`echo' and `test' (from Sh-utils), `tr, `sort', and `uniq' (from
Textutils), and a port of Bash.  However, you should not normally need
to run lisp/Makefile, as all the Lisp files are distributed in
byte-compiled form as well.

d577 1
a577 1
support long file names on Windows 9X no matter what was the setting
a615 17
Running "config msdos" checks for several programs that are required
to configure and build Emacs; if one of those programs is not found,
CONFIG.BAT stops and prints an error message.  If you have DJGPP
version 2.0 or 2.01, it will complain about a program called
DJECHO.EXE.  These old versions of DJGPP shipped that program under
the name ECHO.EXE, so you can simply copy ECHO.EXE to DJECHO.EXE and
rerun CONFIG.BAT.  If you have neither ECHO.EXE nor DJECHO.EXE, you
should be able to find them in your djdevNNN.zip archive (where NNN is
the DJGPP version number).

On Windows NT or Windows 2000, running "config msdos" might print an
error message like "VDM has been already loaded".  This is because
those systems have a program called `redir.exe' which is incompatible
with a program by the same name supplied with DJGPP, which is used by
config.bat.  To resolve this, move the DJGPP's `bin' subdirectory to
the front of your PATH environment variable.

d636 1
a636 1
intlfonts, keep the fonts directory and all its subdirectories as well.)
d655 2
a656 17
files and link them into temacs.  Djgpp versions 2.01 and later have
these bugs fixed, so upgrade if you can before building Emacs.

COPYING PERMISSIONS

   Permission is granted to anyone to make or distribute verbatim copies
   of this document as received, in any medium, provided that the
   copyright notice and permission notice are preserved,
   and that the distributor grants the recipient permission
   for further redistribution as permitted by this notice.

   Permission is granted to distribute modified versions
   of this document, or of portions of it,
   under the above conditions, provided also that they
   carry prominent notices stating who last changed them,
   and that any new or changed statements about the activities
   of the Free Software Foundation are approved by the Foundation.
@


1.1.1.21
log
@import emacs-21.0.105
@
text
@a184 2
		      Get version 3.4k or later, which lets Emacs 
		      use its own color allocation functions.
@


1.1.1.22
log
@import emacs-21.3
@
text
@d2 1
a2 1
Copyright (c) 1992, 1994, 1996, 1997, 2000, 2001 Free software Foundation, Inc.
d24 6
a29 1
  1. Make sure your system has at least 120 MB of free disk space.
d31 3
a33 1
  2a. `cd' to the directory where you unpacked Emacs and invoke the
d38 1
a38 1
  2b. Alternatively, create a separate directory, outside the source
d47 1
a47 1
  3. When `configure' finishes, it prints several lines of details
d65 1
a65 1
  4. If you need to run the `configure' script more than once (e.g.,
d69 1
a69 1
		make distclean
d72 1
a72 1
  5. Invoke the `make' program:
d76 1
a76 1
  6. If `make' succeeds, it will build an executable program `emacs'
d82 1
a82 1
  7. Assuming that the program `src/emacs' starts and displays its
d101 20
d139 25
d182 1
a182 1
  . libXaw3d for fancy 3D-style
d185 1
a185 1
		      Get version 3.4k or later, which lets Emacs
d193 1
a193 1
  . libungif for GIF:
a206 3
At first, Emacs does not include fonts and does not install them.  You
must do this yourself.

a219 5
BDF fonts etl-unicode.tar.gz used by ps-print and ps-mule to print
Unicode characters are available from <URL:ftp://ftp.x.org/contrib/fonts/>
and <URL:ftp://ftp.xfree86.org/pub/X.Org/contrib/fonts/>.


d230 1
a230 1
least 2.8 MB and can reach 100 MB or more.  If the swapping space is
d234 8
a241 7

Building Emacs requires about 140 MB of disk space (including the
Emacs sources) Once installed, Emacs occupies about 77 MB in the file
system where it is installed; this includes the executable files, Lisp
libraries, miscellaneous data files, and on-line documentation.  If
the building and installation take place in different directories,
then the installation procedure momentarily requires 140+77 MB.
d279 1
a279 1
TOOLKIT is `athena', `motif' or `gtk' (`yes' and `lucid' are synonyms for
a288 5
If `--with-x-toolkit=gtk' is specified, you can tell configure where
to search for GTK by specifying `--with-pkg-config-prog=PATH' where
PATH is the pathname to pkg-config.  Note that GTK version 2.0 or
newer is required for Emacs.

d319 1
a319 1
which support that.  Use --without-sound to disable sound support.
d545 3
a547 2
unneeded files in the leim subdirectories of your site's lisp
directory (usually /usr/local/share/emacs/VERSION/).
d587 1
a587 1
		themselves.
d690 1
a690 1
program.  You need version 2.51 or newer of `autoconf' to rebuild
d731 1
a731 1
- The programs `cvtmail', `fakemail', `hexl',
d833 8
d892 5
a896 4
installed intlfonts, keep the fonts directory and all its
subdirectories as well.)  The bin subdirectory should be added to your
PATH.  The msdos subdirectory includes a PIF and an icon file for
Emacs which you might find useful if you run Emacs under MS Windows.
@


