|
0
|
1 XEmacs Installation Guide
|
|
|
2 Copyright (c) 1994, 1995, 1996 Board of Trustees, University of Illinois
|
|
|
3 Copyright (c) 1994 Free Software Foundation, Inc.
|
|
|
4
|
|
70
|
5 Synched up with: FSF 19.30.
|
|
|
6
|
|
0
|
7 Permission is granted to anyone to make or distribute verbatim copies
|
|
|
8 of this document as received, in any medium, provided that the
|
|
|
9 copyright notice and permission notice are preserved,
|
|
|
10 and that the distributor grants the recipient permission
|
|
|
11 for further redistribution as permitted by this notice.
|
|
|
12
|
|
|
13 Permission is granted to distribute modified versions
|
|
|
14 of this document, or of portions of it,
|
|
|
15 under the above conditions, provided also that they
|
|
|
16 carry prominent notices stating who last changed them,
|
|
|
17 and that any new or changed statements about the activities
|
|
|
18 of the Free Software Foundation are approved by the Foundation.
|
|
|
19
|
|
|
20
|
|
253
|
21 BUILDING AND INSTALLATION (Unix and Cygwin, see the file nt/README
|
|
|
22 for instructions on building under Microsoft Windows):
|
|
0
|
23
|
|
|
24 1) Make sure your system has enough swapping space allocated to handle
|
|
149
|
25 a program whose pure code is 900k bytes and whose data area is at
|
|
|
26 least 400k and can reach 8Mb or more. If the swapping space is
|
|
|
27 insufficient, you will get an error in the command `temacs -batch
|
|
|
28 -l loadup dump', found in `./src/Makefile.in.in', or possibly when
|
|
|
29 running the final dumped XEmacs.
|
|
0
|
30
|
|
243
|
31 Building XEmacs requires about 41 Mb of disk space (including the
|
|
|
32 XEmacs sources). Once installed, XEmacs occupies about 16 Mb in the
|
|
149
|
33 file system where it is installed; this includes the executable files,
|
|
|
34 Lisp libraries, miscellaneous data files, and on-line documentation.
|
|
|
35 The amount of storage of the Lisp directories may be reduced by
|
|
|
36 compressing the .el files. If the building and installation take place
|
|
|
37 in different directories, then the installation procedure temporarily
|
|
243
|
38 requires 41+16 Mb. Adjust this value upwards depending upon what
|
|
|
39 additional Lisp support is installed.
|
|
149
|
40
|
|
255
|
41 XEmacs requires an ANSI C compiler, such as GCC. If you wish to build
|
|
|
42 the documentation yourself, you will need at least version 1.68 of
|
|
|
43 makeinfo (GNU texinfo-3.11).
|
|
149
|
44
|
|
|
45
|
|
|
46 2) Decide on what other software packages you would like to use with
|
|
|
47 XEmacs, but are not yet available on your system. On some systems,
|
|
|
48 Motif and CDE are optional additions. On Solaris, the SUNWaudmo
|
|
|
49 package enables native sound support. There are also a number of free
|
|
|
50 software packages that XEmacs can use. If these are not yet available
|
|
|
51 on your system, obtain, build and install those external packages
|
|
|
52 before building XEmacs. The packages XEmacs can use are:
|
|
0
|
53
|
|
149
|
54 Xaw3d, XPM, JPEG, compface, PNG, zlib, OffiX, GNU DBM, Berkeley DB,
|
|
243
|
55 socks, term, NAS, Canna, Kinput2, SJ3, Wnn.
|
|
149
|
56
|
|
|
57 You can get (most of) them from the XEmacs ftp site at
|
|
243
|
58 ftp://ftp.xemacs.org/pub/xemacs/aux
|
|
0
|
59
|
|
149
|
60 If you want users on other systems to be able to use the XEmacs you
|
|
|
61 have built, try to build those packages so that the generated
|
|
|
62 libraries are statically linked.
|
|
|
63
|
|
|
64 Use the --site-includes and --site-libraries options when building
|
|
201
|
65 XEmacs to allow configure to find the external software packages.
|
|
|
66 If you link with dynamic (``.so'') external package libraries, which
|
|
|
67 is not recommended, you will also need to add the library directories
|
|
|
68 to the --site-runtime-libraries option.
|
|
149
|
69
|
|
0
|
70
|
|
243
|
71 3) Decide what Initial Lisp you need with XEmacs. XEmacs is distributed
|
|
|
72 separately from most of its runtime environment. This is done to make it
|
|
|
73 easier for administrators to tune an installation for what the local users
|
|
|
74 need. See the file etc/PACKAGES for an overview of what is available and
|
|
|
75 which packages need to be installed prior to building XEmacs. At this
|
|
|
76 point you only need a minimum to get started at which point you may install
|
|
|
77 what you wish without further changes to the XEmacs binary. A sample
|
|
|
78 minimum configuration for a Linux system using Mule and Wnn6 from OMRON
|
|
|
79 corporation would be the packages `mule-base' and `egg-its'. By default,
|
|
|
80 packages will be searched for in the directory $prefix/lib/xemacs/packages.
|
|
|
81 This may be changed by specifying a different value with the --package-path
|
|
|
82 configuration option. Multiple directories may be specified.
|
|
|
83
|
|
|
84
|
|
|
85 4) In the top level directory of the XEmacs distribution, run the
|
|
149
|
86 program `configure' as follows:
|
|
0
|
87
|
|
149
|
88 ./configure [CONFIGURATION-NAME] [--OPTION[=VALUE]] ...
|
|
0
|
89
|
|
243
|
90 Almost always, you should let `configure' (actually the shell script
|
|
|
91 `config.guess') guess your host type, by omitting the
|
|
149
|
92 CONFIGURATION-NAME argument. If you like to experiment, specify a
|
|
|
93 configuration name in the form MACHINE-VENDOR-OPSYS, for example:
|
|
|
94
|
|
|
95 sparc-sun-solaris2.6
|
|
|
96
|
|
|
97 See config.guess and configure.in for valid values for MACHINE,
|
|
|
98 VENDOR, and OPSYS. Also check `./etc/MACHINES' for advice on building
|
|
|
99 on particular machines.
|
|
0
|
100
|
|
|
101 If you don't want X support, specify `--with-x=no'. If you omit this
|
|
149
|
102 option, `configure' will try to autodetect whether your system has X,
|
|
|
103 and arrange to use it if present.
|
|
0
|
104
|
|
|
105 The `--x-includes=DIR' and `--x-libraries=DIR' options tell the build
|
|
|
106 process where the compiler should look for the include files and
|
|
|
107 object libraries used with the X Window System. Normally, `configure'
|
|
|
108 is able to find them; these options are necessary if you have your X
|
|
|
109 Window System files installed in unusual places.
|
|
|
110
|
|
|
111 The `--site-includes=DIR' and `--site-libraries=DIR' options allow you
|
|
|
112 to specify additional places the compiler should look for include
|
|
|
113 files and object libraries. You may specify multiple DIR's by
|
|
149
|
114 enclosing the list in quotes. All the external packages you want to
|
|
|
115 use with XEmacs (e.g. xpm, wnn, ...) described later should have their
|
|
|
116 include and library directories defined using these options.
|
|
|
117
|
|
201
|
118 The `--site-runtime-libraries=DIR' option specifies directories to
|
|
|
119 search for shared libraries at run time. This may be necessary if you
|
|
|
120 link with dynamic libraries that are installed in non-standard
|
|
|
121 directories, or if you expect some of the libraries used to build
|
|
|
122 XEmacs to be in a different directory at run time than at build time.
|
|
|
123 Usually this will add a `-R' to each directory specified and use that
|
|
|
124 when linking XEmacs. If you use this option, you must specify ALL of
|
|
|
125 the directories containing shared libraries at run time, including
|
|
|
126 system directories.
|
|
|
127
|
|
|
128 Rationale: Some people think that directories in --site-libraries
|
|
|
129 should be automatically used to update --site-runtime-libraries.
|
|
|
130 Here's a real-life scenario that explains why this is not done: You
|
|
|
131 build binaries for your company using static libs in
|
|
|
132 /net/toy/hack/lib. XEmacs adds /net/toy/hack/lib to the runpath of
|
|
|
133 the executable you've built. Since there are only static libs there,
|
|
|
134 the system runtime loader will look in this dir, and ignore it,
|
|
|
135 causing only a .01 second delay in starting XEmacs. You leave the
|
|
|
136 company for a job at a small Silicon Valley startup. Time passes.
|
|
|
137 The next guy who inherits your machine objects to working on a machine
|
|
|
138 named `toy', and gets the sysadmin to rename the machine `godzilla'.
|
|
|
139 The SA forgets to remove the old entry for `toy' from the hosts file.
|
|
|
140 Now the system loader will still try to access /net/toy/, and the
|
|
|
141 automounter will hang trying to access /net/toy. XEmacs suddenly
|
|
|
142 takes 30 seconds longer to start up, no one can figure out why, and
|
|
|
143 everyone at your old company curses your name, thinking that you've
|
|
|
144 put a time bomb into XEmacs. And they're right!
|
|
0
|
145
|
|
|
146 The `--with-gcc' option specifies that the build process should
|
|
149
|
147 compile XEmacs using GCC. The `--compiler' option allows you to
|
|
|
148 specify some other compiler to be used to compile XEmacs. If neither
|
|
|
149 option is specified, the environment variable CC is used instead.
|
|
|
150 Otherwise the compiler will then default to 'cc'.
|
|
0
|
151
|
|
|
152 The `--cflags' option specifies the CFLAGS the build process should
|
|
149
|
153 use when compiling XEmacs. Otherwise the value of the environment
|
|
|
154 variable CFLAGS is consulted. If that is also undefined, CFLAGS
|
|
|
155 defaults to "-g -O" for gcc and "-g" for all other compilers.
|
|
0
|
156
|
|
|
157 The `--with-gnu-make' option specifies that Makefiles should be
|
|
|
158 written to take advantage of special features of GNU Make. GNU Make
|
|
|
159 works fine on Makefiles even without this option. This flag just
|
|
|
160 allows for simultaneous in-place and --srcdir building.
|
|
|
161
|
|
|
162 The `--dynamic' option specifies that configure should try to link
|
|
|
163 emacs dynamically rather than statically.
|
|
|
164
|
|
|
165 The `--const-is-losing' option is for use if you have trouble
|
|
|
166 compiling due to the `const' storage class in C. This is defined by
|
|
|
167 default. Most users should have no need to change this.
|
|
|
168
|
|
|
169 You can build XEmacs for several different machine types from a single
|
|
|
170 source directory. To do this, you must use a version of `make' that
|
|
|
171 supports the `VPATH' variable, such as GNU `make'. Make separate
|
|
|
172 build directories for the different configuration types, and in each
|
|
|
173 one, run the XEmacs `configure' script. `configure' looks for the
|
|
|
174 Emacs source code in the directory that `configure' is in.
|
|
|
175
|
|
|
176 The `--prefix=PREFIXDIR' option specifies where the installation process
|
|
|
177 should put XEmacs and its data files. This defaults to `/usr/local'.
|
|
|
178 - XEmacs (and the other utilities users run) go in PREFIXDIR/bin
|
|
|
179 (unless the `--exec-prefix' option says otherwise).
|
|
|
180 - The architecture-independent files go in PREFIXDIR/lib/xemacs-VERSION
|
|
227
|
181 (where VERSION is the version number of XEmacs, like `20.5').
|
|
0
|
182 - The architecture-dependent files go in
|
|
243
|
183 PREFIXDIR/lib/xemacs-VERSION/CONFIGURATION-NAME
|
|
|
184 (where CONFIGURATION-NAME is the host type, like mips-dec-ultrix4.2),
|
|
0
|
185 unless the `--exec-prefix' option says otherwise.
|
|
|
186
|
|
|
187 The `--exec-prefix=EXECDIR' option allows you to specify a separate
|
|
|
188 portion of the directory tree for installing architecture-specific
|
|
|
189 files, like executables and utility programs. If specified,
|
|
|
190 - XEmacs (and the other utilities users run) go in EXECDIR/bin, and
|
|
|
191 - The architecture-dependent files go in
|
|
243
|
192 EXECDIR/lib/xemacs-VERSION/CONFIGURATION-NAME.
|
|
0
|
193 EXECDIR/bin should be a directory that is normally in users' PATHs.
|
|
|
194
|
|
|
195 For example, the command
|
|
|
196
|
|
149
|
197 ./configure mips-dec-ultrix --with-x11=yes
|
|
0
|
198
|
|
|
199 configures XEmacs to build for a DECstation running Ultrix, with
|
|
|
200 support for the X11 window system.
|
|
|
201
|
|
|
202 The `--with-menubars=TYPE' option allows you to specify which X
|
|
|
203 toolkit you wish to use for the menubar. The valid options are
|
|
149
|
204 `lucid', `motif' and `no'. The default is `lucid' which is a
|
|
0
|
205 Motif-lookalike menubar. We highly recommend its usage over the real
|
|
|
206 Motif menubar. (In fact, the Motif menubar is currently broken.) If
|
|
149
|
207 `no' is specified then support for menubars will not be compiled in.
|
|
0
|
208
|
|
|
209 The `--with-scrollbars=TYPE' option allows you to specify which X
|
|
|
210 toolkit you wish to use for the scrollbars. The valid options are
|
|
149
|
211 `lucid', `motif', `athena', `athena3d', and `no'. The default is
|
|
|
212 `lucid' which is a Motif-lookalike scrollbar. If `no' is specified
|
|
104
|
213 then support for scrollbars will not be compiled in.
|
|
0
|
214
|
|
|
215 The `--with-dialogs=TYPE' option allows you to specify which X toolkit
|
|
219
|
216 you wish to use for the dialog boxes. The valid options are `athena',
|
|
243
|
217 `athena3d', `motif, and `no. The `lucid' option is accepted and will
|
|
|
218 result in the `athena' toolkit being used. If the Motif toolkit can be
|
|
|
219 found the default is `motif'. Otherwise, the default is `athena'. If
|
|
149
|
220 `no' is specified then support for dialog boxes will not be compiled
|
|
0
|
221 in.
|
|
|
222
|
|
|
223 The `--with-toolbars' option allows you to enable or disable toolbar
|
|
|
224 support. The default is `yes' as long as support for a windowing
|
|
|
225 system is included.
|
|
|
226
|
|
149
|
227 The `--with-xpm' option specifies that XEmacs should support X11
|
|
0
|
228 Pixmaps. `configure' will attempt to detect if you have the Xpm
|
|
|
229 libraries and define `--with-xpm' for you.
|
|
|
230
|
|
|
231 The `--with-xface' option specifies that XEmacs should support
|
|
|
232 X-Faces. `configure' will attempt to detect if you have the compface
|
|
|
233 library and define `--with-xface' for you.
|
|
|
234
|
|
|
235 The `--with-database' option specifies that XEmacs should be built
|
|
|
236 with additional database support. The valid options are `no' or a
|
|
|
237 comma-separated list of one or more of `dbm', `gnudbm' or `berkdb'.
|
|
|
238 `configure' will attempt to detect the necessary libraries and header
|
|
|
239 files and define `--with-database' for you.
|
|
|
240
|
|
|
241 The `--with-socks' option specifies that XEmacs should be built with
|
|
149
|
242 SOCKS support. This requires the libsocks library.
|
|
0
|
243
|
|
|
244 The `--with-tooltalk' option specifies that XEmacs should be built
|
|
|
245 with ToolTalk support for interconnecting with other applications.
|
|
243
|
246 ToolTalk is not yet supported on all architectures. If you use this
|
|
|
247 option, you should have the tooltalk package (see etc/PACKAGES)
|
|
|
248 installed prior to building XEmacs.
|
|
0
|
249
|
|
|
250 The `--with-sparcworks' option specifies that XEmacs should be built
|
|
149
|
251 with support for Sun Sparcworks 3.0.1 and up (including Sun WorkShop).
|
|
|
252 This functionality is only of use on SunOS 4.1.x and Solaris 2.x
|
|
243
|
253 systems. If you use this option, you should have the Sun package (see
|
|
|
254 etc/PACKAGES) installed prior to building XEmacs.
|
|
0
|
255
|
|
149
|
256 The `--with-cde' option allows you to enable or disable CDE drag and
|
|
0
|
257 drop support. `configure' will attempt to detect this option and
|
|
|
258 define `--with-cde' for you.
|
|
|
259
|
|
149
|
260 The `--with-offix' option allows you to enable or disable OffiX drag and
|
|
2
|
261 drop support. `configure' will attempt to detect this option and
|
|
|
262 define `--with-offix' for you.
|
|
|
263
|
|
0
|
264 The `--external-widget' option specifies that XEmacs should be built
|
|
149
|
265 with support for being used as a widget by other X11 applications.
|
|
|
266 This functionality should be considered beta.
|
|
0
|
267
|
|
|
268 The `--with-xmu=no' option can be used if your vendor doesn't ship
|
|
|
269 the Xmu library.
|
|
|
270
|
|
|
271 The `--puresize' option can be used to change the amount of purespace
|
|
104
|
272 allocated for the dumped XEmacs. As of XEmacs 20.1 usage of this
|
|
243
|
273 parameter is deprecated and will be ignored.
|
|
0
|
274
|
|
|
275 The `--with-sound=TYPE' option specifies that XEmacs should be built
|
|
|
276 with sound support. Native (`--with-sound=native') sound support is
|
|
|
277 currently available only on Sun SparcStations, SGI's, HP9000s, and
|
|
149
|
278 systems (such as Linux) with soundcard.h. Network Audio Support (NAS)
|
|
|
279 (`--with-sound=nas' or `--with-sound=both') is an extension to X that
|
|
|
280 you may or may not have for your system. For NAS, you will probably
|
|
|
281 need to provide the paths to the nas include and library directories
|
|
|
282 to configure. If `--with-sound' is not specified, `configure' will
|
|
|
283 attempt to determine if your configuration supports native sound and
|
|
0
|
284 define --with-sound for you. If your native sound library is not in a
|
|
149
|
285 standard location you can specify it with the `--native-sound-lib=LIB'
|
|
|
286 flag. For Linux, `/dev/audio' is required for SunAudio files and
|
|
|
287 `/dev/dsp' is required for raw data and WAVE format files.
|
|
0
|
288
|
|
|
289 The `--rel-alloc' option can be used to either enable or disable use
|
|
151
|
290 of the relocating allocator. Turning on --rel-alloc will allow XEmacs
|
|
|
291 to return unused memory to the operating system, thereby reducing its
|
|
|
292 memory footprint. However, it may make XEmacs runs more slowly,
|
|
|
293 especially if your system's `mmap' implemntation is missing or
|
|
|
294 inefficient. Generally, it's best to go with the default
|
|
|
295 configuration for your system. You can tweak this based on how you
|
|
|
296 use XEmacs, and the memory and cpu resources available on your system.
|
|
0
|
297
|
|
|
298 The `--use-system-malloc' option can be use to either enable or
|
|
149
|
299 disable use of the system malloc. Generally, it's best to go with the
|
|
|
300 default configuration for your system. Note that on many systems
|
|
|
301 using the system malloc disables the use of the relocating allocator.
|
|
0
|
302
|
|
177
|
303 The `--use-debug-malloc' option can be used to link a special debugging
|
|
|
304 version of malloc. Debug Malloc is not included with XEmacs, is
|
|
|
305 intended for use only by the developers and may be obtained from
|
|
|
306 <URL:http://www.letters.com/dmalloc/>.
|
|
|
307
|
|
0
|
308 The `--debug' and `--error-checking' options are intended for use only
|
|
|
309 by the developers. `--debug' adds code to be compiled in for
|
|
|
310 performing various tests. `--error-checking' adds additional tests to
|
|
|
311 many of the commonly used macros.
|
|
|
312
|
|
|
313 The `--verbose' and `--extra-verbose' options are intended for use
|
|
|
314 only by the developers. `--verbose' causes the results of all
|
|
149
|
315 configure tests to be displayed. `--extra-verbose' displays
|
|
|
316 additional information, useful for debugging. Another help for
|
|
|
317 determining configure failures is the file `config.log', which
|
|
|
318 contains the results of the compile and link tests used by configure.
|
|
|
319
|
|
|
320 The `--with-mule' option enables (MUlti-Lingual Emacs) support, needed
|
|
|
321 to suport non-Latin-1 (including Asian) languages. The Mule support
|
|
243
|
322 is not yet as stable or efficient as the `Latin1' support. Enabling
|
|
|
323 Mule support requires the mule-base package installed prior to
|
|
|
324 building XEmacs. The following options require Mule support:
|
|
149
|
325
|
|
|
326 The `--with-xim' option enables use of the X11 XIM mechanism to allow
|
|
|
327 an input method to input text into XEmacs. The input method is shared
|
|
|
328 among all the X applications sharing an X display and using the same
|
|
151
|
329 language. The XIM support comes in two flavors: `motif' and `xlib'.
|
|
|
330 The Motif support (the XmIm* functions) is preferred when available.
|
|
243
|
331 The xlib XIM support works reasonably well so long as the X11 libraries
|
|
|
332 are recent enough. It has been fairly well tested on Linux with glibc
|
|
|
333 2.0.5 and 2.0.6 and Kinput2 as an XIM server. In this configuration
|
|
|
334 X11 must be recompiled with X_LOCALE defined because glibc is lacking
|
|
|
335 localization for Japanese. The XIM support defaults to `no' except
|
|
|
336 when Motif is detected where it is stable with OSF libraries. The XIM
|
|
|
337 support in Lesstif (a Free Motif replacement) does not work as of
|
|
|
338 v0.82. If you enable this option, you will probably wish to install
|
|
|
339 the `locale' package which contains localized Splash screens and
|
|
|
340 Menubars.
|
|
|
341
|
|
|
342 The `--with-xfs' option enables use of a multilingual Menubar. At the
|
|
|
343 present time, only Japanese and French locales are supported. In
|
|
|
344 order to use a multilingual Menubar you must have the `locale' package
|
|
|
345 installed. The `locale' package does not have to be installed when
|
|
|
346 building XEmacs.
|
|
149
|
347
|
|
|
348 The `--with-canna' option enables the use of the Canna Japanese input
|
|
243
|
349 method. This is stable code and fairly well tested. In order to use
|
|
|
350 it, you will have to have the Canna server installed and running.
|
|
|
351 Canna versions 3.2pl2 and 3.5b2 are known to work. Version 3.2pl2 is
|
|
|
352 considered most stable than version 3.5b2. If Canna is already
|
|
|
353 installed, configure will autodetect it, so you never need to
|
|
|
354 explicitly use this option unless your Canna libraries are somewhere
|
|
|
355 strange. Canna run time support is currently bundled with the
|
|
|
356 `mule-base' package so there is nothing additional to install in order
|
|
|
357 to use it.
|
|
0
|
358
|
|
243
|
359 The `--with-wnn' and `--with-wnn6' options are for compiling with the Wnn
|
|
|
360 multi-language input method. `--with-wnn' is for compiling with Wnn-4.2,
|
|
|
361 the Free version of WNN. `--with-wnn6' is for compiling against WNN6,
|
|
|
362 the commercial version of WNN available from OMRON Corporation. This is
|
|
|
363 stable code and fairly well tested. In order to build with this
|
|
|
364 option, you will need to have the `egg-its' lisp package already
|
|
|
365 installed.
|
|
|
366
|
|
|
367 Please note that it is safe to build with as many of the options
|
|
|
368 `--with-xim', `--with-canna' and `--with-wnn' as your system
|
|
|
369 supports.
|
|
104
|
370
|
|
149
|
371 `configure' doesn't do any compilation or installation itself. It
|
|
|
372 just creates the files that influence those things: `./src/config.h',
|
|
|
373 and all the Makefile's in the build tree.
|
|
104
|
374
|
|
126
|
375 The `--with-pop', `--with-hesiod', and `--with-kerberos' options are used
|
|
|
376 in conjunction with movemail. As of XEmacs 20.1, movemail is identical
|
|
|
377 to the one used in Emacs.
|
|
|
378
|
|
0
|
379 When it is done, `configure' prints a description of what it did and
|
|
|
380 creates a shell script `config.status' which, when run, recreates the
|
|
|
381 same configuration. If `configure' exits with an error after
|
|
|
382 disturbing the status quo, it removes `config.status'.
|
|
|
383
|
|
|
384 4) Look at `./lisp/paths.el'; if some of those values are not right
|
|
|
385 for your system, set up the file `./lisp/site-init.el' with XEmacs
|
|
|
386 Lisp code to override them; it is not a good idea to edit paths.el
|
|
|
387 itself. YOU MUST USE THE LISP FUNCTION `setq' TO ASSIGN VALUES,
|
|
|
388 rather than `defvar', as used by `./lisp/paths.el'. For example,
|
|
|
389
|
|
|
390 (setq news-inews-program "/usr/bin/inews")
|
|
|
391
|
|
|
392 is how you would override the default value of the variable
|
|
|
393 news-inews-program (which is "/usr/local/inews").
|
|
|
394
|
|
|
395 Before you override a variable this way, *look at the value* that the
|
|
|
396 variable gets by default! Make sure you know what kind of value the
|
|
|
397 variable should have. If you don't pay attention to what you are
|
|
|
398 doing, you'll make a mistake.
|
|
|
399
|
|
|
400 Things may malfunction if the variable `directory-abbrev-alist' is not set
|
|
|
401 up to translate "temporary" automounter mount points into the canonical
|
|
|
402 form. The default value of this variable contains the translation
|
|
|
403
|
|
|
404 ("^/tmp_mnt/" . "/")
|
|
|
405
|
|
|
406 meaning translate "/tmp_mnt/net/FOO" into "/net/FOO", which is appropriate
|
|
|
407 for the default configuration of the Sun automounter, but which may be
|
|
|
408 inappropriate for different vendor's automounters, or if you have customized
|
|
|
409 your mount-point names.
|
|
|
410
|
|
|
411 5) Put into `./lisp/site-init.el' or `./lisp/site-load.el' any Emacs
|
|
|
412 Lisp code you want XEmacs to load before it is dumped out. Use
|
|
|
413 site-load.el for additional libraries if you arrange for their
|
|
|
414 documentation strings to be in the lib-src/DOC file (see
|
|
|
415 src/Makefile.in.in if you wish to figure out how to do that). For all
|
|
|
416 else, use site-init.el.
|
|
|
417
|
|
|
418 If you set load-path to a different value in site-init.el or
|
|
|
419 site-load.el, XEmacs will use *precisely* that value when it starts up
|
|
|
420 again. If you do this, you are on your own!
|
|
|
421
|
|
|
422 Note that, on some systems, the code you place in site-init.el must
|
|
|
423 not use expand-file-name or any other function which may look
|
|
|
424 something up in the system's password and user information database.
|
|
|
425 See `./PROBLEMS' for more details on which systems this affects.
|
|
|
426
|
|
|
427 The `site-*.el' files are nonexistent in the distribution. You do not
|
|
|
428 need to create them if you have nothing to put in them.
|
|
|
429
|
|
|
430 6) Refer to the file `./etc/TERMS' for information on fields you may
|
|
|
431 wish to add to various termcap entries. The files `./etc/termcap.ucb'
|
|
|
432 and `./etc/termcap.dat' may already contain appropriately-modified
|
|
|
433 entries.
|
|
|
434
|
|
|
435 7) Run `make' in the top directory of the XEmacs distribution to finish
|
|
|
436 building XEmacs in the standard way. The final executable file is
|
|
|
437 named `src/emacs'. You can execute this file "in place" without
|
|
|
438 copying it, if you wish; then it automatically uses the sibling
|
|
|
439 directories ../lisp, ../lib-src, ../info.
|
|
|
440
|
|
|
441 Or you can "install" the executable and the other XEmacs into their
|
|
|
442 installed locations, with `make install'. By default, XEmacs's files
|
|
|
443 are installed in the following directories:
|
|
|
444
|
|
|
445 By default, XEmacs installs its files in the following directories:
|
|
|
446
|
|
|
447 `/usr/local/bin' holds the executable programs users normally run -
|
|
|
448 `xemacs', `etags', `ctags', `b2m', `emacsclient',
|
|
|
449 `gnuclient', `gnudoit', `gnuattach', and `rcs-checkin'.
|
|
|
450
|
|
|
451 `/usr/local/lib/xemacs-VERSION/lisp' holds the Emacs Lisp libraries;
|
|
|
452 `VERSION' stands for the number of the XEmacs version
|
|
|
453 you are installing, like `18.59' or `19.14'. Since
|
|
|
454 the lisp libraries change from one version of XEmacs to
|
|
|
455 another, including the version number in the path
|
|
|
456 allows you to have several versions of XEmacs installed
|
|
|
457 at the same time; this means that you don't have to
|
|
|
458 make XEmacs unavailable while installing a new version.
|
|
|
459
|
|
|
460 XEmacs searches for its lisp files in these
|
|
|
461 directories, and then in
|
|
|
462 `/usr/local/lib/xemacs/site-lisp/*'.
|
|
|
463
|
|
|
464 `/usr/local/lib/xemacs-VERSION/etc' holds the XEmacs tutorial, the
|
|
|
465 `yow' database, and other architecture-independent
|
|
|
466 files XEmacs might need while running. VERSION is as
|
|
|
467 specified for `.../lisp'.
|
|
|
468
|
|
|
469 `/usr/local/lib/xemacs/lock' contains files indicating who is
|
|
|
470 editing what, so XEmacs can detect editing clashes
|
|
|
471 between users.
|
|
|
472
|
|
|
473 `/usr/local/lib/xemacs-VERSION/CONFIGURATION-NAME' contains executable
|
|
|
474 programs used by XEmacs that users are not expected to
|
|
|
475 run themselves, and the DOC file. `VERSION' is the
|
|
|
476 number of the XEmacs version you are installing, and
|
|
243
|
477 `CONFIGURATION-NAME' is the host type of your system.
|
|
|
478 Since these files are specific to the version of
|
|
|
479 XEmacs, operating system, and architecture in use,
|
|
|
480 including the configuration name in the path allows
|
|
|
481 you to have several versions of XEmacs for any mix of
|
|
|
482 machines and operating systems installed at the same
|
|
|
483 time; this is useful for sites at which different
|
|
|
484 kinds of machines share the file system XEmacs is
|
|
|
485 installed on.
|
|
0
|
486
|
|
|
487 `/usr/local/lib/xemacs-VERSION/info' holds the on-line documentation
|
|
|
488 for XEmacs, known as "info files".
|
|
|
489
|
|
|
490 `/usr/local/man/man1' holds the man pages for the programs installed
|
|
|
491 in `/usr/local/bin'.
|
|
|
492
|
|
|
493 If these directories are not what you want, you can specify where to
|
|
|
494 install XEmacs's libraries and data files or where XEmacs should search
|
|
|
495 for its lisp files by giving values for `make' variables as part of
|
|
|
496 the command. See the section below called `MAKE VARIABLES' for more
|
|
|
497 information on this.
|
|
|
498
|
|
|
499 8) If your system uses lock files to interlock access to mailer inbox files,
|
|
|
500 then you might need to make the movemail program setuid or setgid
|
|
|
501 to enable it to write the lock files. We believe this is safe.
|
|
|
502 The setuid/setgid bits need not be set on any other XEmacs-related
|
|
|
503 executables.
|
|
|
504
|
|
243
|
505 9) You are done with the hard part! You can remove executables and
|
|
|
506 object files from the build directory by typing `make clean'. To also
|
|
|
507 remove the files that `configure' created (so you can compile XEmacs
|
|
|
508 for a different configuration), type `make distclean'.
|
|
0
|
509
|
|
243
|
510 10) You should now go to the XEmacs web page at http://www.xemacs.org/
|
|
|
511 and decide what additional Lisp support you wish to have.
|
|
0
|
512
|
|
|
513 MAKE VARIABLES
|
|
|
514
|
|
|
515 You can change where the build process installs XEmacs and its data
|
|
|
516 files by specifying values for `make' variables as part of the `make'
|
|
|
517 command line. For example, if you type
|
|
|
518
|
|
|
519 make install bindir=/usr/local/gnubin
|
|
|
520
|
|
|
521 the `bindir=/usr/local/gnubin' argument indicates that the XEmacs
|
|
|
522 executable files should go in `/usr/local/gnubin', not
|
|
|
523 `/usr/local/bin'.
|
|
|
524
|
|
|
525 Here is a complete list of the variables you may want to set.
|
|
|
526
|
|
|
527 `bindir' indicates where to put executable programs that users can
|
|
|
528 run. This defaults to /usr/local/bin.
|
|
|
529
|
|
|
530 `datadir' indicates where to put the architecture-independent
|
|
|
531 read-only data files that XEmacs refers to while it runs; it
|
|
|
532 defaults to /usr/local/lib. We create the following
|
|
|
533 subdirectories under `datadir':
|
|
|
534 - `xemacs-VERSION/lisp', containing the XEmacs lisp libraries, and
|
|
|
535
|
|
|
536 - `xemacs-VERSION/etc', containing the XEmacs tutorial and the
|
|
|
537 `yow' database.
|
|
|
538 `VERSION' is the number of the XEmacs version you are installing,
|
|
|
539 like `18.59' or `19.14'. Since these files vary from one version
|
|
|
540 of XEmacs to another, including the version number in the path
|
|
|
541 allows you to have several versions of XEmacs installed at the
|
|
|
542 same time; this means that you don't have to make XEmacs
|
|
|
543 unavailable while installing a new version.
|
|
|
544
|
|
|
545 `statedir' indicates where to put architecture-independent data files
|
|
|
546 that XEmacs modifies while it runs; it defaults to
|
|
|
547 /usr/local/lib as well. We create the following
|
|
|
548 subdirectories under `statedir':
|
|
|
549 - `xemacs/lock', containing files indicating who is editing
|
|
|
550 what, so XEmacs can detect editing clashes between
|
|
|
551 users.
|
|
|
552
|
|
|
553 `libdir' indicates where to put architecture-specific data files that
|
|
|
554 XEmacs refers to as it runs; it too defaults to `/usr/local/lib'.
|
|
|
555 We create the following subdirectories under `libdir':
|
|
|
556 - `xemacs-VERSION/CONFIGURATION-NAME', containing executable
|
|
|
557 programs used by XEmacs that users are not expected to run
|
|
|
558 themselves and the DOC file.
|
|
|
559 `VERSION' is the number of the XEmacs version you are installing,
|
|
243
|
560 and `CONFIGURATION-NAME' is the host type of your system.
|
|
|
561 Since these files are specific to the version of XEmacs,
|
|
|
562 operating system, and architecture in use, including the
|
|
|
563 configuration name in the path allows you to have several
|
|
|
564 versions of XEmacs for any mix of machines and operating
|
|
|
565 systems installed at the same time; this is useful for sites
|
|
|
566 at which different kinds of machines share the file system
|
|
|
567 XEmacs is installed on.
|
|
0
|
568
|
|
|
569 `infodir' indicates where to put the info files distributed with
|
|
|
570 XEmacs; it defaults to `/usr/local/lib/xemacs-VERSION/info'.
|
|
|
571
|
|
|
572 `mandir' indicates where to put the man pages for XEmacs and its
|
|
|
573 utilities (like `etags'); it defaults to
|
|
|
574 `/usr/local/man/man1'.
|
|
|
575
|
|
|
576 `prefix' doesn't give a path for any specific part of XEmacs; instead,
|
|
|
577 its value is used to determine the defaults for all the
|
|
|
578 architecture-independent path variables - `datadir',
|
|
|
579 `statedir', `infodir', and `mandir'. Its default value is
|
|
|
580 `/usr/local'; the other variables add on `lib' or `man' to it
|
|
|
581 by default.
|
|
|
582
|
|
|
583 For example, suppose your site generally places GNU software
|
|
|
584 under `/usr/users/software/gnusoft' instead of `/usr/local'.
|
|
|
585 By including
|
|
|
586 `prefix=/usr/users/software/gnusoft'
|
|
|
587 in the arguments to `make', you can instruct the build process
|
|
|
588 to place all of the XEmacs data files in the appropriate
|
|
|
589 directories under that path.
|
|
|
590
|
|
|
591 `exec_prefix' serves the same purpose as `prefix', but instead
|
|
|
592 determines the default values for the architecture-dependent
|
|
|
593 path variables - `bindir' and `libdir'.
|
|
|
594
|
|
|
595 The above variables serve analogous purposes in the makefiles for all
|
|
|
596 GNU software; here are some variables specific to XEmacs.
|
|
|
597
|
|
|
598 `lispdir' indicates where XEmacs installs and expects its lisp
|
|
|
599 libraries. Its default value, based on `datadir' (see above),
|
|
|
600 is `/usr/local/lib/xemacs-VERSION/lisp' (where `VERSION' is as
|
|
|
601 described above).
|
|
|
602
|
|
|
603 `sitelispdir' indicates where XEmacs should search for lisp libraries
|
|
|
604 specific to your site. XEmacs checks them in order before
|
|
|
605 checking `lispdir'. Its default value, based on `datadir'
|
|
|
606 (see above), is `/usr/local/lib/xemacs/site-lisp'.
|
|
|
607
|
|
|
608 `etcdir' indicates where XEmacs should install and expect the rest of
|
|
|
609 its architecture-independent data, like the tutorial and yow
|
|
|
610 database. Its default value, based on `datadir'
|
|
|
611 (see above), is `/usr/local/lib/xemacs-VERSION/etc' (where
|
|
|
612 `VERSION' is as described above).
|
|
|
613
|
|
|
614 `lockdir' indicates the directory where XEmacs keeps track of its
|
|
|
615 locking information. Its default value, based on `statedir'
|
|
|
616 (see above), is `/usr/local/lib/xemacs/lock'.
|
|
|
617
|
|
|
618 `archlibdir' indicates where XEmacs installs and expects the
|
|
|
619 executable files and other architecture-dependent data it uses
|
|
|
620 while running. Its default value, based on `libdir' (see
|
|
|
621 above), is `/usr/local/lib/xemacs-VERSION/CONFIGURATION-NAME'
|
|
|
622 (where VERSION and CONFIGURATION-NAME are as described above).
|
|
|
623
|
|
|
624 Remember that you must specify any variable values you need each time
|
|
|
625 you run `make' in the top directory. If you run `make' once to build
|
|
|
626 xemacs, test it, and then run `make' again to install the files, you
|
|
|
627 must provide the same variable settings each time. To make the
|
|
|
628 settings persist, you can edit them into the `Makefile' in the top
|
|
|
629 directory, but be aware that running the `configure' program erases
|
|
|
630 `Makefile' and rebuilds it from `Makefile.in'.
|
|
|
631
|
|
|
632 The top-level Makefile stores the variable settings it used in the
|
|
|
633 Makefiles for the subdirectories, so you don't have to specify them
|
|
|
634 when running make in the subdirectories.
|
|
|
635
|
|
|
636
|
|
|
637 CONFIGURATION BY HAND
|
|
|
638
|
|
|
639 Instead of running the `configure' program, you have to perform the
|
|
|
640 following steps.
|
|
|
641
|
|
|
642 1) Copy `./src/config.h.in' to `./src/config.h'.
|
|
|
643
|
|
|
644 2) Consult `./etc/MACHINES' to see what configuration name you should
|
|
|
645 use for your system. Look at the code of the `configure' script to
|
|
|
646 see which operating system and architecture description files from
|
|
|
647 `src/s' and `src/m' should be used for that configuration name. Edit
|
|
|
648 `src/config.h', and change the two `#include' directives to include
|
|
|
649 the appropriate system and architecture description files.
|
|
|
650
|
|
|
651 2) Edit `./src/config.h' to set the right options for your system. If
|
|
|
652 you need to override any of the definitions in the s/*.h and m/*.h
|
|
|
653 files for your system and machine, do so by editing config.h, not by
|
|
|
654 changing the s/*.h and m/*.h files. Occasionally you may need to
|
|
|
655 redefine parameters used in `./lib-src/movemail.c'.
|
|
|
656
|
|
|
657 3) If you're going to use the make utility to build XEmacs, you will
|
|
|
658 still need to run `configure' first, giving the appropriate values for
|
|
|
659 the variables in the sections entitled "Things `configure' Might Edit"
|
|
|
660 and "Where To Install Things." Note that you may only need to change
|
|
|
661 the variables `prefix' and `exec_prefix', since the rest of the
|
|
|
662 variables have reasonable defaults based on them. For each Makefile
|
|
|
663 variable of this type, there is a corresponding configure option; for
|
|
|
664 example, to change the location of the lock directory, you might use
|
|
|
665
|
|
|
666 ./configure --lockdir=/nfs/xemacslock
|
|
|
667
|
|
|
668 The `configure' script is built from `configure.in' by the `autoconf'
|
|
|
669 program. However, since XEmacs has configuration requirements that
|
|
185
|
670 autoconf can't meet, `configure.in' uses a marriage of custom-baked
|
|
0
|
671 configuration code and autoconf macros. New versions of autoconf
|
|
|
672 could very well break this arrangement, so it may be wise to avoid
|
|
|
673 rebuilding `configure' from `configure.in' when possible.
|
|
|
674
|
|
|
675
|
|
|
676 BUILDING XEMACS BY HAND
|
|
|
677
|
|
|
678 Once XEmacs is configured, running `make' in the top directory performs
|
|
|
679 the following steps.
|
|
|
680
|
|
|
681 1) Run `make src/paths.h' in the top directory. This produces
|
|
|
682 `./src/paths.h' from the template file `./src/paths.h.in', changing
|
|
|
683 the paths to the values specified in `./Makefile'.
|
|
|
684
|
|
|
685 2) Cd to `./lib-src' and run `make'. This creates executables named
|
|
|
686 `ctags' and `etags' and `wakeup' and `make-docfile' and `digest-doc'
|
|
|
687 and `test-distrib'. And others.
|
|
|
688
|
|
|
689 3) Cd to `./src' and Run `make'. This refers to files in the `./lisp'
|
|
|
690 and `./lib-src' subdirectories using names `../lisp' and
|
|
|
691 `../lib-src'.
|
|
|
692
|
|
|
693 This creates a file `./src/xemacs' which is the runnable XEmacs,
|
|
|
694 assigning it a new build version number by incrementing the build
|
|
|
695 version stored in `./lisp/version.el'.
|
|
|
696
|
|
|
697 It also creates a file in `./lib-src' whose name is `DOC' followed by
|
|
|
698 the current XEmacs version. This file contains documentation strings
|
|
|
699 for all the functions in XEmacs. Each time you run make to make a new
|
|
|
700 xemacs, a new DOC file with a new name is made. You must keep the DOC
|
|
|
701 file for an XEmacs version as long as you keep using that XEmacs
|
|
|
702 version.
|
|
|
703
|
|
|
704
|
|
|
705 INSTALLATION BY HAND
|
|
|
706
|
|
|
707 The steps below are done by running `make install' in the main
|
|
|
708 directory of the XEmacs distribution.
|
|
|
709
|
|
|
710 1) Copy `./lisp' and its subdirectories, `./etc', and the executables
|
|
|
711 in `./lib-src' to their final destinations, as selected in `./src/paths.h'.
|
|
|
712
|
|
|
713 Strictly speaking, not all of the executables in `./lib-src' need be copied.
|
|
|
714 - The programs `cvtmail', `emacsserver', `env', `fakemail', `hexl',
|
|
|
715 `movemail', `timer', `vcdiff', `wakeup', and `yow' are used by
|
|
|
716 XEmacs; they do need to be copied.
|
|
|
717 - The programs `etags', `ctags', `emacsclient', `b2m', `rcs2log',
|
|
|
718 `gnuclient', `gnudoit', and `gnuattach' are intended to be run
|
|
|
719 by users; they are handled below.
|
|
|
720 - The programs `make-docfile' and `test-distrib' were
|
|
|
721 used in building XEmacs, and are not needed any more.
|
|
|
722 - The programs `digest-doc' and `sorted-doc' convert a `DOC' file into
|
|
|
723 a file for users to read. There is no important reason to move them.
|
|
|
724
|
|
|
725 2) Copy the files in `./info' to the place specified in
|
|
|
726 `./lisp/site-init.el' or `./lisp/paths.el'. Note that if the
|
|
|
727 destination directory already contains a file named `dir', you
|
|
|
728 probably don't want to replace it with the `dir' file in the XEmacs
|
|
|
729 distribution. Instead, you should make sure that the existing `dir'
|
|
|
730 file contains an appropriate menu entry for the XEmacs info.
|
|
|
731
|
|
|
732 3) Create a directory for XEmacs to use for clash detection, named as
|
|
|
733 indicated by the PATH_LOCK macro in `./src/paths.h'.
|
|
|
734
|
|
|
735 4) Copy `./src/xemacs' to `/usr/local/bin', or to some other directory
|
|
|
736 in users' search paths. `./src/xemacs' has an alternate name
|
|
|
737 `./src/emacs-EMACSVERSION'; you may wish to make a symbolic link named
|
|
|
738 `/usr/local/bin/xemacs' pointing to that alternate name, as an easy way
|
|
|
739 of installing different versions.
|
|
|
740
|
|
|
741 You can delete `./src/temacs'.
|
|
|
742
|
|
|
743 5) Copy the programs `b2m', `emacsclient', `ctags', `etags', `rcs2log',
|
|
|
744 `gnuclient', `gnudoit', and `gnuattach' from `./lib-src' to
|
|
|
745 `/usr/local/bin'. These programs are intended for users to run.
|
|
|
746
|
|
|
747 6) Copy the man pages in `./etc' for xemacs, ctags, etags, and gnuserv
|
|
|
748 into the appropriate man directories.
|
|
|
749
|
|
|
750 7) The files in the `./src' subdirectory, except for `xemacs', are not
|
|
|
751 used by XEmacs once it is built. The source would be handy for
|
|
|
752 debugging.
|
|
|
753
|
|
|
754
|
|
|
755 PROBLEMS
|
|
|
756
|
|
|
757 See the file PROBLEMS in this directory for a list of various
|
|
|
758 problems sometimes encountered, and what to do about them.
|
|
70
|
759
|
|
|
760
|
|
179
|
761 If all else fails, please see etc/InstallGuide courtesy
|
|
|
762 of Jonathan Seth Hayward.
|
