xemacs-beta: INSTALL comparison

comparison INSTALL @ 357:4711e16a8e49 r21-1-8

Import from CVS: tag r21-1-8

author	cvs
date	Mon, 13 Aug 2007 10:57:04 +0200
parents	182f72e8cd0d
children	972bbb6d6ca2

comparison

equal deleted inserted replaced

-:e85f639a32f3
+:4711e16a8e49
-#!/bin/sh
-#
-# install - install a program, script, or datafile
-# This comes from X11R5.
-#
-# $XConsortium: install.sh,v 1.2 89/12/18 14:47:22 jim Exp $
-#
-# This script is compatible with the BSD install script, but was written
-# from scratch.
-#
-# set DOITPROG to echo to test this script
-# Don't use :- since 4.3BSD and earlier shells don't like it.
-doit="${DOITPROG-}"
-# put in absolute paths if you don't have them in your path; or use env. vars.
-mvprog="${MVPROG-mv}"
-cpprog="${CPPROG-cp}"
-chmodprog="${CHMODPROG-chmod}"
-chownprog="${CHOWNPROG-chown}"
-chgrpprog="${CHGRPPROG-chgrp}"
-stripprog="${STRIPPROG-strip}"
-rmprog="${RMPROG-rm}"
-mkdirprog="${MKDIRPROG-mkdir}"
-tranformbasename=""
-transform_arg=""
-instcmd="$mvprog"
-chmodcmd="$chmodprog 0755"
-chowncmd=""
-chgrpcmd=""
-stripcmd=""
-rmcmd="$rmprog -f"
-mvcmd="$mvprog"
-src=""
-dst=""
-dir_arg=""
-while [ x"$1" != x ]; do
-case $1 in
-	-c) instcmd="$cpprog"
-	    shift
-	    continue;;
-	-d) dir_arg=true
-	    shift
-	    continue;;
-	-m) chmodcmd="$chmodprog $2"
-	    shift
-	    shift
-	    continue;;
-	-o) chowncmd="$chownprog $2"
-	    shift
-	    shift
-	    continue;;
-	-g) chgrpcmd="$chgrpprog $2"
-	    shift
-	    shift
-	    continue;;
-	-s) stripcmd="$stripprog"
-	    shift
-	    continue;;
-	-t=*) transformarg=`echo $1 | sed 's/-t=//'`
-	    shift
-	    continue;;
-	-b=*) transformbasename=`echo $1 | sed 's/-b=//'`
-	    shift
-	    continue;;
-	*)  if [ x"$src" = x ]
-	    then
-		src=$1
-	    else
-		# this colon is to work around a 386BSD /bin/sh bug
-		:
-		dst=$1
-	    fi
-	    shift
-	    continue;;
-esac
-done
-if [ x"$src" = x ]
-then
-	echo "install:	no input file specified"
-	exit 1
-else
-	true
-fi
-if [ x"$dir_arg" != x ]; then
-	dst=$src
-	src=""
-	if [ -d $dst ]; then
-		instcmd=:
-	else
-		instcmd=mkdir
-	fi
-else
-# Waiting for this to be detected by the "$instcmd $src $dsttmp" command
-# might cause directories to be created, which would be especially bad
-# if $src (and thus $dsttmp) contains '*'.
-	if [ -f $src -o -d $src ]
-	then
-		true
-	else
-		echo "install:  $src does not exist"
-		exit 1
-	fi
-	if [ x"$dst" = x ]
-	then
-		echo "install:	no destination specified"
-		exit 1
-	else
-		true
-	fi
-# If destination is a directory, append the input filename; if your system
-# does not like double slashes in filenames, you may need to add some logic
-	if [ -d $dst ]
-	then
-		dst="$dst"/`basename $src`
-	else
-		true
-	fi
-fi
-## this sed command emulates the dirname command
-dstdir=`echo $dst | sed -e 's,[^/]*$,,;s,/$,,;s,^$,.,'`
-# Make sure that the destination directory exists.
-#  this part is taken from Noah Friedman's mkinstalldirs script
-# Skip lots of stat calls in the usual case.
-if [ ! -d "$dstdir" ]; then
-defaultIFS='
-'
-IFS="${IFS-${defaultIFS}}"
-oIFS="${IFS}"
-# Some sh's can't handle IFS=/ for some reason.
-IFS='%'
-set - `echo ${dstdir} | sed -e 's@/@%@g' -e 's@^%@/@'`
-IFS="${oIFS}"
-pathcomp=''
-while [ $# -ne 0 ] ; do
-	pathcomp="${pathcomp}${1}"
-	shift
-	if [ ! -d "${pathcomp}" ] ;
-then
-		$mkdirprog "${pathcomp}"
-	else
-		true
-	fi
-	pathcomp="${pathcomp}/"
-done
-fi
-if [ x"$dir_arg" != x ]
-then
-	$doit $instcmd $dst &&
-	if [ x"$chowncmd" != x ]; then $doit $chowncmd $dst; else true ; fi &&
-	if [ x"$chgrpcmd" != x ]; then $doit $chgrpcmd $dst; else true ; fi &&
-	if [ x"$stripcmd" != x ]; then $doit $stripcmd $dst; else true ; fi &&
-	if [ x"$chmodcmd" != x ]; then $doit $chmodcmd $dst; else true ; fi
-else
-# If we're going to rename the final executable, determine the name now.
-	if [ x"$transformarg" = x ]
-	then
-		dstfile=`basename $dst`
-	else
-		dstfile=`basename $dst $transformbasename |
-			sed $transformarg`$transformbasename
-	fi
-# don't allow the sed command to completely eliminate the filename
-	if [ x"$dstfile" = x ]
-	then
-		dstfile=`basename $dst`
-	else
-		true
-	fi
-# Make a temp file name in the proper directory.
-	dsttmp=$dstdir/#inst.$$#
-# Move or copy the file name to the temp name
-	$doit $instcmd $src $dsttmp &&
-	trap "rm -f ${dsttmp}" 0 &&
-# and set any options; do chmod last to preserve setuid bits
-# If any of these fail, we abort the whole thing.  If we want to
-# ignore errors from any of these, just make sure not to ignore
-# errors from the above "$doit $instcmd $src $dsttmp" command.
-	if [ x"$chowncmd" != x ]; then $doit $chowncmd $dsttmp; else true;fi &&
-	if [ x"$chgrpcmd" != x ]; then $doit $chgrpcmd $dsttmp; else true;fi &&
-	if [ x"$stripcmd" != x ]; then $doit $stripcmd $dsttmp; else true;fi &&
-	if [ x"$chmodcmd" != x ]; then $doit $chmodcmd $dsttmp; else true;fi &&
-# Now rename the file to the real destination.
-	$doit $rmcmd -f $dstdir/$dstfile &&
-	$doit $mvcmd $dsttmp $dstdir/$dstfile
-fi &&
-exit 0
 XEmacs Installation Guide
 Copyright (c) 1994, 1995, 1996 Board of Trustees, University of Illinois
-Copyright (c) 1994 Free Software Foundation, Inc.
+Copyright (c) 1994-1999 Free Software Foundation, Inc.
 Synched up with: FSF 19.30.
 Permission is granted to anyone to make or distribute verbatim copies
 of this document as received, in any medium, provided that the
 BUILDING AND INSTALLATION (Unix and Cygwin, see the file nt/README
 for instructions on building under Microsoft Windows):
 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
+least 400k and can reach 8Mb or more. Note that a typical XEmacs
+build is much bigger. If the swapping space is
 insufficient, you will get an error in the command `temacs -batch
 -l loadup dump', found in `./src/Makefile.in.in', or possibly when
 running the final dumped XEmacs.
-Building XEmacs requires about 41 Mb of disk space (including the
+Verify that your users have a high enough stack limit. On some
-XEmacs sources).  Once installed, XEmacs occupies about 16 Mb in the
+systems such as OpenBSD and OSF/Tru64 the default is 2MB which is
-file system where it is installed; this includes the executable files,
+too low. See 'PROBLEMS' for details.
-Lisp libraries, miscellaneous data files, and on-line documentation.
-The amount of storage of the Lisp directories may be reduced by
+Building XEmacs requires about 100 Mb of disk space (including the
-compressing the .el files. If the building and installation take place
+XEmacs sources).  Once installed, XEmacs occupies between 20 and 100 Mb
-in different directories, then the installation procedure temporarily
+in the file system where it is installed; this includes the executable files,
-requires 41+16 Mb.  Adjust this value upwards depending upon what
+Lisp libraries, miscellaneous data files, and on-line documentation. The
-additional Lisp support is installed.
+exact amount depends greatly on the number of extra lisp packages that are
+installed
 XEmacs requires an ANSI C compiler, such as GCC.  If you wish to build
 the documentation yourself, you will need at least version 1.68 of
 makeinfo (GNU texinfo-3.11).
 Use the --site-includes and --site-libraries options when building
 XEmacs to allow configure to find the external software packages.
 If you link with dynamic (``.so'') external package libraries, which
 is not recommended, you will also need to add the library directories
-to the --site-runtime-libraries option.
+to the --site-runtime-libraries option. For your convenience these can
+be set together by using the --with-site-prefix command. This will set
+these variables as needed assuming your libraries are organised as a
-3) Decide what Initial Lisp you need with XEmacs.  XEmacs is
+typical /usr tree.
-distributed separately from most of its runtime environment.  This is
+3) [N.B. Most of this section can be done during or after the
+compilation of the core source code, but is present early to catch
+your attention.]
+Decide what Initial Lisp you need with XEmacs. XEmacs is
+distributed separately from most of its runtime environment. This is
 done to make it easier for administrators to tune an installation for
