Mercurial > hg > xemacs-beta

comparison INSTALL @ 149:538048ae2ab8 r20-3b1

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Import from CVS: tag r20-3b1
author cvs
date Mon, 13 Aug 2007 09:36:16 +0200
parents 1370575f1259
children 59463afc5666
comparison
equal deleted inserted replaced
148:f659db2a1f73 149:538048ae2ab8
19 19
20 20
21 BUILDING AND INSTALLATION: 21 BUILDING AND INSTALLATION:
22 22
23 1) Make sure your system has enough swapping space allocated to handle 23 1) Make sure your system has enough swapping space allocated to handle
24 a program whose pure code is 900k bytes and whose data area is at 24 a program whose pure code is 900k bytes and whose data area is at
25 least 400k and can reach 8Mb or more. If the swapping space is 25 least 400k and can reach 8Mb or more. If the swapping space is
26 insufficient, you will get an error in the command `temacs -batch -l 26 insufficient, you will get an error in the command `temacs -batch
27 loadup dump', found in `./src/Makefile.in.in', or possibly when 27 -l loadup dump', found in `./src/Makefile.in.in', or possibly when
28 running the final dumped XEmacs. 28 running the final dumped XEmacs.
29 29
30 Building XEmacs requires about 88 Mb of disk space (including the XEmacs 30 Building XEmacs requires about 88 Mb of disk space (including the
31 sources). Once installed, XEmacs occupies about 50 Mb in the file system 31 XEmacs sources). Once installed, XEmacs occupies about 50 Mb in the
32 where it is installed; this includes the executable files, Lisp libraries, 32 file system where it is installed; this includes the executable files,
33 miscellaneous data files, and on-line documentation. The amount of storage 33 Lisp libraries, miscellaneous data files, and on-line documentation.
34 of the Lisp directories may be reduced by compressing the .el files. If 34 The amount of storage of the Lisp directories may be reduced by
35 the building and installation take place in different directories, then 35 compressing the .el files. If the building and installation take place
36 the installation procedure momentarily requires 88+50 Mb. 36 in different directories, then the installation procedure temporarily
37 37 requires 88+50 Mb.
38 XEmacs requires an ANSI C compiler, such as LCC or GCC. 38
39 39 XEmacs requires an ANSI C compiler, such as GCC.
40 2) Consult `./etc/MACHINES' to see what configuration name you should 40
41 give to the `configure' program. That file offers hints for 41
42 getting around some possible installation problems. 42 2) Decide on what other software packages you would like to use with
43 43 XEmacs, but are not yet available on your system. On some systems,
44 3) In the top directory of the XEmacs distribution, run the program 44 Motif and CDE are optional additions. On Solaris, the SUNWaudmo
45 `configure' as follows: 45 package enables native sound support. There are also a number of free
46 46 software packages that XEmacs can use. If these are not yet available
47 ./configure CONFIGURATION-NAME [--OPTION[=VALUE]] ... 47 on your system, obtain, build and install those external packages
48 48 before building XEmacs. The packages XEmacs can use are:
49 The CONFIGURATION-NAME argument should be a configuration name given 49
50 in `./etc/MACHINES'. If omitted, `configure' will try to guess your 50 Xaw3d, XPM, JPEG, compface, PNG, zlib, OffiX, GNU DBM, Berkeley DB,
51 system type; if it cannot, you must find the appropriate configuration 51 socks, term, NAS, Canna, Wnn.
52 name in `./etc/MACHINES' and specify it explicitly. 52
53 You can get (most of) them from the XEmacs ftp site at
54 ftp://ftp.xemacs.org/pub/aux
55
56 If you want users on other systems to be able to use the XEmacs you
57 have built, try to build those packages so that the generated
58 libraries are statically linked.
59
60 Use the --site-includes and --site-libraries options when building
61 XEmacs to allow configure to find the external software packages.
62
63
64 3) In the top level directory of the XEmacs distribution, run the
65 program `configure' as follows:
66
67 ./configure [CONFIGURATION-NAME] [--OPTION[=VALUE]] ...
68
69 Usually, you should let `configure' (actually the shell script
70 `config.guess') guess your system type, by omitting the
71 CONFIGURATION-NAME argument. If you like to experiment, specify a
72 configuration name in the form MACHINE-VENDOR-OPSYS, for example:
73
74 sparc-sun-solaris2.6
75
76 See config.guess and configure.in for valid values for MACHINE,
77 VENDOR, and OPSYS. Also check `./etc/MACHINES' for advice on building
78 on particular machines.
53 79
54 If you don't want X support, specify `--with-x=no'. If you omit this 80 If you don't want X support, specify `--with-x=no'. If you omit this
55 option, `configure' will try to figure out for itself whether your 81 option, `configure' will try to autodetect whether your system has X,
56 system has X, and arrange to use it if present. 82 and arrange to use it if present.
57
58 Additional support can be included for the NeXTstep system by
59 specifying the flag `--with-ns'. This is not yet fully supported.
60 83
61 The `--x-includes=DIR' and `--x-libraries=DIR' options tell the build 84 The `--x-includes=DIR' and `--x-libraries=DIR' options tell the build
62 process where the compiler should look for the include files and 85 process where the compiler should look for the include files and
63 object libraries used with the X Window System. Normally, `configure' 86 object libraries used with the X Window System. Normally, `configure'
64 is able to find them; these options are necessary if you have your X 87 is able to find them; these options are necessary if you have your X
65 Window System files installed in unusual places. 88 Window System files installed in unusual places.
66 89
67 The `--site-includes=DIR' and `--site-libraries=DIR' options allow you 90 The `--site-includes=DIR' and `--site-libraries=DIR' options allow you
68 to specify additional places the compiler should look for include 91 to specify additional places the compiler should look for include
69 files and object libraries. You may specify multiple DIR's by 92 files and object libraries. You may specify multiple DIR's by
70 enclosing the list in quotes. On some systems (noticeably Solaris) you 93 enclosing the list in quotes. All the external packages you want to
71 may need to use `--site-runtime-libraries=DIR'. This will add -R 94 use with XEmacs (e.g. xpm, wnn, ...) described later should have their
72 versions of each path in addition to the -L versions. 95 include and library directories defined using these options.
96
97 The `--site-runtime-libraries=DIR' option specifies additional
98 directories to search for shared libraries at run time. This may be
99 necessary on some systems, or if you expect some of the libraries used
100 to build XEmacs to be in a different directory at run time than at
101 build time. Usually this will add a `-R' to each directory specified
102 and use that when linking XEmacs.
73 103
74 The `--with-gcc' option specifies that the build process should 104 The `--with-gcc' option specifies that the build process should
75 compile XEmacs using GCC. The `--with-lcc' option specifies that the 105 compile XEmacs using GCC. The `--compiler' option allows you to
76 build process should compile XEmacs using Lucid C. The `--compiler' 106 specify some other compiler to be used to compile XEmacs. If neither
77 option allows you to specify some other compiler to be used to compile 107 option is specified, the environment variable CC is used instead.
78 XEmacs. It is compatible with both the `--with-gcc' and `--with-lcc' 108 Otherwise the compiler will then default to 'cc'.
79 options, so if the compiler that you specify is a special version of
80 either gcc or lcc, then use the appropriate --with-gcc or --with-lcc
81 flag as well as the --compiler flag. If none of these flags is
82 specified, `configure' will search for GCC in your load path, and use
83 it if present. If you don't want to use GCC, specify `--with-gcc=no'
84 and the compiler will then default to 'cc'.
85 109
86 The `--cflags' option specifies the CFLAGS the build process should 110 The `--cflags' option specifies the CFLAGS the build process should
87 use when compiling XEmacs. If not used CFLAGS defaults to "-g -O" for 111 use when compiling XEmacs. Otherwise the value of the environment
88 gcc and "-g" for all other compilers. 112 variable CFLAGS is consulted. If that is also undefined, CFLAGS
113 defaults to "-g -O" for gcc and "-g" for all other compilers.
89 114
90 The `--with-gnu-make' option specifies that Makefiles should be 115 The `--with-gnu-make' option specifies that Makefiles should be
91 written to take advantage of special features of GNU Make. GNU Make 116 written to take advantage of special features of GNU Make. GNU Make
92 works fine on Makefiles even without this option. This flag just 117 works fine on Makefiles even without this option. This flag just
93 allows for simultaneous in-place and --srcdir building. 118 allows for simultaneous in-place and --srcdir building.
109 The `--prefix=PREFIXDIR' option specifies where the installation process 134 The `--prefix=PREFIXDIR' option specifies where the installation process
110 should put XEmacs and its data files. This defaults to `/usr/local'. 135 should put XEmacs and its data files. This defaults to `/usr/local'.
111 - XEmacs (and the other utilities users run) go in PREFIXDIR/bin 136 - XEmacs (and the other utilities users run) go in PREFIXDIR/bin
112 (unless the `--exec-prefix' option says otherwise). 137 (unless the `--exec-prefix' option says otherwise).
113 - The architecture-independent files go in PREFIXDIR/lib/xemacs-VERSION 138 - The architecture-independent files go in PREFIXDIR/lib/xemacs-VERSION
114 (where VERSION is the version number of XEmacs, like `19.14'). 139 (where VERSION is the version number of XEmacs, like `20.3').
115 - The architecture-dependent files go in 140 - The architecture-dependent files go in
116 PREFIXDIR/lib/xemacs-VERSION/CONFIGURATION 141 PREFIXDIR/lib/xemacs-VERSION/CONFIGURATION
117 (where CONFIGURATION is the configuration name, like mips-dec-ultrix4.2), 142 (where CONFIGURATION is the configuration name, like mips-dec-ultrix4.2),
118 unless the `--exec-prefix' option says otherwise. 143 unless the `--exec-prefix' option says otherwise.
119 144
125 EXECDIR/lib/xemacs-VERSION/CONFIGURATION. 150 EXECDIR/lib/xemacs-VERSION/CONFIGURATION.
126 EXECDIR/bin should be a directory that is normally in users' PATHs. 151 EXECDIR/bin should be a directory that is normally in users' PATHs.
127 152
128 For example, the command 153 For example, the command
129 154
130 ./configure mips-dec-ultrix --with-x 155 ./configure mips-dec-ultrix --with-x11=yes
131 156
132 configures XEmacs to build for a DECstation running Ultrix, with 157 configures XEmacs to build for a DECstation running Ultrix, with
133 support for the X11 window system. 158 support for the X11 window system.
134 159
135 The `--run-in-place' option will make the installed binaries reference
136 the source tree for the elisp files.
137
138 The `--with-menubars=TYPE' option allows you to specify which X 160 The `--with-menubars=TYPE' option allows you to specify which X
139 toolkit you wish to use for the menubar. The valid options are 161 toolkit you wish to use for the menubar. The valid options are
140 `lucid', `motif' and `none'. The default is `lucid' which is a 162 `lucid', `motif' and `no'. The default is `lucid' which is a
141 Motif-lookalike menubar. We highly recommend its usage over the real 163 Motif-lookalike menubar. We highly recommend its usage over the real
142 Motif menubar. (In fact, the Motif menubar is currently broken.) If 164 Motif menubar. (In fact, the Motif menubar is currently broken.) If
143 `none' is specified then support for menubars will not be compiled in. 165 `no' is specified then support for menubars will not be compiled in.
144 166
145 The `--with-scrollbars=TYPE' option allows you to specify which X 167 The `--with-scrollbars=TYPE' option allows you to specify which X
146 toolkit you wish to use for the scrollbars. The valid options are 168 toolkit you wish to use for the scrollbars. The valid options are
147 `lucid', `motif', `athena', `athena3d', and `none'. The default is 169 `lucid', `motif', `athena', `athena3d', and `no'. The default is
148 `lucid' which is a Motif-lookalike scrollbar. If `none' is specified 170 `lucid' which is a Motif-lookalike scrollbar. If `no' is specified
149 then support for scrollbars will not be compiled in. 171 then support for scrollbars will not be compiled in.
150 172
151 The `--with-dialogs=TYPE' option allows you to specify which X toolkit 173 The `--with-dialogs=TYPE' option allows you to specify which X toolkit
152 you wish to use for the scrollbars. The valid options are `athena', 174 you wish to use for the scrollbars. The valid options are `athena',
153 `motif, and `none. The `lucid' option is accepted and will result in 175 `motif, and `no. The `lucid' option is accepted and will result in
154 the `athena' toolkit being used. If the Motif toolkit can be found 176 the `athena' toolkit being used. If the Motif toolkit can be found
155 the default is `motif'. Otherwise, the default is `athena'. If 177 the default is `motif'. Otherwise, the default is `athena'. If
156 `none' is specified then support for dialog boxes will not be compiled 178 `no' is specified then support for dialog boxes will not be compiled
157 in. 179 in.
158 180
159 The `--with-toolbars' option allows you to enable or disable toolbar 181 The `--with-toolbars' option allows you to enable or disable toolbar
160 support. The default is `yes' as long as support for a windowing 182 support. The default is `yes' as long as support for a windowing
161 system is included. 183 system is included.
162 184
163 The `--with-xpm' option specifies that XEmacs should support X 185 The `--with-gif' option specifies that XEmacs should support GIF image
186 conversion. No extra libraries are required. This options defaults
187 to `yes'.
188
189 The `--with-xpm' option specifies that XEmacs should support X11
164 Pixmaps. `configure' will attempt to detect if you have the Xpm 190 Pixmaps. `configure' will attempt to detect if you have the Xpm
165 libraries and define `--with-xpm' for you. 191 libraries and define `--with-xpm' for you.
166 192
167 The `--with-xface' option specifies that XEmacs should support 193 The `--with-xface' option specifies that XEmacs should support
168 X-Faces. `configure' will attempt to detect if you have the compface 194 X-Faces. `configure' will attempt to detect if you have the compface
169 library and define `--with-xface' for you. 195 library and define `--with-xface' for you.
170
171 The `--with-gif' option specifies that XEmacs should support GIF image
172 conversion. No extra libraries are required. This options defaults
173 to `yes'.
174 196
175 The `--with-jpeg' option specifies that XEmacs should support JPEG 197 The `--with-jpeg' option specifies that XEmacs should support JPEG
176 image conversion. This option requires libjpeg from the Independent 198 image conversion. This option requires libjpeg from the Independent
177 JPEG Group which is available on the XEmacs ftp site. `configure' 199 JPEG Group which is available on the XEmacs ftp site. `configure'
178 will attempt to detect if you have libjpeg and define `--with-jpeg' 200 will attempt to detect if you have libjpeg and define `--with-jpeg'
179 for you. 201 for you.
180 202
181 The `--with-png option specifies that XEmacs should support PNG image 203 The `--with-png' option specifies that XEmacs should support PNG image
182 conversion. The valid options at `yes', `no' and `gnuz'. This option 204 conversion. The valid options are `yes' and `no'. This option
183 requires libpng which is available on the XEmacs ftp site. This 205 requires libpng which is available on the XEmacs ftp site. This
184 option also requires a decompression library, either libz or libgz. 206 option also requires a decompression library, either libz or
185 The default is to use libz. Specify `gnuz' as the option to use libgz 207 libgz. XEmacs will detect whether libz is available, and use that,
186 instead. `configure' will attempt to detect if you have libpng and 208 else it will use libgz.
187 define `--with-png' for you.
188 209
189 The `--with-database' option specifies that XEmacs should be built 210 The `--with-database' option specifies that XEmacs should be built
190 with additional database support. The valid options are `no' or a 211 with additional database support. The valid options are `no' or a
191 comma-separated list of one or more of `dbm', `gnudbm' or `berkdb'. 212 comma-separated list of one or more of `dbm', `gnudbm' or `berkdb'.
192 `configure' will attempt to detect the necessary libraries and header 213 `configure' will attempt to detect the necessary libraries and header
193 files and define `--with-database' for you. 214 files and define `--with-database' for you.
194 215
195 The `--with-socks' option specifies that XEmacs should be built with 216 The `--with-socks' option specifies that XEmacs should be built with
196 SOCKS support. 217 SOCKS support. This requires the libsocks library.
197 218
198 The `--with-term' option specifies that XEmacs should be built with 219 The `--with-term' option specifies that XEmacs should be built with
199 TERM support. TERM is a way to multiplex serial lines over a simple 220 TERM support. TERM is a way to multiplex serial lines over a simple
200 dialup connection, used on Linux and other systems. We cannot 221 dialup connection, used on Linux and other systems. We cannot
201 guarantee that our TERM support coexists well with standard Internet 222 guarantee that our TERM support coexists well with standard Internet
204 The `--with-tooltalk' option specifies that XEmacs should be built 225 The `--with-tooltalk' option specifies that XEmacs should be built
205 with ToolTalk support for interconnecting with other applications. 226 with ToolTalk support for interconnecting with other applications.
206 ToolTalk is not yet supported on all architectures. 227 ToolTalk is not yet supported on all architectures.
207 228
208 The `--with-sparcworks' option specifies that XEmacs should be built 229 The `--with-sparcworks' option specifies that XEmacs should be built
209 with support for Sun Sparcworks 3.0.1 and up. This functionality is 230 with support for Sun Sparcworks 3.0.1 and up (including Sun WorkShop).
210 only of use on SunOS 4.1.x and Solaris 2.x systems. 231 This functionality is only of use on SunOS 4.1.x and Solaris 2.x
211 232 systems.
212 The `--with-cde option allows you to enable or disable CDE drag and 233
234 The `--with-cde' option allows you to enable or disable CDE drag and
213 drop support. `configure' will attempt to detect this option and 235 drop support. `configure' will attempt to detect this option and
214 define `--with-cde' for you. 236 define `--with-cde' for you.
215 237
216 The `--with-offix option allows you to enable or disable OffiX drag and 238 The `--with-offix' option allows you to enable or disable OffiX drag and
217 drop support. `configure' will attempt to detect this option and 239 drop support. `configure' will attempt to detect this option and
218 define `--with-offix' for you. 240 define `--with-offix' for you.
219 241
220 The `--with-energize' option specifies that XEmacs should be built 242 The `--with-energize' option specifies that XEmacs should be built
221 with support for the Lucid Energize system. (If you have not 243 with support for the Lucid Energize system. (If you have not
222 purchased Energize, specifying this option won't gain you anything.) 244 purchased Energize, specifying this option won't gain you anything.)
223 Currently this doesn't work. 245 Currently this doesn't work.
224 246
225 The `--external-widget' option specifies that XEmacs should be built 247 The `--external-widget' option specifies that XEmacs should be built
226 with support for being used as a widget. This functionality should be 248 with support for being used as a widget by other X11 applications.
227 considered beta. 249 This functionality should be considered beta.
228 250
229 The `--with-mocklisp' option specifies that XEmacs should be built 251 The `--with-mocklisp' option specifies that XEmacs should be built
230 with support for Mocklisp. Do not use this option unless you have a 252 with support for Mocklisp. Do not use this option unless you have a
231 Mocklisp program that you need to run. 253 Mocklisp program that you need to run.
232 254
238 parameter is deprecated and, in fact, ignored. 260 parameter is deprecated and, in fact, ignored.
239 261
240 The `--with-sound=TYPE' option specifies that XEmacs should be built 262 The `--with-sound=TYPE' option specifies that XEmacs should be built
241 with sound support. Native (`--with-sound=native') sound support is 263 with sound support. Native (`--with-sound=native') sound support is
242 currently available only on Sun SparcStations, SGI's, HP9000s, and 264 currently available only on Sun SparcStations, SGI's, HP9000s, and
243 Linux. Network Audio Support (NAS) (`--with-sound=nas' or 265 systems (such as Linux) with soundcard.h. Network Audio Support (NAS)
244 `--with-sound=both') is an extension to X that you may or may not have 266 (`--with-sound=nas' or `--with-sound=both') is an extension to X that
245 for your system. For NAS, you will probably need to provide the paths 267 you may or may not have for your system. For NAS, you will probably
246 to the nas include and library directories to configure. `configure' 268 need to provide the paths to the nas include and library directories
247 will attempt to determine if your configuration supports sound and 269 to configure. If `--with-sound' is not specified, `configure' will
270 attempt to determine if your configuration supports native sound and
248 define --with-sound for you. If your native sound library is not in a 271 define --with-sound for you. If your native sound library is not in a
249 standard location you can specify where it is with the 272 standard location you can specify it with the `--native-sound-lib=LIB'
250 `--native-sound-lib=LIB' flag. For Linux, `/dev/audio' is required 273 flag. For Linux, `/dev/audio' is required for SunAudio files and
251 for SunAudio files and `/dev/dsp' is required for raw data and WAVE 274 `/dev/dsp' is required for raw data and WAVE format files.
252 format files.
253 275
254 The `--rel-alloc' option can be used to either enable or disable use 276 The `--rel-alloc' option can be used to either enable or disable use
255 of the relocating allocator. Generally, it's best to go with the 277 of the relocating allocator. Generally, it's best to go with the
256 default configuration for your system. 278 default configuration for your system.
257 279
258 The `--use-system-malloc' option can be use to either enable or 280 The `--use-system-malloc' option can be use to either enable or
259 disable use of the relocating allocator. Generally, it's best to go 281 disable use of the system malloc. Generally, it's best to go with the
260 with the default configuration for your system. Note that on many 282 default configuration for your system. Note that on many systems
261 systems using the system malloc disables the use of the relocating 283 using the system malloc disables the use of the relocating allocator.
262 allocator.
263
264 The `--with-epoch' option enables functionality taken from Epoch.
265 Currently this doesn't work.
266 284
267 The `--debug' and `--error-checking' options are intended for use only 285 The `--debug' and `--error-checking' options are intended for use only
268 by the developers. `--debug' adds code to be compiled in for 286 by the developers. `--debug' adds code to be compiled in for
269 performing various tests. `--error-checking' adds additional tests to 287 performing various tests. `--error-checking' adds additional tests to
270 many of the commonly used macros. 288 many of the commonly used macros.
271 289
272 The `--verbose' and `--extra-verbose' options are intended for use 290 The `--verbose' and `--extra-verbose' options are intended for use
273 only by the developers. `--verbose' causes the results of all 291 only by the developers. `--verbose' causes the results of all
274 configure tests to be displayed. `--extra-verbose' also displays the 292 configure tests to be displayed. `--extra-verbose' displays
275 output of any compiler invocations done by configure. 293 additional information, useful for debugging. Another help for
294 determining configure failures is the file `config.log', which
295 contains the results of the compile and link tests used by configure.
296
297 The `--with-mule' option enables (MUlti-Lingual Emacs) support, needed
298 to suport non-Latin-1 (including Asian) languages. The Mule support
299 is not yet as stable or efficient as the `Latin1' support. The
300 following options require Mule support:
301
302 The `--with-xim' option enables use of the X11 XIM mechanism to allow
303 an input method to input text into XEmacs. The input method is shared
304 among all the X applications sharing an X display and using the same
305 language. The XIM support comes in 2 flavors: motif, and xlib. If
306 Motif support (the XmIm* set of functions) is available, it is
307 preferred when available. The xlib XIM support does not work quite as
308 well, so by default if the XmIm* routines are autodetected, then the
309 default is `--with-xim=motif', else `--with-xim=no'.
310
311 The `--with-canna' option enables the use of the Canna Japanese input
312 method.
276 313
277 The `--with-wnn' and `--with-wnn6' options are for compiling with the 314 The `--with-wnn' and `--with-wnn6' options are for compiling with the
278 Wnn multi-language input method. `--with-wnn' is for compiling 315 Wnn multi-language input method. `--with-wnn' is for compiling with
279 against Wnn-4.2 the free version of WNN. This is beta level code. 316 Wnn-4.2, the free version of WNN. This is beta level code.
280 `--with-wnn6' is for compiling against WNN6 the commercial version of 317 `--with-wnn6' is for compiling against WNN6, the commercial version
281 WNN. This is alpha level code and very lightly tested at present. 318 of WNN. This is alpha level code and very lightly tested at present.
282 319
283 The `--wnn-includes=DIR' and `wnn-libraries=DIR' options are provided 320 `configure' doesn't do any compilation or installation itself. It
284 for specifying information about where to find WNN include directories 321 just creates the files that influence those things: `./src/config.h',
285 and WNN libraries. Currently you need to specify wnn-includes in most 322 and all the Makefile's in the build tree.
286 installations of Wnn-4.2.
287 323
288 The `--with-pop', `--with-hesiod', and `--with-kerberos' options are used 324 The `--with-pop', `--with-hesiod', and `--with-kerberos' options are used
289 in conjunction with movemail. As of XEmacs 20.1, movemail is identical 325 in conjunction with movemail. As of XEmacs 20.1, movemail is identical
290 to the one used in Emacs. 326 to the one used in Emacs.
291
292 `configure' doesn't do any compilation or installation
293 itself. It just creates the files that influence those things:
294 `./Makefile', `src/Makefile', `lwlib/Makefile', `lib-src/Makefile',
295 `man/Makefile', `dynodump/Makefile', and `./src/config.h'. For
296 details on exactly what it does, see the section called `CONFIGURATION
297 BY HAND', below.
298 327
299 When it is done, `configure' prints a description of what it did and 328 When it is done, `configure' prints a description of what it did and
300 creates a shell script `config.status' which, when run, recreates the 329 creates a shell script `config.status' which, when run, recreates the
301 same configuration. If `configure' exits with an error after 330 same configuration. If `configure' exits with an error after
302 disturbing the status quo, it removes `config.status'. 331 disturbing the status quo, it removes `config.status'.
303
304 The work of `configure' can be done by editing various files in the
305 distribution, but using `configure' is supposed to be simpler. See
306 the section called "CONFIGURATION BY HAND" below if you want to do the
307 configuration yourself.
308 332
309 4) Look at `./lisp/paths.el'; if some of those values are not right 333 4) Look at `./lisp/paths.el'; if some of those values are not right
310 for your system, set up the file `./lisp/site-init.el' with XEmacs 334 for your system, set up the file `./lisp/site-init.el' with XEmacs
311 Lisp code to override them; it is not a good idea to edit paths.el 335 Lisp code to override them; it is not a good idea to edit paths.el
312 itself. YOU MUST USE THE LISP FUNCTION `setq' TO ASSIGN VALUES, 336 itself. YOU MUST USE THE LISP FUNCTION `setq' TO ASSIGN VALUES,