
This directory contains Linux 1.x executables for Lucid Emacs 19.10.
These were compiled with gcc 2.5,8, libc 4.5.26, Athena 3d widgets, 
XPM 3.4a,  Xfree 2.1.1, full optimization, and are statically linked.
Note that the bin/i486-unknown-linux/lemacs-19.10 is BIG because it was 
compiled with -g.  To strip symbol table out, cd to the bin directory and 
mv lemacs-19.10 lemacs-19.10-big
install -s lemacs-19.10-big lemacs-19.10

The tar file which contains these executables contains only the
executables (the architecture-dependent files.)  To use these
executables, you will also need the architecture-independent files
(the `lisp' and `etc' directories.)  These files are distributed
in a seperate file (lemacs-19.10-common.tar.gz.)

HOW TO INSTALL
==============

Simply cd to the directory in which you wish to install lemacs,
and then unpack the architecture independent tar file, followed by
the architecture-dependent files for those architectures you use.

  cd /usr/local/	# or wherever you install 3rd-party software
  gzip -dc lemacs-19.10-common.tar.gz | tar -xf -
  gzip -dc lemacs-19.10-i486-unknown-linux.tar.gz | tar -xf -

Replace `/usr/local/' with what you like, but it probably ought not
have `lemacs' or a version number in it - that directory is expected
to be the common prefix for installed software, and lemacs-specific
subdirectories of it will be created.  The directories are arranged
in such a way that multiple versions of lemacs can peaceably coexist
under the same `/usr/local/' tree.

After unpacking, you will have a directory structure like:

  ./bin/i486-unknown-linux/lemacs-19.10*	executable
  ./lib/lemacs-19.10/lisp/			lisp library
  ./lib/lemacs-19.10/etc/			data directory
  ./lib/lemacs-19.10/info/			documentation
  ./lib/lemacs-19.10/i486-unknown-linux/	utility programs
  ./lib/lemacs/lock/				lock directory
  ./lib/lemacs/site-lisp/			local lisp code

For the executable to work, the directory layout must look pretty
much like this; the executable looks for "sibling" directories at
run-time to figure out where its lisp library is.  These constraints
on the local directory layout are necessary to avoid having to
hardcode pathnames into the executables, or require that environment
variables be set before running the executable.

It is possible to do a multi-architecture in such a way that the
executables for the various architectures are on different
partitions; in that case you must install some symbolic links so
that the directory structure appears as above from the clients.

For example, assume that $LOCAL refers to a directory which is
mounted only on machines of the same type; and $SHARED refers to
a directory which is shared among all machines.  You could set up
the directory hierarchy like this:

  $LOCAL/bin/lemacs-19.10*
  $LOCAL/lib/lemacs-19.10/i486-unknown-linux/
  $LOCAL/lib/lemacs-19.10/lisp@  ->  $SHARED/lemacs-19.10/lisp/
  $LOCAL/lib/lemacs-19.10/etc@   ->  $SHARED/lemacs-19.10/etc/
  $LOCAL/lib/lemacs-19.10/info@  ->  $SHARED/lemacs-19.10/info/
  $LOCAL/lib/lemacs@             ->  $SHARED/lemacs/

  $SHARED/lemacs-19.10/lisp/
  $SHARED/lemacs-19.10/etc/
  $SHARED/lemacs-19.10/info/
  $SHARED/lemacs/lock/
  $SHARED/lemacs/site-lisp/

That is, the various $SHARED directories contain only the
architecture-independent files, but still look like normal
installation trees, since the architecture-independent
directories have been replaced with symbolic links to the 
single $COMMON tree.


This binary distribution was built with care by:

Tibor Polgar
tlp00@spg.amdahl.com