-what the local users need.  See the file etc/PACKAGES for an overview
+what the local users need. Note that while XEmacs will compile and
-of what is available and which packages need to be installed prior to
+install without any packages present at least some additional lisp
-building XEmacs.  At this point you only need a minimum to get started
+packages are needed to bring XEmacs up to "normal" editor
-at which point you may install what you wish without further changes
+functionality. Installation and upgrading of the packages can be done
-to the XEmacs binary.  A sample minimum configuration for a Linux
+almost automatically when from inside XEmacs when it has been compiled
-system using Mule and Wnn6 from OMRON corporation would be the
+and installed.
-packages `mule-base' and `egg-its'.  By default, packages will be
-searched for in the path
+More information and suggestions for which packages to install see the
+file README.packages.
+IMPORTANT! The file README.packages contain information vital to have
+a fully working XEmacs. This information was not included in this file
+only because it is too large for this terse INSTALL.  Please read
+README.packages now!
+By default, packages will be searched for in the path
 ~/.xemacs::$prefix/lib/xemacs-${version}/mule-packages:$prefix/lib/xemacs/mule-packages:$prefix/lib/xemacs-${version}/xemacs-packages:$prefix/lib/xemacs/xemacs-packages
 This may be changed by specifying a different value with the
 --package-path configuration option.
 IMPORTANT NOTE: In a future version of XEmacs, the user-specific
 package hierarchy will move from ~/.xemacs to ~/.xemacs/packages.
 4) In the top level directory of the XEmacs distribution, run the
 program `configure' as follows:
 ./configure [CONFIGURATION-NAME] [--OPTION[=VALUE]] ...
 especially if your system's `mmap' implemntation is missing or
 inefficient.  Generally, it's best to go with the default
 configuration for your system.  You can tweak this based on how you
 use XEmacs, and the memory and cpu resources available on your system.
