0
|
1 XEmacs Installation Guide
|
1338
|
2
|
0
|
3 Copyright (c) 1994, 1995, 1996 Board of Trustees, University of Illinois
|
1338
|
4 Copyright (c) 1994-1999, 2003 Free Software Foundation, Inc.
|
412
|
5
|
0
|
6 Permission is granted to anyone to make or distribute verbatim copies
|
|
7 of this document as received, in any medium, provided that the
|
|
8 copyright notice and permission notice are preserved,
|
|
9 and that the distributor grants the recipient permission
|
|
10 for further redistribution as permitted by this notice.
|
|
11
|
|
12 Permission is granted to distribute modified versions
|
|
13 of this document, or of portions of it,
|
|
14 under the above conditions, provided also that they
|
|
15 carry prominent notices stating who last changed them,
|
|
16 and that any new or changed statements about the activities
|
|
17 of the Free Software Foundation are approved by the Foundation.
|
|
18
|
442
|
19 BUILDING AND INSTALLATION FOR UNIX AND CYGWIN
|
|
20
|
|
21 (for Microsoft Windows, see nt/README also.)
|
|
22
|
|
23 PREREQUISITES
|
|
24 =============
|
404
|
25
|
442
|
26 Make sure your system has enough swapping space allocated to handle a
|
|
27 program whose pure code is 900k bytes and whose data area is at least
|
1338
|
28 400k and can reach 8Mb or more. Note that a typical XEmacs process
|
|
29 can get much bigger: the instance this sentence was written with is
|
|
30 over 100MB! If the swapping space is insufficient, you will get an
|
442
|
31 error in the command `temacs -batch -l loadup dump', found in
|
|
32 `./src/Makefile.in.in', or possibly when running the final dumped
|
|
33 XEmacs.
|
0
|
34
|
442
|
35 Verify that your users have a high enough stack limit. On some systems
|
1036
|
36 such as OpenBSD and OSF/Tru64 the default is 2MB which is too low. On
|
2648
|
37 MacOS/X (Darwin) before 10.3, it's 512kB. See 'PROBLEMS' for details.
|
424
|
38
|
|
39 Building XEmacs requires about 100 Mb of disk space (including the
|
1338
|
40 XEmacs sources). Once installed, XEmacs occupies between 20 and 100
|
|
41 MB in the file system where it is installed; this includes the
|
|
42 executable files, Lisp libraries, miscellaneous data files, and
|
|
43 on-line documentation. The exact amount depends greatly on the number
|
|
44 of extra Lisp packages that are installed.
|
149
|
45
|
2427
|
46 XEmacs requires an ANSI C compiler, such as GCC. If you wish to build the
|
|
47 documentation yourself, you will need at least version 1.68 of makeinfo (GNU
|
|
48 texinfo-3.11). GNU Texinfo 4.2 is recommended; it is necessary for building
|
|
49 Lisp packages, and we may move to it for the core.
|
149
|
50
|
1338
|
51 A note on terminology: unfortunately the terms "library" and "package"
|
|
52 are heavily overloaded. In the following, "library" refers to an
|
|
53 external body of executable code which may be linked with XEmacs at
|
|
54 build time to provide support for system features, such as images,
|
|
55 audio, stream compression, databases, and input methods. A "Lisp
|
|
56 library" is a file of Lisp code which may be loaded into XEmacs at
|
|
57 run-time to provide editor features. A "package" is a specially
|
|
58 prepared Lisp library or set of Lisp libraries, providing for easy
|
|
59 installation, upgrade, and removal of applications written in Lisp.
|
398
|
60
|
442
|
61 PACKAGE SYSTEM
|
|
62 ==============
|
424
|
63
|
442
|
64 The file README.packages contain information vital to have a fully
|
1338
|
65 working XEmacs. It includes a description of available packages, and
|
|
66 how to bootstrap XEmacs from a minimal or a complete set of packages.
|
|
67 This information was not included in this file only because it is too
|
|
68 large for this terse INSTALL. Please read README.packages now!
|
|
69
|
|
70 ADD-ON LIBRARIES
|
|
71 ================
|
|
72
|
|
73 Decide which libraries you would like to use with XEmacs, but are not
|
1375
|
74 yet available on your system. On some systems, X11, Motif and CDE are
|
3018
|
75 optional additions. On MacOS/X systems prior to 10.2, you may download
|
|
76 X11R6 for Mac OS X from http://www.apple.com/macosx/x11/download/. In
|
|
77 later releases X11 is available as an optional package on the
|
|
78 installation CDs. In either case you need both the runtime libraries
|
|
79 and the SDK (in a sidebar of that page at the time of writing). There
|
|
80 is also a 3rd-party implementation of X11R6 for the Mac at
|
|
81 http://www.xdarwin.org/. On Solaris, the SUNWaudmo package enables
|
|
82 native sound support. There are also a number of free software
|
|
83 applications that XEmacs can use. If these are not yet available on
|
|
84 your system, obtain, build and install those external libraries before
|
|
85 building XEmacs. The libraries XEmacs can use are:
|
1338
|
86
|
|
87 Xaw3d, XPM, JPEG, compface, PNG, zlib, GNU DBM, Berkeley DB, socks,
|
|
88 term, NAS, Canna, Kinput2, SJ3, Wnn, PostgreSQL, LDAP.
|
|
89
|
|
90 You can get (most of) them from the XEmacs FTP archive at
|
|
91 <ftp://ftp.xemacs.org/pub/xemacs/aux>. Information about what
|
|
92 each library does is available in the file
|
|
93 <ftp://ftp.xemacs.org/pub/xemacs/aux/00README.txt>.
|
|
94
|
2648
|
95 Use the `--with-site-includes' and `--with-site-libraries' options when
|
|
96 building XEmacs to allow configure to find the external software
|
|
97 packages. For your convenience these can be set together by using the
|
|
98 `--with-site-prefixes' option. This will set these variables as needed
|
1338
|
99 assuming your libraries are organised as a typical /usr tree.
|
|
100
|
|
101 If you link dynamically with external libraries, usually denoted by
|
2648
|
102 ".so" (Unix), ".dll" (Windows), or ".dylib" (MacOS) file extensions, on
|
|
103 some systems you may also need to add the library directories to the
|
|
104 `--with-site-runtime-libraries' option. It is typically necessary only
|
1338
|
105 if you link with dynamic libraries that are installed in non-standard
|
2648
|
106 directories, or if you expect some of the libraries used to build XEmacs
|
|
107 to be in a different directory at run time than at build time.
|
1338
|
108
|
|
109 NOTE: This option has unusual semantics. ONLY libraries found in the
|
|
110 directories specified in this option will be used at runtime. This
|
|
111 means you must specify ALL directories you want searched at runtime in
|
|
112 this option (perhaps excluding a very small number of standard system
|
|
113 library paths).
|
|
114
|
2648
|
115 Directories specified with `--with-site-libraries' are NOT automatically
|
|
116 added. The rationale is that most users will not need this option, and
|
|
117 this allows the builder to specify exactly the needed directories.
|
|
118 Specifying unnecessary directories leads to obscure problems (typically
|
|
119 startup delays) if those directories are mounted over a network, and the
|
|
120 automounter configuration changes. Not all systems need this option;
|
|
121 it's best to avoid using it if you can.
|
1338
|
122
|
|
123 Dynamic linking has pros and cons. Dynamically linking 3rd party
|
|
124 libraries to XEmacs decreases the size of the binary, and means you
|
|
125 don't need to rebuild XEmacs to take advantage of improvements in the
|
|
126 libraries. On the other hand, XEmacs can fail subtly if the semantics
|
|
127 of a library changes, other users may not be able to use your
|
|
128 "private" copies of the libraries, and you may have to relink XEmacs,
|
|
129 or even omit the feature, if the ABI changes when the libraries are
|
|
130 upgraded.
|
424
|
131
|
442
|
132 CONFIGURATION OPTIONS
|
|
133 =====================
|
269
|
134
|
442
|
135 In the top level directory of the XEmacs distribution, run the
|
|
136 program `configure' as follows:
|
0
|
137
|
149
|
138 ./configure [CONFIGURATION-NAME] [--OPTION[=VALUE]] ...
|
0
|
139
|
3018
|
140 Options are generally of the form `--with-FEATURE' or
|
|
141 `--enable-FEATURE' to use a feature or `--without-FEATURE' or
|
|
142 `--disable-FEATURE' to not use a feature. Unlike the `configure'
|
|
143 program used in other applications, either `--with-FEATURE' or
|
|
144 `--enable-FEATURE' can be used to use the same feature.
|
|
145
|
3050
|
146 If you haven't built XEmacs 21.5 recently, the change from the
|
|
147 configure script based on Autoconf 2.13 can be a shock. Appendix:
|
|
148 Correspondence to Old Configure Options (at the end of this document)
|
|
149 contains a list of old options and their new equivalents.
|
|
150
|
1338
|
151 Controlling the Host Type
|
|
152 -------------------------
|
|
153
|
243
|
154 Almost always, you should let `configure' (actually the shell script
|
|
155 `config.guess') guess your host type, by omitting the
|
149
|
156 CONFIGURATION-NAME argument. If you like to experiment, specify a
|
|
157 configuration name in the form MACHINE-VENDOR-OPSYS, for example:
|
|
158
|
|
159 sparc-sun-solaris2.6
|
|
160
|
|
161 See config.guess and configure.in for valid values for MACHINE,
|
|
162 VENDOR, and OPSYS. Also check `./etc/MACHINES' for advice on building
|
|
163 on particular machines.
|
0
|
164
|
1338
|
165 Specifying Location of Headers and Libraries
|
|
166 --------------------------------------------
|
|
167
|
2648
|
168 The `--with-site-includes=DIR' and `--with-site-libraries=DIR' options
|
|
169 allow you to specify additional places the compiler should look for
|
|
170 include files and object libraries. You may specify multiple DIR's by
|
1338
|
171 enclosing the list in quotes. All the external libraries you want to
|
|
172 use with XEmacs (e.g. xpm, wnn, ...) described later should have their
|
|
173 include and library directories defined using these options.
|
|
174
|
2648
|
175 The `--with-site-runtime-libraries=DIR' option specifies directories to
|
1338
|
176 search for shared libraries at run time. If you use this option, you
|
|
177 must specify ALL of the directories containing shared libraries at run
|
|
178 time, including system directories. Please read the information about
|
|
179 "ADD-ON LIBRARIES" above very carefully.
|
0
|
180
|
|
181 The `--x-includes=DIR' and `--x-libraries=DIR' options tell the build
|
|
182 process where the compiler should look for the include files and
|
|
183 object libraries used with the X Window System. Normally, `configure'
|
|
184 is able to find them; these options are necessary if you have your X
|
|
185 Window System files installed in unusual places.
|
|
186
|
1338
|
187 Configuring the Build Process
|
|
188 -----------------------------
|
149
|
189
|
2648
|
190 The `--with-gcc=PROGRAM' option specifies that the build process should
|
|
191 compile XEmacs using GCC. The `--with-compiler' option allows you to
|
|
192 specify some other compiler to be used to compile XEmacs. If neither
|
|
193 option is specified, the environment variable CC is used instead.
|
|
194 Otherwise the compiler will then default to 'cc'.
|
201
|
195
|
2648
|
196 The `--with-xemacs-compiler=PROGRAM' option specifies the compiler
|
|
197 control program for the xemacs binary only. Other C code will be
|
|
198 compiled according to the `--with-gcc' and `--with-compiler' options
|
|
199 above. This is useful if you wish to compile XEmacs with a C++
|
|
200 compiler, because the utilities in ./lib-src cannot be compiled as C++.
|
|
201 This option is primarily intended for use by the maintainers.
|
0
|
202
|
2648
|
203 The `--with-cflags=FLAGS' option specifies all of the CFLAGS the build
|
|
204 process should use when compiling XEmacs, except for flags controlling
|
|
205 warning generation. Otherwise the value of the environment variable
|
|
206 CFLAGS is consulted. If that is also undefined, CFLAGS defaults to "-g
|
|
207 -O" for gcc and "-g" for all other compilers.
|
0
|
208
|
2648
|
209 The `--with-cflags-warning=FLAGS' option specifies the warnings to be
|
1338
|
210 generated. There is normally no reason to use this flag, as XEmacs
|
3050
|
211 turns on as many warnings as possible, and is still intended to build
|
|
212 with no warnings. If you get any undocumented warnings, please report
|
|
213 them as bugs---they very often are, or at least indicate possible
|
|
214 bitrot.
|
594
|
215
|
2648
|
216 The `--with-cflags-optimization=FLAGS' option specifies the
|
3050
|
217 optimizations to be used. There is normally no reason to use this
|
|
218 flag, as XEmacs will already set the maximum safe optimization flags
|
|
219 appropriate for the compiler being invoked.
|
2648
|
220
|
|
221 The `--with-cflags-debugging=FLAGS' option specifies debugging
|
3050
|
222 information to be generated. You should avoid using this flag, as it
|
|
223 makes most severe or fatal bugs hard-to-impossible to diagnose and
|
|
224 fix. Debugging information does not slow down XEmacs at runtime, and
|
|
225 it doesn't make the binary very much bigger.
|
2648
|
226
|
3050
|
227 The `--with-dynamic' option specifies that configure should try to
|
|
228 link XEmacs dynamically rather than statically. `--with-static'
|
|
229 specifies the reverse. XEmacs's configure script detects whether
|
|
230 dynamic linking can be done on all platforms we know of; these options
|
|
231 are normally unnecessary.
|
|
232
|
|
233 The `--with-modules' option specifies that XEmacs be built with
|
|
234 support for runtime loadable modules. NOTE TO OEMS: XEmacs can be
|
|
235 distributed configured to support several options based on external
|
|
236 APIs (currently LDAP, PostgreSQL, and Canna) as loadable modules. You
|
|
237 can distribute an XEmacs binary package with these options enabled
|
|
238 without depending on the external package. XEmacs will fail
|
|
239 gracefully at runtime, issuing an error message indicating that the
|
|
240 required support was not found on the system.
|
0
|
241
|
|
242 You can build XEmacs for several different machine types from a single
|
|
243 source directory. To do this, you must use a version of `make' that
|
442
|
244 supports the `VPATH' variable, such as GNU `make'. Create separate
|
0
|
245 build directories for the different configuration types, and in each
|
|
246 one, run the XEmacs `configure' script. `configure' looks for the
|
1338
|
247 Emacs source code in the directory that `configure' is in. The
|
|
248 `--srcdir' option may not work correctly (traditionally it was
|
|
249 overridden by the directory containing `configure').
|
|
250
|
|
251 Configuring the Installation Layout
|
|
252 -----------------------------------
|
0
|
253
|
|
254 The `--prefix=PREFIXDIR' option specifies where the installation process
|
|
255 should put XEmacs and its data files. This defaults to `/usr/local'.
|
|
256 - XEmacs (and the other utilities users run) go in PREFIXDIR/bin
|
|
257 (unless the `--exec-prefix' option says otherwise).
|
|
258 - The architecture-independent files go in PREFIXDIR/lib/xemacs-VERSION
|
276
|
259 (where VERSION is the version number of XEmacs, like `21.0').
|
0
|
260 - The architecture-dependent files go in
|
243
|
261 PREFIXDIR/lib/xemacs-VERSION/CONFIGURATION-NAME
|
|
262 (where CONFIGURATION-NAME is the host type, like mips-dec-ultrix4.2),
|
0
|
263 unless the `--exec-prefix' option says otherwise.
|
|
264
|
|
265 The `--exec-prefix=EXECDIR' option allows you to specify a separate
|
|
266 portion of the directory tree for installing architecture-specific
|
|
267 files, like executables and utility programs. If specified,
|
|
268 - XEmacs (and the other utilities users run) go in EXECDIR/bin, and
|
|
269 - The architecture-dependent files go in
|
243
|
270 EXECDIR/lib/xemacs-VERSION/CONFIGURATION-NAME.
|
0
|
271 EXECDIR/bin should be a directory that is normally in users' PATHs.
|
|
272
|
442
|
273 If you specify --prefix (or any of the other installation directory
|
|
274 options), they will get compiled into the xemacs executable so it will
|
1338
|
275 be able to find its various associated files. However, XEmacs has
|
442
|
276 quite elaborate logic to find out the locations of these directories
|
|
277 dynamically. Sometimes, it is desirable *not* to compile these
|
|
278 directories into the executable so you can move the XEmacs
|
|
279 installation around (as whole) at will. This is true for binary kits,
|
|
280 for instance. Therefore, you can specify --without-prefix on the
|
|
281 configure command line to prevent the installation prefix to become
|
|
282 part of the generated executable; everything else will continue to
|
|
283 work as usual.
|
0
|
284
|
1338
|
285 Configuring Feature Support
|
|
286 ---------------------------
|
|
287
|
|
288 If you don't want X Window System support, specify `--without-x'. If
|
|
289 you omit this option, `configure' will try to autodetect whether your
|
|
290 system has X Window System support, and arrange to use it if present.
|
|
291
|
|
292 The `--without-xmu' option can be used if your vendor doesn't ship
|
|
293 the Xmu library.
|
|
294
|
3050
|
295 The `--with-menubars=TYPE' option allows you to specify which X
|
0
|
296 toolkit you wish to use for the menubar. The valid options are
|
149
|
297 `lucid', `motif' and `no'. The default is `lucid' which is a
|
0
|
298 Motif-lookalike menubar. We highly recommend its usage over the real
|
|
299 Motif menubar. (In fact, the Motif menubar is currently broken.) If
|
149
|
300 `no' is specified then support for menubars will not be compiled in.
|
0
|
301
|
3050
|
302 The `--with-scrollbars=TYPE' option allows you to specify which X
|
0
|
303 toolkit you wish to use for the scrollbars. The valid options are
|
149
|
304 `lucid', `motif', `athena', `athena3d', and `no'. The default is
|
2648
|
305 `lucid' which is a Motif-lookalike scrollbar. If `no' is specified then
|
|
306 support for scrollbars will not be compiled in.
|
0
|
307
|
3050
|
308 The `--with-dialogs=TYPE' option allows you to specify which X toolkit
|
219
|
309 you wish to use for the dialog boxes. The valid options are `athena',
|
243
|
310 `athena3d', `motif, and `no. The `lucid' option is accepted and will
|
|
311 result in the `athena' toolkit being used. If the Motif toolkit can be
|
|
312 found the default is `motif'. Otherwise, the default is `athena'. If
|
2648
|
313 `no' is specified then support for dialog boxes will not be compiled in.
|
0
|
314
|
3050
|
315 The `--with-toolbars' option allows you to enable or disable toolbar
|
1338
|
316 support. The default is `yes' if support for a windowing system is
|
|
317 included.
|
0
|
318
|
149
|
319 The `--with-xpm' option specifies that XEmacs should support X11
|
0
|
320 Pixmaps. `configure' will attempt to detect if you have the Xpm
|
|
321 libraries and define `--with-xpm' for you.
|
|
322
|
|
323 The `--with-xface' option specifies that XEmacs should support
|
|
324 X-Faces. `configure' will attempt to detect if you have the compface
|
|
325 library and define `--with-xface' for you.
|
|
326
|
3050
|
327 The `--with-database' option specifies that XEmacs should be built
|
1338
|
328 with simple database support. The valid options are `no' or a
|
0
|
329 comma-separated list of one or more of `dbm', `gnudbm' or `berkdb'.
|
|
330 `configure' will attempt to detect the necessary libraries and header
|
3050
|
331 files and define `--with-database' for you.
|
0
|
332
|
1338
|
333 The `--with-postgresql' option specifies that XEmacs should be built
|
|
334 with PostgreSQL support, linking with libpq. `configure' will attempt
|
|
335 to detect whether PostgreSQL support is available, and automatically
|
3050
|
336 define `--with-postgresql' for you. NOTE TO OEMS: If modules are
|
|
337 supported and enabled, the libpq API support will be build as a
|
|
338 module.
|
1338
|
339
|
|
340 The `--with-ldap' option specifies that XEmacs should be build with
|
|
341 LDAP support, using the OpenLDAP libraries. `configure' will attempt
|
|
342 to detect whether LDAP support is available, and automatically define
|
3050
|
343 `--with-ldap' for you. NOTE TO OEMS: If modules are supported and
|
|
344 enabled, the OpenLDAP API support will be build as a module.
|
1338
|
345
|
0
|
346 The `--with-socks' option specifies that XEmacs should be built with
|
149
|
347 SOCKS support. This requires the libsocks library.
|
0
|
348
|
3050
|
349 The `--with-external-widget' option specifies that XEmacs should be
|
2648
|
350 built with support for being used as a widget by other X11 applications.
|
1338
|
351 This functionality should be considered beta.
|
|
352
|
3050
|
353 The `--with-sound=TYPE' option specifies that XEmacs should be built
|
|
354 with sound support. Native (`--with-sound=native') sound support is
|
1338
|
355 currently available only on Sun SparcStations, SGI's, HP9000s, and
|
|
356 systems (such as Linux) with soundcard.h. Network Audio Support (NAS)
|
3050
|
357 (`--with-sound=nas') is an extension to X that you may or may not have
|
2648
|
358 for your system. For NAS, you will probably need to provide the paths
|
|
359 to the nas include and library directories to configure. If
|
3050
|
360 `--with-sound' is not specified, `configure' will attempt to determine
|
|
361 if your configuration supports native sound and define --with-sound
|
2648
|
362 for you. If your native sound library is not in a standard location you
|
|
363 can specify it with the `--with-native-sound-lib=LIB' flag. For Linux,
|
|
364 `/dev/audio' is required for SunAudio files and `/dev/dsp' is required
|
|
365 for raw data and WAVE format files.
|
1338
|
366
|
0
|
367 The `--with-tooltalk' option specifies that XEmacs should be built
|
|
368 with ToolTalk support for interconnecting with other applications.
|
243
|
369 ToolTalk is not yet supported on all architectures. If you use this
|
|
370 option, you should have the tooltalk package (see etc/PACKAGES)
|
|
371 installed prior to building XEmacs.
|
0
|
372
|
|
373 The `--with-sparcworks' option specifies that XEmacs should be built
|
149
|
374 with support for Sun Sparcworks 3.0.1 and up (including Sun WorkShop).
|
|
375 This functionality is only of use on SunOS 4.1.x and Solaris 2.x
|
272
|
376 systems. If you use this option, you should have the Sun package (see
|
243
|
377 etc/PACKAGES) installed prior to building XEmacs.
|
0
|
378
|
149
|
379 The `--with-cde' option allows you to enable or disable CDE drag and
|
0
|
380 drop support. `configure' will attempt to detect this option and
|
|
381 define `--with-cde' for you.
|
|
382
|
272
|
383 The `--with-offix' option allows you to enable or disable OffiX drag
|
|
384 and drop support. This requires no external library support, so if
|
|
385 X11 support is available, then this option defaults to `yes'. OffiX
|
274
|
386 support can be explicitly disabled via the `--with-offix=no' option.
|
2
|
387
|
1338
|
388 Internationalization Options
|
|
389 ----------------------------
|
0
|
390
|
3050
|
391 The `--with-mule' option enables MUlti-Lingual Emacs (Mule) support,
|
1338
|
392 needed to support non-Latin-1 (including Asian) languages. Mule
|
|
393 support is required for Asian language and Unicode (multibyte and wide
|
|
394 character) support. With the advent of the Euro and European
|
|
395 Community expansion, Mule support is also recommended for Western
|
|
396 Europeans. Enabling Mule support requires the mule-base package
|
|
397 installed prior to building XEmacs. The `--with-xim', --with-xfs',
|
|
398 `--with-canna', `--with-wnn' and `--with-wnn6' options require
|
|
399 Mule support.
|
149
|
400
|
|
401 The `--with-xim' option enables use of the X11 XIM mechanism to allow
|
|
402 an input method to input text into XEmacs. The input method is shared
|
|
403 among all the X applications sharing an X display and using the same
|
151
|
404 language. The XIM support comes in two flavors: `motif' and `xlib'.
|
|
405 The Motif support (the XmIm* functions) is preferred when available.
|
243
|
406 The xlib XIM support works reasonably well so long as the X11 libraries
|
|
407 are recent enough. It has been fairly well tested on Linux with glibc
|
|
408 2.0.5 and 2.0.6 and Kinput2 as an XIM server. In this configuration
|
|
409 X11 must be recompiled with X_LOCALE defined because glibc is lacking
|
|
410 localization for Japanese. The XIM support defaults to `no' except
|
|
411 when Motif is detected where it is stable with OSF libraries. The XIM
|
|
412 support in Lesstif (a Free Motif replacement) does not work as of
|
|
413 v0.82. If you enable this option, you will probably wish to install
|
|
414 the `locale' package which contains localized Splash screens and
|
|
415 Menubars.
|
|
416
|
272
|
417 The `--with-xfs' option enables use of a multilingual Menubar. At the
|
243
|
418 present time, only Japanese and French locales are supported. In
|
272
|
419 order to use a multilingual Menubar you must have the `locale' package
|
243
|
420 installed. The `locale' package does not have to be installed when
|
|
421 building XEmacs.
|
149
|
422
|
|
423 The `--with-canna' option enables the use of the Canna Japanese input
|
243
|
424 method. This is stable code and fairly well tested. In order to use
|
2283
|
425 it, you will have to have the Canna server installed and running. Canna
|
|
426 versions 3.2pl2, 3.5b2, and 3.7p3 are known to work. Version 3.2pl2 is
|
|
427 considered more stable than version 3.5b2; the stability of 3.7p3 is
|
|
428 still unknown. If Canna is already installed, configure will autodetect
|
|
429 it, so you never need to explicitly use this option unless your Canna
|
|
430 libraries are somewhere strange. Canna run time support is currently
|
|
431 bundled with the `mule-base' package so there is nothing additional to
|
3050
|
432 install in order to use it. NOTE TO OEMS: If modules are supported
|
|
433 and enabled, the libcanna API support will be build as a module.
|
0
|
434
|
243
|
435 The `--with-wnn' and `--with-wnn6' options are for compiling with the Wnn
|
|
436 multi-language input method. `--with-wnn' is for compiling with Wnn-4.2,
|
|
437 the Free version of WNN. `--with-wnn6' is for compiling against WNN6,
|
|
438 the commercial version of WNN available from OMRON Corporation. This is
|
|
439 stable code and fairly well tested. In order to build with this
|
|
440 option, you will need to have the `egg-its' lisp package already
|
|
441 installed.
|
|
442
|
|
443 Please note that it is safe to build with as many of the options
|
|
444 `--with-xim', `--with-canna' and `--with-wnn' as your system
|
|
445 supports.
|
104
|
446
|
1338
|
447 Options for Developers and Special Requirements
|
|
448 -----------------------------------------------
|
|
449
|
2648
|
450 The `--with-rel-alloc' option can be used to either enable or disable
|
|
451 use of the relocating allocator. Turning on --with-rel-alloc will allow
|
|
452 XEmacs to return unused memory to the operating system, thereby reducing
|
|
453 its memory footprint. However, it may make XEmacs runs more slowly,
|
1338
|
454 especially if your system's `mmap' implementation is missing or
|
2648
|
455 inefficient. Generally, it's best to go with the default configuration
|
|
456 for your system. You can tweak this based on how you use XEmacs, and
|
|
457 the memory and cpu resources available on your system.
|
1338
|
458
|
|
459 The `--with-system-malloc' option can be used to either enable or
|
|
460 disable use of the system malloc. Generally, it's best to go with the
|
|
461 default configuration for your system. Note that on many systems
|
|
462 using the system malloc disables the use of the relocating allocator.
|
|
463
|
|
464 The `--with-debug-malloc' option can be used to link a special
|
|
465 debugging version of malloc. Debug Malloc is not included with XEmacs
|
|
466 and is intended for use only by the developers. It may be obtained
|
|
467 from <URL:http://www.letters.com/dmalloc/>.
|
|
468
|
2648
|
469 The `--enable-debug' and `--enable-error-checking' options are primarily
|
|
470 useful to the developers. `--enable-debug' incorporates code for
|
|
471 performing various tests, but does not impose a speed penalty.
|
|
472 `--enable-error-checking' adds additional tests to many of the commonly
|
|
473 used macros, and imposes a speed penalty. Using either or both of these
|
|
474 options can make bug reports more useful to the developers.
|
1338
|
475
|
2648
|
476 The `--verbose' option is useful only to the developers. It displays
|
|
477 additional information, useful for debugging `configure'.
|
1338
|
478
|
442
|
479 MAIL LOCKING
|
|
480 ============
|
|
481
|
845
|
482 For most platforms, configure or the src/s file have the preferred
|
|
483 method for locking mail spool files preconfigured. Otherwise you must
|
|
484 find out for youself. Do not choose a locking protocol "on the
|
|
485 objective merits." XEmacs must use the same method as other mail
|
1338
|
486 utilities on your system, or you WILL lose mail.
|
845
|
487
|
|
488 Presently, XEmacs supports lockf, flock, and dot locking. Specify the
|
2648
|
489 locking method via the --with-mail-locking=METHOD option to configure.
|
|
490 Valid values for METHOD are --with-mail-locking are `lockf', `flock',
|
|
491 and `dot'.
|
442
|
492
|
|
493 RUNNING CONFIGURE
|
|
494 =================
|
|
495
|
149
|
496 `configure' doesn't do any compilation or installation itself. It
|
|
497 just creates the files that influence those things: `./src/config.h',
|
1338
|
498 and all the Makefiles in the build tree.
|
104
|
499
|
0
|
500 When it is done, `configure' prints a description of what it did and
|
|
501 creates a shell script `config.status' which, when run, recreates the
|
|
502 same configuration. If `configure' exits with an error after
|
1338
|
503 disturbing the status quo, it removes `config.status'. If `configure'
|
|
504 doesn't work as expected, the file `config.log' contains details of
|
|
505 the tests run and their results.
|
0
|
506
|
442
|
507 AUXILIARY PATHS
|
|
508 ===============
|
|
509
|
|
510 Look at `./lisp/paths.el'; if some of those values are not right for
|
|
511 your system, set up the file `./lisp/site-init.el' with XEmacs Lisp
|
|
512 code to override them; it is not a good idea to edit paths.el itself.
|
|
513 YOU MUST USE THE LISP FUNCTION `setq' TO ASSIGN VALUES, rather than
|
|
514 `defvar', as used by `./lisp/paths.el'. For example,
|
0
|
515
|
|
516 (setq news-inews-program "/usr/bin/inews")
|
|
517
|
|
518 is how you would override the default value of the variable
|
|
519 news-inews-program (which is "/usr/local/inews").
|
|
520
|
|
521 Before you override a variable this way, *look at the value* that the
|
|
522 variable gets by default! Make sure you know what kind of value the
|
|
523 variable should have. If you don't pay attention to what you are
|
|
524 doing, you'll make a mistake.
|
|
525
|
392
|
526 Things may malfunction if the variable `directory-abbrev-alist' is not
|
|
527 set up to translate "temporary" automounter mount points into the
|
|
528 canonical form. XEmacs tries to detect how your automounter is
|
|
529 configured. If you have an unusual automounter configuration that
|
|
530 XEmacs cannot detect, you may need to change the value of
|
|
531 `directory-abbrev-alist'.
|
371
|
532
|
442
|
533 SITE-SPECIFIC STARTUP CODE
|
|
534 ==========================
|
|
535
|
|
536 Put into `./lisp/site-init.el' or `./lisp/site-load.el' any Emacs Lisp
|
|
537 code you want XEmacs to load before it is dumped out. Use
|
0
|
538 site-load.el for additional libraries if you arrange for their
|
|
539 documentation strings to be in the lib-src/DOC file (see
|
|
540 src/Makefile.in.in if you wish to figure out how to do that). For all
|
|
541 else, use site-init.el.
|
|
542
|
|
543 Note that, on some systems, the code you place in site-init.el must
|
|
544 not use expand-file-name or any other function which may look
|
|
545 something up in the system's password and user information database.
|
|
546 See `./PROBLEMS' for more details on which systems this affects.
|
|
547
|
|
548 The `site-*.el' files are nonexistent in the distribution. You do not
|
|
549 need to create them if you have nothing to put in them.
|
|
550
|
442
|
551 TERMCAP CONFIGURATION
|
|
552 =====================
|
|
553
|
|
554 Refer to the file `./etc/TERMS' for information on fields you may
|
0
|
555 wish to add to various termcap entries. The files `./etc/termcap.ucb'
|
|
556 and `./etc/termcap.dat' may already contain appropriately-modified
|
|
557 entries.
|
|
558
|
442
|
559 RUNNING MAKE
|
|
560 ============
|
|
561
|
|
562 Run `make' in the top directory of the XEmacs distribution to finish
|
0
|
563 building XEmacs in the standard way. The final executable file is
|
1338
|
564 named `src/xemacs'. You can execute this file in place without
|
0
|
565 copying it, if you wish; then it automatically uses the sibling
|
|
566 directories ../lisp, ../lib-src, ../info.
|
|
567
|
1338
|
568 Or you can install the executable and the other XEmacs into their
|
|
569 permanent locations, with `make install'. By default, XEmacs's files
|
0
|
570 are installed in the following directories:
|
|
571
|
|
572 `/usr/local/bin' holds the executable programs users normally run -
|
388
|
573 `xemacs', `etags', `ctags', `b2m', `emacsclient', `ellcc',
|
0
|
574 `gnuclient', `gnudoit', `gnuattach', and `rcs-checkin'.
|
|
575
|
|
576 `/usr/local/lib/xemacs-VERSION/lisp' holds the Emacs Lisp libraries;
|
|
577 `VERSION' stands for the number of the XEmacs version
|
|
578 you are installing, like `18.59' or `19.14'. Since
|
|
579 the lisp libraries change from one version of XEmacs to
|
|
580 another, including the version number in the path
|
|
581 allows you to have several versions of XEmacs installed
|
|
582 at the same time; this means that you don't have to
|
|
583 make XEmacs unavailable while installing a new version.
|
|
584
|
|
585 XEmacs searches for its lisp files in these
|
|
586 directories, and then in
|
|
587 `/usr/local/lib/xemacs/site-lisp/*'.
|
|
588
|
|
589 `/usr/local/lib/xemacs-VERSION/etc' holds the XEmacs tutorial, the
|
|
590 `yow' database, and other architecture-independent
|
|
591 files XEmacs might need while running. VERSION is as
|
|
592 specified for `.../lisp'.
|
|
593
|
|
594 `/usr/local/lib/xemacs/lock' contains files indicating who is
|
|
595 editing what, so XEmacs can detect editing clashes
|
|
596 between users.
|
|
597
|
|
598 `/usr/local/lib/xemacs-VERSION/CONFIGURATION-NAME' contains executable
|
|
599 programs used by XEmacs that users are not expected to
|
|
600 run themselves, and the DOC file. `VERSION' is the
|
|
601 number of the XEmacs version you are installing, and
|
243
|
602 `CONFIGURATION-NAME' is the host type of your system.
|
|
603 Since these files are specific to the version of
|
|
604 XEmacs, operating system, and architecture in use,
|
|
605 including the configuration name in the path allows
|
|
606 you to have several versions of XEmacs for any mix of
|
|
607 machines and operating systems installed at the same
|
|
608 time; this is useful for sites at which different
|
|
609 kinds of machines share the file system XEmacs is
|
|
610 installed on.
|
0
|
611
|
388
|
612 `/usr/local/lib/xemacs-VERSION/CONFIGURATION-NAME/modules' holds the Emacs
|
|
613 dynamically loadable modules. These are special programs
|
|
614 typically written in C that can be loaded in much the same
|
|
615 way that Lisp packages are. Not all systems support
|
|
616 dynamic modules, so do not be alarmed if this directory
|
|
617 does not exist or is empty.
|
|
618
|
|
619 XEmacs searches for modules in this directory, or any
|
|
620 sub-directory of it, and then in
|
|
621 `/usr/local/lib/xemacs/site-modules/*'.
|
|
622
|
0
|
623 `/usr/local/lib/xemacs-VERSION/info' holds the on-line documentation
|
|
624 for XEmacs, known as "info files".
|
|
625
|
|
626 `/usr/local/man/man1' holds the man pages for the programs installed
|
|
627 in `/usr/local/bin'.
|
|
628
|
|
629 If these directories are not what you want, you can specify where to
|
|
630 install XEmacs's libraries and data files or where XEmacs should search
|
|
631 for its lisp files by giving values for `make' variables as part of
|
442
|
632 the command.
|
0
|
633
|
|
634 You can change where the build process installs XEmacs and its data
|
|
635 files by specifying values for `make' variables as part of the `make'
|
|
636 command line. For example, if you type
|
|
637
|
|
638 make install bindir=/usr/local/gnubin
|
|
639
|
|
640 the `bindir=/usr/local/gnubin' argument indicates that the XEmacs
|
|
641 executable files should go in `/usr/local/gnubin', not
|
|
642 `/usr/local/bin'.
|
|
643
|
|
644 Here is a complete list of the variables you may want to set.
|
|
645
|
|
646 `bindir' indicates where to put executable programs that users can
|
|
647 run. This defaults to /usr/local/bin.
|
|
648
|
|
649 `datadir' indicates where to put the architecture-independent
|
|
650 read-only data files that XEmacs refers to while it runs; it
|
|
651 defaults to /usr/local/lib. We create the following
|
|
652 subdirectories under `datadir':
|
|
653 - `xemacs-VERSION/lisp', containing the XEmacs lisp libraries, and
|
|
654
|
|
655 - `xemacs-VERSION/etc', containing the XEmacs tutorial and the
|
|
656 `yow' database.
|
|
657 `VERSION' is the number of the XEmacs version you are installing,
|
|
658 like `18.59' or `19.14'. Since these files vary from one version
|
|
659 of XEmacs to another, including the version number in the path
|
|
660 allows you to have several versions of XEmacs installed at the
|
|
661 same time; this means that you don't have to make XEmacs
|
|
662 unavailable while installing a new version.
|
|
663
|
|
664 `statedir' indicates where to put architecture-independent data files
|
|
665 that XEmacs modifies while it runs; it defaults to
|
|
666 /usr/local/lib as well. We create the following
|
|
667 subdirectories under `statedir':
|
|
668 - `xemacs/lock', containing files indicating who is editing
|
|
669 what, so XEmacs can detect editing clashes between
|
|
670 users.
|
|
671
|
|
672 `libdir' indicates where to put architecture-specific data files that
|
|
673 XEmacs refers to as it runs; it too defaults to `/usr/local/lib'.
|
|
674 We create the following subdirectories under `libdir':
|
|
675 - `xemacs-VERSION/CONFIGURATION-NAME', containing executable
|
|
676 programs used by XEmacs that users are not expected to run
|
1338
|
677 themselves, and the DOC file.
|
0
|
678 `VERSION' is the number of the XEmacs version you are installing,
|
243
|
679 and `CONFIGURATION-NAME' is the host type of your system.
|
|
680 Since these files are specific to the version of XEmacs,
|
|
681 operating system, and architecture in use, including the
|
|
682 configuration name in the path allows you to have several
|
|
683 versions of XEmacs for any mix of machines and operating
|
|
684 systems installed at the same time; this is useful for sites
|
|
685 at which different kinds of machines share the file system
|
|
686 XEmacs is installed on.
|
0
|
687
|
|
688 `infodir' indicates where to put the info files distributed with
|
|
689 XEmacs; it defaults to `/usr/local/lib/xemacs-VERSION/info'.
|
|
690
|
|
691 `mandir' indicates where to put the man pages for XEmacs and its
|
|
692 utilities (like `etags'); it defaults to
|
|
693 `/usr/local/man/man1'.
|
|
694
|
|
695 `prefix' doesn't give a path for any specific part of XEmacs; instead,
|
|
696 its value is used to determine the defaults for all the
|
|
697 architecture-independent path variables - `datadir',
|
|
698 `statedir', `infodir', and `mandir'. Its default value is
|
|
699 `/usr/local'; the other variables add on `lib' or `man' to it
|
|
700 by default.
|
|
701
|
|
702 For example, suppose your site generally places GNU software
|
|
703 under `/usr/users/software/gnusoft' instead of `/usr/local'.
|
|
704 By including
|
|
705 `prefix=/usr/users/software/gnusoft'
|
|
706 in the arguments to `make', you can instruct the build process
|
|
707 to place all of the XEmacs data files in the appropriate
|
|
708 directories under that path.
|
|
709
|
|
710 `exec_prefix' serves the same purpose as `prefix', but instead
|
|
711 determines the default values for the architecture-dependent
|
|
712 path variables - `bindir' and `libdir'.
|
|
713
|
|
714 The above variables serve analogous purposes in the makefiles for all
|
|
715 GNU software; here are some variables specific to XEmacs.
|
|
716
|
|
717 `lispdir' indicates where XEmacs installs and expects its lisp
|
|
718 libraries. Its default value, based on `datadir' (see above),
|
|
719 is `/usr/local/lib/xemacs-VERSION/lisp' (where `VERSION' is as
|
|
720 described above).
|
|
721
|
|
722 `sitelispdir' indicates where XEmacs should search for lisp libraries
|
|
723 specific to your site. XEmacs checks them in order before
|
|
724 checking `lispdir'. Its default value, based on `datadir'
|
|
725 (see above), is `/usr/local/lib/xemacs/site-lisp'.
|
|
726
|
|
727 `etcdir' indicates where XEmacs should install and expect the rest of
|
|
728 its architecture-independent data, like the tutorial and yow
|
|
729 database. Its default value, based on `datadir'
|
|
730 (see above), is `/usr/local/lib/xemacs-VERSION/etc' (where
|
|
731 `VERSION' is as described above).
|
|
732
|
|
733 `lockdir' indicates the directory where XEmacs keeps track of its
|
|
734 locking information. Its default value, based on `statedir'
|
|
735 (see above), is `/usr/local/lib/xemacs/lock'.
|
|
736
|
|
737 `archlibdir' indicates where XEmacs installs and expects the
|
|
738 executable files and other architecture-dependent data it uses
|
|
739 while running. Its default value, based on `libdir' (see
|
|
740 above), is `/usr/local/lib/xemacs-VERSION/CONFIGURATION-NAME'
|
|
741 (where VERSION and CONFIGURATION-NAME are as described above).
|
|
742
|
420
|
743 `docdir' indicates where to put Lisp documentation strings that XEmacs
|
442
|
744 refers to as it runs. It defaults to the value of `archlibdir'
|
420
|
745 (see above).
|
|
746
|
388
|
747 `moduledir' indicates where XEmacs installs and expects to find
|
|
748 any dynamic modules. Its default value, based on
|
|
749 `archlibdir' (see above) is
|
|
750 `/usr/local/lib/xemacs-VERSION/CONFIGURATION-NAME/modules'
|
|
751 (where VERSION and CONFIGURATION-NAME are as described above).
|
|
752 By their very nature, dynamic loadable modules are architecture-
|
442
|
753 dependent, and care should be taken not to set this directory
|
|
754 to a system- or architecture-independent directory.
|
388
|
755
|
0
|
756 Remember that you must specify any variable values you need each time
|
|
757 you run `make' in the top directory. If you run `make' once to build
|
|
758 xemacs, test it, and then run `make' again to install the files, you
|
|
759 must provide the same variable settings each time. To make the
|
|
760 settings persist, you can edit them into the `Makefile' in the top
|
|
761 directory, but be aware that running the `configure' program erases
|
|
762 `Makefile' and rebuilds it from `Makefile.in'.
|
|
763
|
|
764 The top-level Makefile stores the variable settings it used in the
|
|
765 Makefiles for the subdirectories, so you don't have to specify them
|
|
766 when running make in the subdirectories.
|
|
767
|
442
|
768 Using GNU Make allows for simultaneous builds with and without the
|
|
769 --srcdir option.
|
0
|
770
|
1283
|
771 STRIPPING BINARIES
|
|
772 ==================
|
|
773
|
|
774 This saves nothing but a small (by modern standards) amount of disk
|
|
775 space; the symbol table is not loaded into memory at execution time.
|
|
776 If you do encounter a crash or other serious bug, the first thing the
|
|
777 developers will do is ask you to build an XEmacs with a full symbol
|
|
778 table, anyway. Don't strip the XEmacs binary.
|
|
779
|
442
|
780 MAIL-LOCKING POST-INSTALLATION
|
|
781 ==============================
|
0
|
782
|
442
|
783 If your system uses dot-locking to interlock access to mailer inbox
|
|
784 files, then you might need to make the movemail program setuid or
|
|
785 setgid to enable it to write the lock files. We believe this is safe.
|
|
786 The setuid/setgid bits need not be set on any other XEmacs-related
|
|
787 executables.
|
0
|
788
|
442
|
789 CLEANING UP
|
|
790 ==========
|
0
|
791
|
442
|
792 You are done with the hard part! You can remove executables and
|
|
793 object files from the build directory by typing `make clean'. To also
|
|
794 remove the files that `configure' created (so you can compile XEmacs
|
|
795 for a different configuration), type `make distclean'.
|
0
|
796
|
442
|
797 READ README.packages
|
|
798 ====================
|
0
|
799
|
442
|
800 Do it!
|
0
|
801
|
|
802 PROBLEMS
|
442
|
803 ========
|
398
|
804
|
1338
|
805 The most common problem is that you forgot to read and follow the
|
|
806 directions in README.packages. You can not have a normal XEmacs
|
424
|
807 without downloading some additional packages.
|
|
808
|
1036
|
809 See the file PROBLEMS in this directory for a list of various problems
|
|
810 sometimes encountered, and what to do about them. PROBLEMS is also
|
|
811 the place where platform-specific build notes can be found.
|
3050
|
812
|
|
813 APPENDIX: CORRESPONDENCE TO OLD CONFIGURE OPTIONS
|
|
814 =================================================
|
|
815
|
|
816 Here is a full translation of command line arguments. Note that any
|
|
817 option starting with "--with" may also be specified with "--enable".
|
|
818 This list may not be up-to-date.
|
|
819
|
|
820 Old | New
|
|
821 ------------------------------------------
|
|
822 General options:
|
|
823 ----------------
|
|
824
|
|
825 --help Unchanged
|
|
826 --usage Removed
|
|
827 --verbose Unchanged
|
|
828 --extra-verbose Removed
|
|
829
|
|
830 Compilation options:
|
|
831 --------------------
|
|
832
|
|
833 --compiler --with-compiler
|
|
834 --xemacs-compiler --with-xemacs-compiler
|
|
835 --with-gcc Unchanged
|
|
836 --cflags --with-cflags
|
|
837 --cflags-warning --with-cflags-warning
|
|
838 --debug --with-debug
|
|
839 New --with-cflags-debug
|
|
840 New --with-optimization
|
|
841 New --with-cflags-optimization
|
|
842 --cpp --with-cpp
|
|
843 --cppflags --with-cppflags
|
|
844 --libs --with-libs
|
|
845 --ldflags --with-ldflags
|
|
846 --site-includes --with-site-includes
|
|
847 --site-libraries --with-site-libraries
|
|
848 --site-prefixes --with-site-prefixes
|
|
849 --site-runtime-libraries --with-site-runtime-libraries
|
|
850 --dynamic --with-dynamic
|
|
851 --srcdir Unchanged
|
|
852
|
|
853 Installation options:
|
|
854 ---------------------
|
|
855
|
|
856 --prefix Unchanged
|
|
857 --with-prefix Unchanged
|
|
858 --with-netinstall Unchanged
|
|
859 --bindir Unchanged
|
|
860 --datadir Unchanged
|
|
861 --statedir Unchanged
|
|
862 --libdir Unchanged
|
|
863 --infodir Unchanged
|
|
864 --mandir Unchanged
|
|
865 --lispdir --with-lispdir
|
|
866 --sitelispdir Removed
|
|
867 --etcdir --with-etcdir
|
|
868 --lockdir Removed
|
|
869 --archlibdir --with-archlibdir
|
|
870 --docdir --with-docdir
|
|
871 --moduledir --with-moduledir
|
|
872
|
|
873 Run-time path-searching options:
|
|
874 --------------------------------
|
|
875
|
|
876 --with-site-lisp Unchanged
|
|
877 --with-site-modules Unchanged
|
|
878 --package-path --with-package-path
|
|
879 --infopath --with-infopath
|
|
880
|
|
881 Window-system options:
|
|
882 ----------------------
|
|
883
|
|
884 --with-gtk Unchanged
|
|
885 --with-gnome Unchanged
|
|
886 --with-x11 Unchanged
|
|
887 --x-includes Unchanged
|
|
888 --x-libraries Unchanged
|
|
889 --with-msw Unchanged
|
|
890 --with-toolbars Unchanged
|
|
891 --with-wmcommand Unchanged
|
|
892 --with-athena Unchanged
|
|
893 --with-menubars Unchanged
|
|
894 --with-scrollbars Unchanged
|
|
895 --with-dialogs Unchanged
|
|
896 --with-widgets Unchanged
|
|
897 --with-dragndrop Unchanged
|
|
898 --with-cde Unchanged
|
|
899 --with-offix Unchanged
|
|
900 --with-xmu Unchanged
|
|
901 --external-widget --with-external-widget
|
|
902
|
|
903 TTY (character terminal) options:
|
|
904 ---------------------------------
|
|
905
|
|
906 --with-tty Unchanged
|
|
907 --with-ncurses Unchanged
|
|
908 --with-gpm Unchanged
|
|
909
|
|
910 Image options:
|
|
911 --------------
|
|
912
|
|
913 --with-xpm Unchanged
|
|
914 --with-png Unchanged
|
|
915 --with-jpeg Unchanged
|
|
916 --with-tiff Unchanged
|
|
917 --with-xface Unchanged
|
|
918 --with-gif Unchanged
|
|
919
|
|
920 Sound options:
|
|
921 --------------
|
|
922
|
|
923 --with-sound Unchanged
|
|
924 --native-sound-lib=LIB --with-native-sound-lib
|
|
925
|
|
926 Internationalization options:
|
|
927 -----------------------------
|
|
928
|
|
929 --with-mule Unchanged
|
|
930 --with-xim Unchanged
|
|
931 --with-canna Unchanged
|
|
932 --with-wnn Unchanged
|
|
933 --with-wnn6 Unchanged
|
|
934 --with-xfs Unchanged
|
|
935
|
|
936 File-related options:
|
|
937 ---------------------
|
|
938
|
|
939 --with-default-eol-detection Unchanged
|
|
940 --with-clash-detection Unchanged
|
|
941
|
|
942 Database options:
|
|
943 -----------------
|
|
944
|
|
945 --with-database Unchanged
|
|
946 --with-ldap Unchanged
|
|
947 --with-postgresql Unchanged
|
|
948
|
|
949 Mail options:
|
|
950 -------------
|
|
951
|
|
952 --mail-locking=TYPE --with-mail-locking
|
|
953 --with-pop Unchanged
|
|
954 --with-kerberos Unchanged
|
|
955 --with-hesiod Unchanged
|
|
956
|
|
957 Networking options:
|
|
958 -------------------
|
|
959
|
|
960 --with-tooltalk Unchanged
|
|
961 --with-socks Unchanged
|
|
962 --with-dnet Unchanged
|
|
963 --with-ipv6-cname Unchanged
|
|
964
|
|
965 Memory allocation options:
|
|
966 --------------------------
|
|
967
|
|
968 --rel-alloc --with-rel-alloc
|
|
969 --with-dlmalloc Unchanged
|
|
970 --with-system-malloc Unchanged
|
|
971 --with-debug-malloc Unchanged
|
|
972
|
|
973 Emacs Lisp options:
|
|
974 -------------------
|
|
975
|
|
976 --use-number-lib --with-bignum
|
|
977
|
|
978 Debugging options:
|
|
979 ------------------
|
|
980
|
|
981 --debug --with-debug
|
|
982 --error-checking --with-error-checking
|
|
983 --memory-usage-stats --with-memory-usage-stats
|
|
984 --quick-build --with-quick-build
|
|
985 --use-union-type --with-union-type
|
|
986 --with-quantify Unchanged
|
|
987 --with-purify Unchanged
|
|
988
|
|
989 Developer options:
|
|
990 ------------------
|
|
991
|
|
992 --with-workshop Unchanged
|
|
993 --pdump --with-pdump
|
|
994 --use-kkcc --with-kkcc
|
|
995 --with-modules Unchanged
|
|
996
|
|
997 The output files produced by this new configure should be almost
|
|
998 identical to those produced by the old. This can be tested with the
|
|
999 provided regression test script. This script runs the two versions of
|
|
1000 configure with the supplied list of command line arguments and reports
|
|
1001 any differences. Please add your favorite configuration command lines
|
|
1002 to the list before running the test. The script is run as:
|
|
1003
|
|
1004 $ tests/autoconf/regressiontest.pl /absolute/path/to/2.13/configure \
|
|
1005 /absolute/path/to/2.59/configure >diffs.txt
|
|
1006
|
|
1007 The only differences should be:
|
|
1008 - those related to changes in the command line arguments
|
|
1009 - the change of SYS_SIGLIST_DECLARED to HAVE_DECL_SYS_SIGLIST (because the old
|
|
1010 form has been removed), and
|
|
1011 - The removal of trailing comments in src/config.h.
|
|
1012
|