-The `--use-system-malloc' option can be use to either enable or
+The `--with-system-malloc' option can be use to either enable or
 disable use of the system malloc.  Generally, it's best to go with the
 default configuration for your system.  Note that on many systems
 using the system malloc disables the use of the relocating allocator.
-The `--use-debug-malloc' option can be used to link a special debugging
+The `--with-debug-malloc' option can be used to link a special debugging
 version of malloc.  Debug Malloc is not included with XEmacs, is
 intended for use only by the developers and may be obtained from
 <URL:http://www.letters.com/dmalloc/>.
 The `--debug' and `--error-checking' options are intended for use only
 When it is done, `configure' prints a description of what it did and
 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'.
-4) Look at `./lisp/paths.el'; if some of those values are not right
+5) Look at `./lisp/paths.el'; if some of those values are not right
 for your system, set up the file `./lisp/site-init.el' with XEmacs
 Lisp code to override them; it is not a good idea 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,
 canonical form.  XEmacs tries to detect how your automounter is
 configured.  If you have an unusual automounter configuration that
 XEmacs cannot detect, you may need to change the value of
 `directory-abbrev-alist'.
-5) Put into `./lisp/site-init.el' or `./lisp/site-load.el' any Emacs
+6) Put into `./lisp/site-init.el' or `./lisp/site-load.el' any Emacs
 Lisp code you want XEmacs 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 lib-src/DOC file (see
 src/Makefile.in.in if you wish to figure out how to do that).  For all
 else, use site-init.el.
 See `./PROBLEMS' for more details on which systems this affects.
 The `site-*.el' files are nonexistent in the distribution.  You do not
 need to create them if you have nothing to put in them.
-6) Refer to the file `./etc/TERMS' for information on fields you may
+7) 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 XEmacs distribution to finish
+8) Run `make' in the top directory of the XEmacs distribution to finish
 building XEmacs 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.
 install XEmacs's libraries and data files or where XEmacs 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) If your system uses lock files to interlock access to mailer inbox files,
+9) If your system uses lock files to interlock access to mailer inbox
-then you might need to make the movemail program setuid or setgid
+files, then you might need to make the movemail program setuid or
-to enable it to write the lock files.  We believe this is safe.
+setgid to enable it to write the lock files.  We believe this is safe.
 The setuid/setgid bits need not be set on any other XEmacs-related
 executables.
-9) You are done with the hard part!  You can remove executables and
+10) You are done with the hard part!  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 XEmacs
 for a different configuration), type `make distclean'.
-10) You should now go to the XEmacs web page at http://www.xemacs.org/
+11) You should now go to the XEmacs web page at http://www.xemacs.org/
 and decide what additional Lisp support you wish to have.
 MAKE VARIABLES
 You can change where the build process installs XEmacs and its data
 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
+3) 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 XEmacs, you will
+4) If you're going to use the make utility to build XEmacs, you will
 still need to run `configure' first, giving 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.  For each Makefile
 debugging.
 PROBLEMS
+The most likely problem is that you forgot to read and follow the
+directions in README.packages.  You can not have a working XEmacs
+without downloading some additional packages.
 See the file PROBLEMS in this directory for a list of various
 problems sometimes encountered, and what to do about them.
 If all else fails, please see etc/InstallGuide courtesy

Mercurial > hg > xemacs-beta

comparison INSTALL @ 357:4711e16a8e49 r21-1-8