|
278
|
1 -*- mode:outline -*-
|
|
|
2
|
|
0
|
3 This file describes various problems that have been encountered
|
|
197
|
4 in compiling, installing and running XEmacs. It has been updated for
|
|
1332
|
5 XEmacs 21.5.
|
|
0
|
6
|
|
278
|
7 This file is rather large, but we have tried to sort the entries by
|
|
|
8 their respective relevance for XEmacs, but may have not succeeded
|
|
|
9 completely in that task. The file is divided into four parts:
|
|
124
|
10
|
|
197
|
11 - Problems with building XEmacs
|
|
|
12 - Problems with running XEmacs
|
|
|
13 - Compatibility problems
|
|
|
14 - Mule issues
|
|
120
|
15
|
|
197
|
16 Use `C-c C-f' to move to the next equal level of outline, and
|
|
223
|
17 `C-c C-b' to move to previous equal level. `C-h m' will give more
|
|
|
18 info about the Outline mode.
|
|
120
|
19
|
|
197
|
20 Also, Try finding the things you need using one of the search commands
|
|
|
21 XEmacs provides (e.g. `C-s').
|
|
|
22
|
|
524
|
23 General advice:
|
|
957
|
24
|
|
524
|
25 WATCH OUT for your init file! (~/.xemacs/init.el or ~/.emacs) If
|
|
|
26 you observe strange problems, invoke XEmacs with the `-vanilla'
|
|
|
27 option and see if you can repeat the problem.
|
|
197
|
28
|
|
957
|
29 Note that most of the problems described here manifest at RUN
|
|
|
30 time, even those described as BUILD problems. It is quite unusual
|
|
|
31 for a released XEmacs to fail to build. So a "build problem"
|
|
|
32 requires you to tweak the build environment, then rebuild XEmacs.
|
|
|
33 A "runtime problem" is one that can be fixed by proper
|
|
|
34 configuration of the existing build. Compatibility problems and
|
|
|
35 Mule issues are generally runtime problems, but are treated
|
|
|
36 separately for convenience.
|
|
|
37
|
|
120
|
38
|
|
124
|
39 * Problems with building XEmacs
|
|
197
|
40 ===============================
|
|
0
|
41
|
|
373
|
42 ** General
|
|
1245
|
43
|
|
915
|
44 Much general information is in INSTALL. If it's covered in
|
|
|
45 INSTALL, we don't repeat it here.
|
|
|
46
|
|
3404
|
47 *** X11/bitmaps/gray (or other X11-related file) not found.
|
|
|
48
|
|
|
49 The X11R6 distribution was monolithic, but the X11R7 distribution is
|
|
|
50 much more modular. Many OS distributions omit these bitmaps (assuming
|
|
|
51 nobody uses them, evidently). Your OS distribution should have a
|
|
|
52 developer's package containing these files, probably with a name
|
|
|
53 containing the string "bitmap". Known package names (you may need to
|
|
|
54 add an extension such as .deb or .rpm) include x11/xbitmaps (Ubuntu)
|
|
|
55 and xorg-x11-xbitmaps (Fedora Core 5).
|
|
|
56
|
|
1098
|
57 *** How do I configure to get the buffer tabs/progress bars?
|
|
915
|
58
|
|
|
59 These features depend on support for "native widgets". Use the
|
|
2648
|
60 --enable-widgets option to configure. Configuration of widgets is
|
|
915
|
61 automatic for "modern" toolkits (MS Windows, GTK, and Motif), but if
|
|
|
62 you are using Xt and the Athena widgets, you will probably want to
|
|
|
63 specify a "3d" widget set. See configure --usage, and don't forget to
|
|
|
64 install the corresponding development libraries.
|
|
|
65
|
|
|
66 *** I know I have libfoo installed, but configure doesn't find it.
|
|
|
67
|
|
|
68 Typical of Linux systems with package managers. To link with a shared
|
|
|
69 library, you only need the shared library. To compile objects that
|
|
|
70 link with it, you need the headers---and distros don't provide them with
|
|
|
71 the libraries. You need the additional "development" package, too.
|
|
|
72
|
|
373
|
73 *** When using gcc, you get the error message "undefined symbol __fixunsdfsi".
|
|
|
74 When using gcc, you get the error message "undefined symbol __main".
|
|
|
75
|
|
|
76 This means that you need to link with the gcc library. It may be called
|
|
|
77 "gcc-gnulib" or "libgcc.a"; figure out where it is, and define LIB_GCC in
|
|
|
78 config.h to point to it.
|
|
|
79
|
|
|
80 It may also work to use the GCC version of `ld' instead of the standard one.
|
|
|
81
|
|
|
82 *** Excessive optimization with pgcc can break XEmacs
|
|
124
|
83
|
|
|
84 It has been reported on some systems that compiling with -O6 can lead
|
|
|
85 to XEmacs failures. The workaround is to use a lower optimization
|
|
|
86 level. -O2 and -O4 have been tested extensively.
|
|
|
87
|
|
229
|
88 All of this depends heavily on the version of pgcc and the version
|
|
|
89 of libc. Snapshots near the release of pgcc-1.0 have been tested
|
|
|
90 extensively and no sign of breakage has been seen on systems using
|
|
|
91 glibc-2.
|
|
|
92
|
|
373
|
93 *** src/Makefile and lib-src/Makefile are truncated--most of the file missing.
|
|
229
|
94
|
|
373
|
95 This can happen if configure uses GNU sed version 2.03. That version
|
|
|
96 had a bug. GNU sed version 2.05 works properly.
|
|
124
|
97
|
|
373
|
98 *** When compiling with X11, you get "undefined symbol _XtStrings".
|
|
124
|
99
|
|
373
|
100 This means that you are trying to link emacs against the X11r4 version of
|
|
|
101 libXt.a, but you have compiled either Emacs or the code in the lwlib
|
|
|
102 subdirectory with the X11r5 header files. That doesn't work.
|
|
124
|
103
|
|
373
|
104 Remember, you can't compile lwlib for r4 and emacs for r5, or vice versa.
|
|
|
105 They must be in sync.
|
|
124
|
106
|
|
373
|
107 *** test-distrib says that the distribution has been clobbered
|
|
197
|
108 or, temacs prints "Command key out of range 0-127"
|
|
|
109 or, temacs runs and dumps xemacs, but xemacs totally fails to work.
|
|
|
110 or, temacs gets errors dumping xemacs
|
|
|
111
|
|
|
112 This can be because the .elc files have been garbled. Do not be
|
|
|
113 fooled by the fact that most of a .elc file is text: these are binary
|
|
|
114 files and can contain all 256 byte values.
|
|
|
115
|
|
|
116 In particular `shar' cannot be used for transmitting GNU Emacs. It
|
|
|
117 typically truncates "lines". (this does not apply to GNU shar, which
|
|
|
118 uses uuencode to encode binary files.)
|
|
|
119
|
|
|
120 If you have a copy of Emacs that has been damaged in its nonprinting
|
|
|
121 characters, you can fix them by running:
|
|
|
122
|
|
|
123 make all-elc
|
|
|
124
|
|
|
125 This will rebuild all the needed .elc files.
|
|
|
126
|
|
1318
|
127 ** Intel Architecture General
|
|
|
128
|
|
|
129 *** Don't use -O2 or -O3 with Cygwin 1.0, CodeFusion-99070 or gcc 2.7.2 on x86
|
|
|
130 without also using `-fno-strength-reduce'.
|
|
|
131
|
|
|
132 gcc will generate incorrect code otherwise. This bug is present in at
|
|
|
133 least 2.6.x and 2.7.[0-2]. This bug has been fixed in GCC 2.7.2.1 and
|
|
|
134 later. This bug is O/S independent, but is limited to x86 architectures.
|
|
|
135
|
|
|
136 This problem is known to be fixed in egcs (or pgcc) 1.0 or later.
|
|
|
137
|
|
|
138 Unfortunately, later releases of Cygnus-released compilers (not the
|
|
|
139 Net-released ones) have a bug with the same `problem signature'.
|
|
|
140
|
|
|
141 If you're lucky, you'll get an error while compiling that looks like:
|
|
|
142
|
|
|
143 event-stream.c:3189: internal error--unrecognizable insn:
|
|
|
144 (insn 256 14 15 (set (reg/v:SI 24)
|
|
|
145 (minus:SI (reg/v:SI 25)
|
|
|
146 (const_int 2))) -1 (insn_list 11 (nil))
|
|
|
147 (nil))
|
|
|
148 0 0 [main]
|
|
|
149
|
|
|
150 If you're unlucky, your code will simply execute incorrectly.
|
|
|
151
|
|
|
152 *** Don't use -O2 with gcc 2.7.2 under Intel architectures without also
|
|
|
153 using `-fno-caller-saves'.
|
|
|
154
|
|
|
155 gcc will generate incorrect code otherwise. This bug is still
|
|
|
156 present in gcc 2.7.2.3. There have been no reports to indicate the
|
|
|
157 bug is present in egcs 1.0 (or pgcc 1.0) or later. This bug is O/S
|
|
|
158 independent, but limited to x86 architectures.
|
|
|
159
|
|
|
160 This problem is known to be fixed in egcs (or pgcc) 1.0 or later.
|
|
|
161
|
|
373
|
162 *** `compress' and `uncompress' not found and XFree86
|
|
|
163
|
|
|
164 XFree86 installs a very old version of libz.a by default ahead of where
|
|
|
165 more modern version of libz might be installed. This will cause problems
|
|
|
166 when attempting to link against libMagick. The fix is to remove the old
|
|
|
167 libz.a in the X11 binary directory.
|
|
|
168
|
|
|
169
|
|
1245
|
170 ** Motif
|
|
|
171
|
|
|
172 Motif is the X11 version of the Gnus torture test: if there's a way to
|
|
|
173 crash, Motif will find it. With the open source release of Motif, it
|
|
|
174 seems like a good idea to collect all Motif-related issues in one
|
|
|
175 place.
|
|
|
176
|
|
|
177 You should also look in your OS's section, as it may not be Motif's
|
|
|
178 fault.
|
|
|
179
|
|
|
180 *** XEmacs crashes on exit (#1).
|
|
|
181
|
|
|
182 The backtrace is something like:
|
|
|
183
|
|
|
184 (gdb) where
|
|
|
185 #0 0xfeb9a480 in _libc_kill () from /usr/lib/libc.so.1
|
|
|
186 #1 0x000b0388 in fatal_error_signal ()
|
|
|
187 #2 <signal handler called>
|
|
|
188 #3 YowIter (ht=0xb, id=0x0, v=0x74682074, client=0x47e3c0)
|
|
|
189 at ImageCache.c:1159
|
|
|
190 #4 0xff26cc5c in _LTHashTableForEachItem (ht=0x4725e8,
|
|
|
191 iter=0xff26dda0 <YowIter>, ClientData=0x47e3c0) at Hash.c:671
|
|
|
192 #5 0xff2a4664 in destroy (w=0x496550) at Screen.c:352
|
|
|
193 #6 0xfef92118 in Phase2Destroy () from /usr/openwin/lib/libXt.so.4
|
|
|
194 #7 0xfef91940 in Recursive () from /usr/openwin/lib/libXt.so.4
|
|
|
195 #8 0xfef91e44 in XtPhase2Destroy () from /usr/openwin/lib/libXt.so.4
|
|
|
196 #9 0xfef91ae8 in _XtDoPhase2Destroy () from /usr/openwin/lib/libXt.so.4
|
|
|
197 #10 0xfef918cc in XtDestroyWidget () from /usr/openwin/lib/libXt.so.4
|
|
|
198 #11 0xfef91438 in CloseDisplay () from /usr/openwin/lib/libXt.so.4
|
|
|
199 #12 0xfef91394 in XtCloseDisplay () from /usr/openwin/lib/libXt.so.4
|
|
|
200 #13 0x0025b8b0 in x_delete_device ()
|
|
|
201 #14 0x000940b0 in delete_device_internal ()
|
|
|
202 #15 0x000806a0 in delete_console_internal ()
|
|
|
203
|
|
|
204 This is known to happen with Lesstif version 0.93.36. Similar
|
|
|
205 backtraces have also been observed on HP/UX and Solaris. There is a
|
|
|
206 patch for Lesstif. (This is not a solution; it just stops the crash.
|
|
|
207 It may or may not be harmless, but "it works for the author".)
|
|
|
208
|
|
|
209 Note that this backtrace looks a lot like the one in the next item.
|
|
|
210 However, this one is invulnerable to the Solaris patches mentioned there.
|
|
|
211
|
|
|
212 Frank McIngvale <frankm@hiwaay.net> says:
|
|
|
213
|
|
|
214 Ok, 0.93.34 works, and I tracked down the crash to a section
|
|
|
215 marked "experimental" in 0.93.36. Patch attached, "works for me".
|
|
|
216
|
|
|
217 diff -u -r lesstif-0.93.36/lib/Xm/ImageCache.c lesstif-0.93.36-mod/lib/Xm/ImageCache.c
|
|
|
218 --- lesstif-0.93.36/lib/Xm/ImageCache.c 2002-08-05 14:53:24.000000000 -0500
|
|
|
219 +++ lesstif-0.93.36-mod/lib/Xm/ImageCache.c 2002-11-11 11:13:12.000000000 -0600
|
|
|
220 @@ -1166,5 +1166,4 @@
|
|
|
221 DEBUGOUT(_LtDebug0(__FILE__, NULL, "_LtImageCacheScreenDestroy (XmGetPixmapByDepth) %p\n",
|
|
|
222 s));
|
|
|
223
|
|
|
224 - (void) _LTHashTableForEachItem(PixmapCache, YowIter, (XtPointer)s);
|
|
|
225 }
|
|
|
226
|
|
|
227 *** XEmacs crashes on exit (#2)
|
|
|
228
|
|
|
229 Especially frequent with multiple frames. Crashes that produce C
|
|
|
230 backtraces like this:
|
|
|
231
|
|
|
232 #0 0xfec9a118 in _libc_kill () from /usr/lib/libc.so.1
|
|
|
233 #1 0x77f48 in fatal_error_signal (sig=11)
|
|
|
234 at /codes/rpluim/xemacs-21.4/src/emacs.c:539
|
|
|
235 #2 <signal handler called>
|
|
|
236 #3 0xfee929f4 in XFindContext () from /usr/openwin/lib/libX11.so.4
|
|
|
237 #4 0xfee92930 in XFindContext () from /usr/openwin/lib/libX11.so.4
|
|
|
238 #5 0xff297e54 in DisplayDestroy () from /usr/dt/lib/libXm.so.4
|
|
|
239 #6 0xfefbece0 in XtCallCallbackList () from /usr/openwin/lib/libXt.so.4
|
|
|
240 #7 0xfefc486c in XtPhase2Destroy () from /usr/openwin/lib/libXt.so.4
|
|
|
241 #8 0xfefc45d0 in _XtDoPhase2Destroy () from /usr/openwin/lib/libXt.so.4
|
|
|
242 #9 0xfefc43b4 in XtDestroyWidget () from /usr/openwin/lib/libXt.so.4
|
|
|
243 #10 0x15cf9c in x_delete_device (d=0x523f00)
|
|
|
244
|
|
|
245 are caused by buggy Motif libraries. Installing the following patches
|
|
|
246 has been reported to solve the problem on Solaris 2.7:
|
|
|
247
|
|
|
248 107081-40 107656-07
|
|
|
249
|
|
|
250 For information (although they have not been confirmed to work), the
|
|
|
251 equivalent patches for Solaris 2.8 are:
|
|
|
252
|
|
|
253 108940-33 108652-25
|
|
|
254
|
|
|
255 *** On HP-UX 11.0 XEmacs causes excessive X11 errors when running.
|
|
|
256 (also appears on AIX as reported in comp.emacs.xemacs)
|
|
|
257
|
|
|
258 Marcus Thiessel <marcus@xemacs.org>
|
|
|
259
|
|
|
260 Unfortunately, XEmacs releases prior to 21.0 don't work with
|
|
|
261 Motif2.1. It will compile but you will get excessive X11 errors like
|
|
|
262
|
|
|
263 xemacs: X Error of failed request: BadGC (invalid GC parameter)
|
|
|
264
|
|
|
265 and finally XEmacs gets killed. A workaround is to use the
|
|
|
266 Motif1.2_R6 libraries. You can the following line to your call to
|
|
|
267 configure:
|
|
|
268
|
|
|
269 --x-libraries="/usr/lib/Motif1.2_R6 -L/usr/lib/X11R6"
|
|
|
270
|
|
|
271 Make sure /usr/lib/Motif1.2_R6/libXm.sl is a link to
|
|
|
272 /usr/lib/Motif1.2_R6/libXm.3.
|
|
|
273
|
|
|
274 *** On HP-UX 11.0: Object "" does not have windowed ancestor
|
|
|
275
|
|
|
276 Marcus Thiessel <marcus@xemacs.org>
|
|
|
277
|
|
|
278 XEmacs dies without core file and reports:
|
|
|
279
|
|
|
280 Error: Object "" does not have windowed ancestor.
|
|
|
281
|
|
|
282 This is a bug. Please apply the patch PHSS_19964 (check if
|
|
|
283 superseded). The other alternative is to link with Motif1.2_R6 (see
|
|
|
284 previous item).
|
|
|
285
|
|
|
286 *** Motif dialog boxes lose on Irix.
|
|
|
287
|
|
|
288 Larry Auton <lda@control.att.com> writes:
|
|
|
289 Beware of not specifying
|
|
|
290
|
|
2648
|
291 --enable-dialogs=athena
|
|
1245
|
292
|
|
|
293 if it builds with the motif dialogs [boom!] you're a dead man.
|
|
|
294
|
|
|
295
|
|
373
|
296 ** AIX
|
|
1009
|
297 *** IBM compiler fails: "The character # is not a valid C source character."
|
|
|
298
|
|
|
299 Most recently observed in 21.5.9, due to USE_KKCC ifdefs (they just
|
|
|
300 happen to tickle the implementation).
|
|
|
301
|
|
|
302 Valdis Kletnieks says:
|
|
|
303
|
|
|
304 The problem is that IBM defines a *MACRO* called 'memcpy', and we
|
|
|
305 have stuck a #ifdef/#endif inside the macro call. As a workaround,
|
|
|
306 try adding '-U__STR__' to your CFLAGS - this will cause string.h to
|
|
|
307 not do a #define for strcpy() to __strcpy() - it uses this for
|
|
|
308 automatic inlining support.
|
|
|
309
|
|
|
310 (For the record, the same issue affects a number of other functions
|
|
|
311 defined in string.h - basically anything the compiler knows how to
|
|
|
312 inline.)
|
|
|
313
|
|
2648
|
314 *** On AIX 4.3, you must specify --enable-dialogs=athena with configure
|
|
373
|
315
|
|
442
|
316 *** The libXt shipped with AIX 4.3 up to 4.3.2 is broken. This causes
|
|
|
317 xemacs -nw to fail in various ways. The official APAR is this:
|
|
|
318
|
|
|
319 APAR NUMBER: <IX89470> RESOLVED AS: PROGRAM ERROR
|
|
|
320
|
|
|
321 ABSTRACT:
|
|
|
322 <IX89470>: LIBXT.A INCORRECT HANDLING OF EXCEPTIONS IN XTAPPADDINPUT
|
|
|
323
|
|
|
324 The solution is to install X11.base.lib at version >=4.3.2.5.
|
|
392
|
325
|
|
373
|
326 *** On AIX, you get this compiler error message:
|
|
|
327
|
|
|
328 Processing include file ./XMenuInt.h
|
|
|
329 1501-106: (S) Include file X11/Xlib.h not found.
|
|
|
330
|
|
|
331 This means your system was installed with only the X11 runtime i.d
|
|
|
332 libraries. You have to find your sipo (bootable tape) and install
|
|
|
333 X11Dev... with smit.
|
|
|
334
|
|
|
335 *** On AIX 4.1.2, linker error messages such as
|
|
|
336 ld: 0711-212 SEVERE ERROR: Symbol .__quous, found in the global symbol table
|
|
|
337 of archive /usr/lib/libIM.a, was not defined in archive member shr.o.
|
|
|
338
|
|
|
339 This is a problem in libIM.a. You can work around it by executing
|
|
|
340 these shell commands in the src subdirectory of the directory where
|
|
|
341 you build Emacs:
|
|
|
342
|
|
|
343 cp /usr/lib/libIM.a .
|
|
|
344 chmod 664 libIM.a
|
|
|
345 ranlib libIM.a
|
|
|
346
|
|
|
347 Then change -lIM to ./libIM.a in the command to link temacs (in
|
|
|
348 Makefile).
|
|
|
349
|
|
|
350 *** Excessive optimization on AIX 4.2 can lead to compiler failure.
|
|
|
351
|
|
|
352 Valdis.Kletnieks@vt.edu writes:
|
|
|
353 At least at the b34 level, and the latest-and-greatest IBM xlc
|
|
|
354 (3.1.4.4), there are problems with -O3. I haven't investigated
|
|
|
355 further.
|
|
|
356
|
|
|
357
|
|
|
358 ** SunOS/Solaris
|
|
1318
|
359 *** Don't use -O2 with gcc 2.8.1 and egcs 1.0 under SPARC architectures
|
|
|
360 without also using `-fno-schedule-insns'.
|
|
|
361
|
|
|
362 gcc will generate incorrect code otherwise, typically resulting in
|
|
|
363 crashes in the function skip-syntax-backward.
|
|
|
364
|
|
|
365 *** Don't use gcc-2.95.2 with -mcpu=ultrasparc on Solaris 2.6.
|
|
|
366
|
|
|
367 gcc will assume a 64-bit operating system, even though you've
|
|
|
368 merely told it to assume a 64-bit instruction set.
|
|
|
369
|
|
454
|
370 *** Dumping error when using GNU binutils / GNU ld on a Sun.
|
|
|
371
|
|
|
372 Errors similar to the following:
|
|
|
373
|
|
|
374 Dumping under the name xemacs unexec():
|
|
|
375 dldump(/space/rpluim/xemacs-obj/src/xemacs): ld.so.1: ./temacs:
|
|
|
376 fatal: /space/rpluim/xemacs-obj/src/xemacs: unknown dynamic entry:
|
|
|
377 1879048176
|
|
|
378
|
|
|
379 are caused by using GNU ld. There are several workarounds available:
|
|
|
380
|
|
|
381 In XEmacs 21.2 or later, configure using the new portable dumper
|
|
2648
|
382 (--enable-pdump).
|
|
454
|
383
|
|
|
384 Alternatively, you can link using the Sun version of ld, which is
|
|
|
385 normally held in /usr/ccs/bin. This can be done by one of:
|
|
|
386
|
|
|
387 - building gcc with these configure flags:
|
|
|
388 configure --with-ld=/usr/ccs/bin/ld --with-as=/usr/ccs/bin/as
|
|
|
389
|
|
|
390 - adding -B/usr/ccs/bin/ to CFLAGS used to configure XEmacs
|
|
|
391 (Note: The trailing '/' there is significant.)
|
|
|
392
|
|
|
393 - uninstalling GNU ld.
|
|
|
394
|
|
|
395 The Solaris2 FAQ claims:
|
|
|
396
|
|
|
397 When you install gcc, don't make the mistake of installing
|
|
|
398 GNU binutils or GNU libc, they are not as capable as their
|
|
|
399 counterparts you get with Solaris 2.x.
|
|
|
400
|
|
373
|
401 *** Link failure when using acc on a Sun.
|
|
|
402
|
|
|
403 To use acc, you need additional options just before the libraries, such as
|
|
|
404
|
|
|
405 /usr/lang/SC2.0.1/values-Xt.o -L/usr/lang/SC2.0.1/cg87 -L/usr/lang/SC2.0.1
|
|
|
406
|
|
|
407 and you need to add -lansi just before -lc.
|
|
|
408
|
|
|
409 The precise file names depend on the compiler version, so we
|
|
|
410 cannot easily arrange to supply them.
|
|
|
411
|
|
|
412 *** Problems finding X11 libraries on Solaris with Openwindows
|
|
|
413
|
|
|
414 Some users have reported problems in this area. The reported solution
|
|
|
415 is to define the environment variable OPENWINHOME, even if you must set
|
|
|
416 it to `/usr/openwin'.
|
|
|
417
|
|
|
418 *** Sed problems on Solaris 2.5
|
|
|
419
|
|
|
420 There have been reports of Sun sed truncating very lines in the
|
|
|
421 Makefile during configuration. The workaround is to use GNU sed or,
|
|
454
|
422 even better, think of a better way to generate Makefile, and send us a
|
|
373
|
423 patch. :-)
|
|
|
424
|
|
|
425 *** On Solaris 2 I get undefined symbols from libcurses.a.
|
|
|
426
|
|
|
427 You probably have /usr/ucblib/ on your LD_LIBRARY_PATH. Do the link with
|
|
|
428 LD_LIBRARY_PATH unset. Generally, avoid using any ucb* stuff when
|
|
|
429 building XEmacs.
|
|
|
430
|
|
|
431 *** On Solaris 2 I cannot make alloc.o, glyphs.o or process.o.
|
|
|
432
|
|
|
433 The SparcWorks C compiler may have difficulty building those modules
|
|
|
434 with optimization level -xO4. Try using only "-fast" optimization
|
|
|
435 for just those modules. (Or use gcc).
|
|
|
436
|
|
|
437 *** Solaris 2.3 /bin/sh coredumps during configuration.
|
|
|
438
|
|
|
439 This only occurs if you have LANG != C. This is a known bug with
|
|
|
440 /bin/sh fixed by installing Patch-ID# 101613-01. Or, you can use
|
|
1697
|
441 bash by setting the environment variable CONFIG_SHELL to /bin/bash
|
|
|
442
|
|
|
443 *** Solaris 2.x configure fails: ./config.status: test: argument expected
|
|
|
444
|
|
|
445 This is a known bug with /bin/sh and /bin/test, i.e. they do not
|
|
|
446 support the XPG4 standard. You can use bash as a workaround or an
|
|
|
447 XPG4-compliant Bourne shell such as the Sun-supplied /usr/xpg4/bin/sh
|
|
|
448 by setting the environment variable CONFIG_SHELL to /usr/xpg4/bin/sh
|
|
373
|
449
|
|
|
450 *** On SunOS, you get linker errors
|
|
454
|
451 ld: Undefined symbol
|
|
373
|
452 _get_wmShellWidgetClass
|
|
|
453 _get_applicationShellWidgetClass
|
|
|
454
|
|
|
455 The fix to this is to install patch 100573 for OpenWindows 3.0
|
|
|
456 or link libXmu statically.
|
|
|
457
|
|
|
458 *** On Sunos 4, you get the error ld: Undefined symbol __lib_version.
|
|
|
459
|
|
|
460 This is the result of using cc or gcc with the shared library meant
|
|
|
461 for acc (the Sunpro compiler). Check your LD_LIBRARY_PATH and delete
|
|
|
462 /usr/lang/SC2.0.1 or some similar directory.
|
|
|
463
|
|
|
464 *** Undefined symbols when linking on Sunos 4.1.
|
|
|
465
|
|
|
466 If you get the undefined symbols _atowc _wcslen, _iswprint, _iswspace,
|
|
|
467 _iswcntrl, _wcscpy, and _wcsncpy, then you need to add -lXwchar after
|
|
|
468 -lXaw in the command that links temacs.
|
|
|
469
|
|
|
470 This problem seems to arise only when the international language
|
|
|
471 extensions to X11R5 are installed.
|
|
|
472
|
|
|
473 *** On a Sun running SunOS 4.1.1, you get this error message from GNU ld:
|
|
|
474
|
|
454
|
475 /lib/libc.a(_Q_sub.o): Undefined symbol __Q_get_rp_rd referenced from text segment
|
|
373
|
476
|
|
|
477 The problem is in the Sun shared C library, not in GNU ld.
|
|
|
478
|
|
|
479 The solution is to install Patch-ID# 100267-03 from Sun.
|
|
|
480
|
|
|
481 *** SunOS 4.1.2: undefined symbol _get_wmShellWidgetClass
|
|
|
482
|
|
|
483 Apparently the version of libXmu.so.a that Sun ships is hosed: it's missing
|
|
454
|
484 some stuff that is in libXmu.a (the static version). Sun has a patch for
|
|
373
|
485 this, but a workaround is to use the static version of libXmu, by changing
|
|
|
486 the link command from "-lXmu" to "-Bstatic -lXmu -Bdynamic". If you have
|
|
|
487 OpenWindows 3.0, ask Sun for these patches:
|
|
|
488 100512-02 4.1.x OpenWindows 3.0 libXt Jumbo patch
|
|
|
489 100573-03 4.1.x OpenWindows 3.0 undefined symbols with shared libXmu
|
|
|
490
|
|
|
491 *** Random other SunOS 4.1.[12] link errors.
|
|
|
492
|
|
|
493 The X headers and libraries that Sun ships in /usr/{include,lib}/X11 are
|
|
|
494 broken. Use the ones in /usr/openwin/{include,lib} instead.
|
|
|
495
|
|
|
496 ** Linux
|
|
1318
|
497
|
|
|
498 See also Intel Architecture General, above.
|
|
|
499
|
|
|
500 *** egcs-1.1 on Alpha Linux
|
|
|
501
|
|
|
502 There have been reports of egcs-1.1 not compiling XEmacs correctly on
|
|
|
503 Alpha Linux. There have also been reports that egcs-1.0.3a is O.K.
|
|
|
504
|
|
373
|
505 *** Under Linux, you get "too many arguments to function `getpgrp'".
|
|
|
506
|
|
|
507 You have probably installed LessTiff under `/usr/local' and `libXm.so'
|
|
|
508 could not be found when linking `getpgrp()' test program, making XEmacs
|
|
|
509 think that `getpgrp()' takes an argument. Try adding `/usr/local/lib'
|
|
|
510 in `/etc/ld.so.conf' and run `ldconfig'. Then run XEmacs's `configure'
|
|
|
511 again. As with all problems of this type, reading the config.log file
|
|
|
512 generated from configure and seeing the log of how the test failed can
|
|
|
513 prove enlightening.
|
|
|
514
|
|
|
515 *** `Error: No ExtNode to pop!' on Linux systems with Lesstif.
|
|
197
|
516
|
|
|
517 This error message has been observed with lesstif-0.75a. It does not
|
|
|
518 appear to cause any harm.
|
|
|
519
|
|
373
|
520 *** xemacs: can't resolve symbol '__malloc_hook'
|
|
|
521
|
|
|
522 This is a Linux problem where you've compiled the XEmacs binary on a libc
|
|
|
523 5.4 with version higher than 5.4.19 and attempted to run the binary against
|
|
|
524 an earlier version. The solution is to upgrade your old library.
|
|
|
525
|
|
|
526 ** IRIX
|
|
452
|
527
|
|
1098
|
528 *** More coredumping in Irix (6.5 known to be vulnerable)
|
|
|
529
|
|
|
530 No fix is known yet. Here's the best information we have:
|
|
|
531
|
|
|
532 Valdis Kletnieks <Valdis.Kletnieks@vt.edu> writes:
|
|
|
533
|
|
|
534 Were xemacs and [any 3rd party, locally-compiled] libraries [you use]
|
|
|
535 all compiled with the same ABI ( -o32, -n32, -64) and
|
|
|
536 mips2/mips3/mips4 flags, and are they appropriate for the machine in
|
|
|
537 question? I know the IP30 implies an Octane, so it should be an R10K
|
|
|
538 chipset and above such nonsense, but I've seen the most astoundingly
|
|
|
539 bizzare crashes when somebody managed to compile with -mips4 and get
|
|
|
540 it to run on an R4400 or R5K system. ;)
|
|
|
541
|
|
|
542 Also, since you're using gcc, try re-running fixincludes and *then*
|
|
|
543 rebuilding xemacs and [any] libraries - mismatched headers can do that
|
|
|
544 sort of thing to you with little or no clue what's wrong (often you
|
|
|
545 get screwed when one routine does an malloc(sizeof(foo_struct)) and
|
|
|
546 passes the result to something that things foo_struct is a bit bigger,
|
|
|
547 trashing memory....
|
|
|
548
|
|
2648
|
549 Here's typical crash backtrace. With --enable-pdump, this occurs
|
|
|
550 usually at startup under X windows and xemacs -nw at least starts, while
|
|
|
551 without --pdump a similar crash is observed during build.
|
|
1098
|
552
|
|
|
553 #0 0x0fa460b8 in kill () at regcomp.c:637
|
|
|
554 637 regcomp.c: No such file or directory.
|
|
|
555 in regcomp.c
|
|
|
556 (gdb) where
|
|
|
557 #0 0x0fa460b8 in kill () at regcomp.c:637
|
|
|
558 #1 0x10087f34 in fatal_error_signal ()
|
|
|
559 (gdb) quit
|
|
|
560
|
|
|
561 This is confusing because there is no such file in the XEmacs
|
|
|
562 distribution. This is seen on (at least) the following configurations:
|
|
|
563
|
|
|
564 uname -a: IRIX64 oct202 6.5 01091821 IP30
|
|
|
565 XEmacs 21.4.9 "Informed Management" configured for `mips-sgi-irix6.5'.
|
|
|
566 XEmacs 21.5-b9 "brussels sprouts" configured for `mips-sgi-irix6.5'.
|
|
|
567
|
|
452
|
568 *** On Irix 6.5, the MIPSpro compiler gets an internal compiler error
|
|
|
569
|
|
|
570 The MIPSpro Compiler (at least version 7.2.1) can't seem to handle the
|
|
|
571 union type properly, and fails to compile src/glyphs.c. To avoid this
|
|
2648
|
572 problem, always build --enable-union-type=no (but that's the default, so
|
|
452
|
573 you should only see this problem if you're an XEmacs maintainer).
|
|
|
574
|
|
373
|
575 *** Linking with -rpath on IRIX.
|
|
124
|
576
|
|
|
577 Darrell Kindred <dkindred@cmu.edu> writes:
|
|
|
578 There are a couple of problems [with use of -rpath with Irix ld], though:
|
|
|
579
|
|
|
580 1. The ld in IRIX 5.3 ignores all but the last -rpath
|
|
|
581 spec, so the patched configure spits out a warning
|
|
2648
|
582 if --x-libraries or --with-site-runtime-libraries are
|
|
454
|
583 specified under irix 5.x, and it only adds -rpath
|
|
2648
|
584 entries for the --with-site-runtime-libraries. This bug was
|
|
124
|
585 fixed sometime between 5.3 and 6.2.
|
|
|
586
|
|
|
587 2. IRIX gcc 2.7.2 doesn't accept -rpath directly, so
|
|
|
588 it would have to be prefixed by -Xlinker or "-Wl,".
|
|
|
589 This would be fine, except that configure compiles with
|
|
|
590 ${CC-cc} $CFLAGS $LDFLAGS ...
|
|
|
591 rather than quoting $LDFLAGS with prefix-args, like
|
|
|
592 src/Makefile does. So if you specify --x-libraries
|
|
2648
|
593 or --with-site-runtime-libraries, you must use
|
|
|
594 --with--gcc=no, or configure will fail.
|
|
124
|
595
|
|
373
|
596 *** On Irix 6.3, the SGI ld quits with segmentation fault when linking temacs
|
|
207
|
597
|
|
|
598 This occurs if you use the SGI linker version 7.1. Installing the
|
|
|
599 patch SG0001872 fixes this problem.
|
|
197
|
600
|
|
373
|
601 *** On Irix 6.0, make tries (and fails) to build a program named unexelfsgi
|
|
|
602
|
|
|
603 A compiler bug inserts spaces into the string "unexelfsgi . o"
|
|
|
604 in src/Makefile. Edit src/Makefile, after configure is run,
|
|
|
605 find that string, and take out the spaces.
|
|
|
606
|
|
|
607 Compiler fixes in Irix 6.0.1 should eliminate this problem.
|
|
124
|
608
|
|
373
|
609 *** On Irix 5.2, unexelfsgi.c can't find cmplrs/stsupport.h.
|
|
124
|
610
|
|
373
|
611 The file cmplrs/stsupport.h was included in the wrong file set in the
|
|
|
612 Irix 5.2 distribution. You can find it in the optional fileset
|
|
|
613 compiler_dev, or copy it from some other Irix 5.2 system. A kludgy
|
|
|
614 workaround is to change unexelfsgi.c to include sym.h instead of
|
|
|
615 syms.h.
|
|
124
|
616
|
|
373
|
617 *** Coredumping in Irix 6.2
|
|
124
|
618
|
|
373
|
619 Pete Forman <gsez020@compo.bedford.waii.com> writes:
|
|
|
620 A problem noted by myself and others (I've lost the references) was
|
|
|
621 that XEmacs coredumped when the cut or copy toolbar buttons were
|
|
|
622 pressed. This has been fixed by loading the SGI patchset (Feb 98)
|
|
|
623 without having to recompile XEmacs.
|
|
124
|
624
|
|
373
|
625 My versions are XEmacs 20.3 (problem first noted in 19.15) and IRIX
|
|
|
626 6.2, compiled using -n32. I'd guess that the relevant individual
|
|
|
627 patch was "SG0002580: multiple fixes for X libraries". SGI recommends
|
|
|
628 that the complete patch set be installed rather than parts of it.
|
|
124
|
629
|
|
373
|
630 ** Digital UNIX/OSF/VMS
|
|
|
631 *** On Digital UNIX, the DEC C compiler might have a problem compiling
|
|
197
|
632 some files.
|
|
124
|
633
|
|
|
634 In particular, src/extents.c and src/faces.c might cause the DEC C
|
|
|
635 compiler to abort. When this happens: cd src, compile the files by
|
|
|
636 hand, cd .., and redo the "make" command. When recompiling the files by
|
|
|
637 hand, use the old C compiler for the following versions of Digital UNIX:
|
|
|
638 - V3.n: Remove "-migrate" from the compile command.
|
|
|
639 - V4.n: Add "-oldc" to the compile command.
|
|
|
640
|
|
197
|
641 A related compiler bug has been fixed by the DEC compiler team. The
|
|
|
642 new versions of the compiler should run fine.
|
|
126
|
643
|
|
373
|
644 *** Under some versions of OSF XEmacs runs fine if built without
|
|
|
645 optimization but will crash randomly if built with optimization.
|
|
|
646
|
|
|
647 Using 'cc -g' is not sufficient to eliminate all optimization. Try
|
|
|
648 'cc -g -O0' instead.
|
|
|
649
|
|
|
650 *** Compilation errors on VMS.
|
|
|
651
|
|
|
652 Sorry, XEmacs does not work under VMS. You might consider working on
|
|
|
653 the port if you really want to have XEmacs work under VMS.
|
|
|
654
|
|
|
655 ** HP-UX
|
|
|
656 *** On HPUX, the HP C compiler might have a problem compiling some files
|
|
278
|
657 with optimization.
|
|
124
|
658
|
|
|
659 Richard Cognot <cognot@ensg.u-nancy.fr> writes:
|
|
|
660
|
|
|
661 Had to drop once again to level 2 optimization, at least to
|
|
|
662 compile lstream.c. Otherwise, I get a "variable is void: \if"
|
|
|
663 problem while dumping (this is a problem I already reported
|
|
|
664 with vanilla hpux 10.01 and 9.07, which went away after
|
|
|
665 applying patches for the C compiler). Trouble is I still
|
|
|
666 haven't found the same patch for hpux 10.10, and I don't
|
|
|
667 remember the patch numbers. I think potential XEmacs builders
|
|
|
668 on HP should be warned about this.
|
|
|
669
|
|
373
|
670 *** I don't have `xmkmf' and `imake' on my HP.
|
|
124
|
671
|
|
304
|
672 You can get these standard X tools by anonymous FTP to
|
|
|
673 hpcvaaz.cv.hp.com. Essentially all X programs need these.
|
|
124
|
674
|
|
373
|
675 *** On HP-UX, problems with make
|
|
278
|
676
|
|
442
|
677 Marcus Thiessel <marcus@xemacs.org>
|
|
278
|
678
|
|
304
|
679 Some releases of XEmacs (e.g. 20.4) require GNU make to build
|
|
|
680 successfully. You don't need GNU make when building 21.x.
|
|
278
|
681
|
|
373
|
682 *** On HP-UX 9.05 XEmacs won't compile or coredump during the build.
|
|
278
|
683
|
|
442
|
684 Marcus Thiessel <marcus@xemacs.org>
|
|
278
|
685
|
|
|
686 This might be a sed problem. For your own safety make sure to use
|
|
|
687 GNU sed while dumping XEmacs.
|
|
|
688
|
|
442
|
689
|
|
373
|
690 ** SCO OpenServer
|
|
|
691 *** Native cc on SCO OpenServer 5 is now OK. Icc may still throw you
|
|
197
|
692 a curve. Here is what Robert Lipe <robertl@arnet.com> says:
|
|
124
|
693
|
|
454
|
694 Unlike XEmacs 19.13, building with the native cc on SCO OpenServer 5
|
|
124
|
695 now produces a functional binary. I will typically build this
|
|
|
696 configuration for COFF with:
|
|
|
697
|
|
197
|
698 /path_to_xemacs_source/configure --with-gcc=no \
|
|
2648
|
699 --with-site-includes=/usr/local/include \
|
|
|
700 --with-site-libraries=/usr/local/lib \
|
|
|
701 --with-xpm --with-xface --enable-sound=nas
|
|
124
|
702
|
|
454
|
703 This version now supports ELF builds. I highly recommend this to
|
|
|
704 reduce the in-core footprint of XEmacs. This is now how I compile
|
|
124
|
705 all my test releases. Build it like this:
|
|
|
706
|
|
|
707 /path_to_XEmacs_source/configure --with-gcc=no \
|
|
2648
|
708 --with-site-includes=/usr/local/include
|
|
|
709 --with-site-libraries=/usr/local/lib \
|
|
|
710 --with-xpm --with-xface --enable-sound=nas --with-dynamic
|
|
124
|
711
|
|
454
|
712 The compiler known as icc [ supplied with the OpenServer 5 Development
|
|
124
|
713 System ] generates a working binary, but it takes forever to generate
|
|
|
714 XEmacs. ICC also whines more about the code than /bin/cc does. I do
|
|
|
715 believe all its whining is legitimate, however. Note that you do
|
|
|
716 have to 'cd src ; make LD=icc' to avoid linker errors.
|
|
|
717
|
|
|
718 The way I handle the build procedure is:
|
|
|
719
|
|
|
720 /path_to_XEmacs_source/configure --with-gcc=no \
|
|
2648
|
721 --with-site-includes=/usr/local/include \
|
|
|
722 --with-site-libraries=/usr/local/lib \
|
|
|
723 --with-xpm --with-xface --enable-sound=nas --with-dynamic \
|
|
|
724 --with-compiler="icc"
|
|
124
|
725
|
|
454
|
726 NOTE I have the xpm, xface, and audio libraries and includes in
|
|
124
|
727 /usr/local/lib, /usr/local/include. If you don't have these,
|
|
|
728 don't include the "--with-*" arguments in any of my examples.
|
|
|
729
|
|
454
|
730 In previous versions of XEmacs, you had to override the defaults while
|
|
124
|
731 compiling font-lock.o and extents.o when building with icc. This seems
|
|
|
732 to no longer be true, but I'm including this old information in case it
|
|
|
733 resurfaces. The process I used was:
|
|
|
734
|
|
454
|
735 make -k
|
|
|
736 [ procure pizza, beer, repeat ]
|
|
124
|
737 cd src
|
|
|
738 make CC="icc -W0,-mP1COPT_max_tree_size=3000" font-lock.o extents.o
|
|
|
739 make LD=icc
|
|
|
740
|
|
454
|
741 If you want sound support, get the tls566 supplement from
|
|
|
742 ftp.sco.com:/TLS or any of its mirrors. It works just groovy
|
|
124
|
743 with XEmacs.
|
|
|
744
|
|
|
745 The M-x manual-entry is known not to work. If you know Lisp and would
|
|
|
746 like help in making it work, e-mail me at <robertl@dgii.com>.
|
|
|
747 (UNCHECKED for 19.15 -- it might work).
|
|
|
748
|
|
454
|
749 In earlier releases, gnuserv/gnuclient/gnudoit would open a frame
|
|
124
|
750 just fine, but the client would lock up and the server would
|
|
454
|
751 terminate when you used C-x # to close the frame. This is now
|
|
124
|
752 fixed in XEmacs.
|
|
|
753
|
|
|
754 In etc/ there are two files of note. emacskeys.sco and emacsstrs.sco.
|
|
|
755 The comments at the top of emacskeys.sco describe its function, and
|
|
|
756 the emacstrs.sco is a suitable candidate for /usr/lib/keyboard/strings
|
|
|
757 to take advantage of the keyboard map in emacskeys.sco.
|
|
|
758
|
|
373
|
759 Note: Much of the above entry is probably not valid for XEmacs 21.0
|
|
207
|
760 and later.
|
|
197
|
761
|
|
1332
|
762 ** Windows
|
|
|
763
|
|
1441
|
764 *** XEmacs complains "No such file or directory, diff"
|
|
|
765
|
|
|
766 or "ispell" or other commands that seem related to whatever you just
|
|
|
767 tried to do.
|
|
|
768
|
|
|
769 There are a large number of common (in the sense that "everyone has
|
|
|
770 these, really") Unix utilities that are not provided with XEmacs. The
|
|
|
771 GNU Project's implementations are available for Windows in the the
|
|
|
772 Cygwin distribution (http://www.cygwin.com/), which also provides a
|
|
|
773 complete Unix emulation environment (and thus makes ports of Unix
|
|
|
774 utilities nearly trivial). Another implementation is that from MinGW
|
|
|
775 (http://www.mingw.org/msys.shtml).
|
|
|
776
|
|
1332
|
777 *** Weird crashes in pdump load or shortly after pdump load.
|
|
|
778
|
|
|
779 This can happen with incremental linking. Check if you have set
|
|
|
780 SUPPORT_EDIT_AND_CONTINUE to non-zero in config.inc, which must allow
|
|
|
781 incremental linking to be enabled (otherwise it's disabled). Either turn
|
|
|
782 this off, execute `nmake -f xemacs.mak clean', or manually remove
|
|
|
783 `temacs.exe' and `xemacs.exe'.
|
|
|
784
|
|
392
|
785 ** Cygwin
|
|
524
|
786
|
|
1318
|
787 See also Intel Architecture General, above.
|
|
|
788
|
|
|
789 *** Signal 11 when building or running a dumped XEmacs.
|
|
|
790
|
|
|
791 This appears to happen when using the traditional dumping mechanism and
|
|
|
792 the system malloc. Andy Piper writes:
|
|
|
793
|
|
1332
|
794 Traditional dumping on Cygwin relies on using gmalloc (there are specific
|
|
1318
|
795 hacks in our version of gmalloc to support this), I suspect using sysmalloc
|
|
|
796 is the problem.
|
|
|
797
|
|
|
798 Try configuring with pdump or without system malloc.
|
|
|
799
|
|
524
|
800 *** Syntax errors running configure scripts, make failing with exit code 127
|
|
|
801 in inexplicable situations, etc.
|
|
392
|
802
|
|
1332
|
803 [[ This may be because you are using the default Cygwin shell, under old
|
|
|
804 versions of Cygwin. The default Cygwin shell (/bin/sh.exe) is ash, which
|
|
|
805 appears to work in most circumstances but has some weird failure modes.
|
|
|
806 You may need to replace the symlink with bash.exe. ]] This doesn't appear
|
|
|
807 to affect Cygwin any longer, and /bin/sh.exe is no longer a symlink in
|
|
|
808 any case.
|
|
392
|
809
|
|
524
|
810 *** Lots of compile errors, esp. on lines containing macro definitions
|
|
|
811 terminated by backslashes.
|
|
392
|
812
|
|
524
|
813 Your partition holding the source files is mounted binary. It needs
|
|
|
814 to be mounted text. (This will not screw up any binary files because
|
|
|
815 the Cygwin utilities specify explicitly whether they want binary or
|
|
|
816 text mode when working with source vs. binary files, which overrides
|
|
|
817 the mount type.) To fix this, you just need to run the appropriate
|
|
|
818 mount command once -- afterwards, the settings are remembered in the
|
|
|
819 registry.
|
|
392
|
820
|
|
524
|
821 *** Errors from make like /c:not found.
|
|
392
|
822
|
|
524
|
823 Make sure you set the environment variable MAKE_MODE to UNIX in your
|
|
|
824 .bashrc, Control Panel (Windows 2000/NT), or AUTOEXEC.BAT (Windows
|
|
|
825 98/95).
|
|
392
|
826
|
|
|
827 *** The info files will not build.
|
|
|
828
|
|
1332
|
829 makeinfo that ships with old versions of Cygwin doesn't work.
|
|
|
830 Upgrade to the latest Cygwin version.
|
|
392
|
831
|
|
524
|
832 *** XEmacs hangs while attempting to rebuild the .elc files.
|
|
392
|
833
|
|
524
|
834 Check to make sure you're not configuring with rel-alloc. The relocating
|
|
|
835 allocator does not currently work under Cygwin due to bugs in Cygwin's
|
|
|
836 mmap().
|
|
392
|
837
|
|
524
|
838 *** Trying to build with X, but X11 not detected.
|
|
|
839
|
|
|
840 This is usually because xmkmf is not in your path or because you are
|
|
1332
|
841 using the default Cygwin shell. (See above.)
|
|
333
|
842
|
|
|
843
|
|
373
|
844 * Problems with running XEmacs
|
|
|
845 ==============================
|
|
|
846 ** General
|
|
1332
|
847
|
|
|
848 *** Changes made to .el files do not take effect.
|
|
|
849
|
|
|
850 You may have forgotten to recompile them into .elc files. Then the
|
|
|
851 old .elc files will be loaded, and your changes will not be seen. To
|
|
|
852 fix this, do `M-x byte-recompile-directory' and specify the directory
|
|
|
853 that contains the Lisp files.
|
|
|
854
|
|
|
855 Note that you will get a warning when loading a .elc file that is
|
|
|
856 older than the corresponding .el file.
|
|
|
857
|
|
|
858 *** VM appears to hang in large folders.
|
|
|
859
|
|
|
860 This is normal (trust us) when upgrading to VM-6.22 from earlier
|
|
|
861 versions. Let VM finish what it is doing and all will be well.
|
|
1042
|
862
|
|
892
|
863 *** Starting with 21.4.x, killing text is absurdly slow.
|
|
|
864
|
|
|
865 See FAQ Q3.10.6. Should be available on the web near
|
|
|
866 http://www.xemacs.org/faq/xemacs-faq.html#SEC160.
|
|
|
867
|
|
835
|
868 *** Whenever I try to retrieve a remote file, I have problems.
|
|
|
869
|
|
|
870 A typical error: FTP Error: USER request failed; 500 AUTH not understood.
|
|
|
871 Thanks to giacomo boffi <giacomo.boffi@polimi.it> on comp.emacs.xemacs:
|
|
|
872
|
|
|
873 tell your ftp client to not attempt AUTH authentication (or do not
|
|
|
874 use FTP servers that don't understand AUTH)
|
|
|
875
|
|
|
876 and notes that you need to add an element (often "-u") to
|
|
|
877 `efs-ftp-program-args'. Use M-x customize-variable, and verify the
|
|
|
878 needed flag with `man ftp' or other local documentation.
|
|
|
879
|
|
464
|
880 *** gnuserv is running, some clients can connect, but others cannot.
|
|
|
881
|
|
|
882 The code in gnuslib.c respects the value of TMPDIR. If the server and
|
|
|
883 the client have different values in their environment, you lose.
|
|
|
884 One program known to set TMPDIR and manifest this problem is exmh.
|
|
|
885 You can defeat the use of TMPDIR by unsetting USE_TMPDIR at the top of
|
|
|
886 gnuserv.h at build time.
|
|
|
887
|
|
1332
|
888 ** General Unix
|
|
124
|
889
|
|
373
|
890 *** You type Control-H (Backspace) expecting to delete characters.
|
|
124
|
891
|
|
|
892 Emacs has traditionally used Control-H for help; unfortunately this
|
|
424
|
893 interferes with its use as Backspace on TTY's. As of XEmacs 21,
|
|
|
894 XEmacs looks at the "erase" setting of TTY structures and maps C-h to
|
|
|
895 backspace when erase is set to C-h. This is sort of a special hack,
|
|
|
896 but it makes it possible for you to use the standard:
|
|
|
897
|
|
|
898 stty erase ^H
|
|
355
|
899
|
|
424
|
900 to get your backspace key to erase characters. The erase setting is
|
|
|
901 recorded in the Lisp variable `tty-erase-char', which you can use to
|
|
|
902 tune the settings in your .emacs.
|
|
124
|
903
|
|
424
|
904 A major drawback of this is that when C-h becomes backspace, it no
|
|
|
905 longer invokes help. In that case, you need to use f1 for help, or
|
|
|
906 bind another key. An example of the latter is the following code,
|
|
|
907 which moves help to Meta-? (ESC ?):
|
|
124
|
908
|
|
424
|
909 (global-set-key "\M-?" 'help-command)
|
|
124
|
910
|
|
1332
|
911 *** At startup I get a warning on stderr about missing charsets:
|
|
|
912
|
|
|
913 Warning: Missing charsets in String to FontSet conversion
|
|
|
914
|
|
|
915 You need to specify appropriate charsets for your locale (usually the
|
|
|
916 value of the LANG environment variable) in .Xresources. See
|
|
|
917 etc/Emacs.ad for the relevant resources (mostly menubar fonts and
|
|
|
918 fontsets). Do not edit this file, it's purely informative.
|
|
|
919
|
|
|
920 If you have no satisfactory fonts for iso-8859-1, XEmacs will crash.
|
|
|
921
|
|
|
922 It looks like XFree86 4.x (the usual server on Linux and *BSD) has
|
|
|
923 some braindamage where .UTF-8 locales will always generate this
|
|
|
924 message, because the XFree86 (font)server doesn't know that UTF-8 will
|
|
|
925 use the ISO10646-1 font registry (or a Cmap or something).
|
|
|
926
|
|
|
927 If you are not using a .UTF-8 locale and see this warning for a
|
|
|
928 character set not listed in the default in Emacs.ad, please let
|
|
|
929 xemacs-beta@xemacs.org know about it, so we can add fonts to the
|
|
|
930 appropriate fontsets and stifle this warning. (Unfortunately it's
|
|
|
931 buried in Xlib, so we can't easily get rid of it otherwise.)
|
|
|
932
|
|
373
|
933 *** Mail agents (VM, Gnus, rmail) cannot get new mail
|
|
197
|
934
|
|
|
935 rmail and VM get new mail from /usr/spool/mail/$USER using a program
|
|
|
936 called `movemail'. This program interlocks with /bin/mail using the
|
|
|
937 protocol defined by /bin/mail.
|
|
|
938
|
|
|
939 There are two different protocols in general use. One of them uses
|
|
|
940 the `flock' system call. The other involves creating a lock file;
|
|
|
941 `movemail' must be able to write in /usr/spool/mail in order to do
|
|
|
942 this. You control which one is used by defining, or not defining, the
|
|
|
943 macro MAIL_USE_FLOCK in config.h or the m- or s- file it includes. IF
|
|
|
944 YOU DON'T USE THE FORM OF INTERLOCKING THAT IS NORMAL ON YOUR SYSTEM,
|
|
|
945 YOU CAN LOSE MAIL!
|
|
|
946
|
|
|
947 If your system uses the lock file protocol, and fascist restrictions
|
|
|
948 prevent ordinary users from writing the lock files in /usr/spool/mail,
|
|
|
949 you may need to make `movemail' setgid to a suitable group such as
|
|
|
950 `mail'. To do this, use the following commands (as root) after doing
|
|
|
951 the make install.
|
|
|
952
|
|
|
953 chgrp mail movemail
|
|
|
954 chmod 2755 movemail
|
|
|
955
|
|
|
956 Installation normally copies movemail from the build directory to an
|
|
|
957 installation directory which is usually under /usr/local/lib. The
|
|
|
958 installed copy of movemail is usually in the directory
|
|
|
959 /usr/local/lib/emacs/VERSION/TARGET. You must change the group and
|
|
|
960 mode of the installed copy; changing the group and mode of the build
|
|
|
961 directory copy is ineffective.
|
|
|
962
|
|
373
|
963 *** Things which should be bold or italic (such as the initial
|
|
197
|
964 copyright notice) are not.
|
|
0
|
965
|
|
197
|
966 The fonts of the "bold" and "italic" faces are generated from the font
|
|
|
967 of the "default" face; in this way, your bold and italic fonts will
|
|
|
968 have the appropriate size and family. However, emacs can only be
|
|
|
969 clever in this way if you have specified the default font using the
|
|
|
970 XLFD (X Logical Font Description) format, which looks like
|
|
0
|
971
|
|
|
972 *-courier-medium-r-*-*-*-120-*-*-*-*-*-*
|
|
|
973
|
|
197
|
974 if you use any of the other, less strict font name formats, some of
|
|
|
975 which look like:
|
|
|
976
|
|
0
|
977 lucidasanstypewriter-12
|
|
|
978 and fixed
|
|
|
979 and 9x13
|
|
|
980
|
|
|
981 then emacs won't be able to guess the names of the "bold" and "italic"
|
|
|
982 versions. All X fonts can be referred to via XLFD-style names, so you
|
|
|
983 should use those forms. See the man pages for X(1), xlsfonts(1), and
|
|
|
984 xfontsel(1).
|
|
|
985
|
|
373
|
986 *** The dumped Emacs crashes when run, trying to write pure data.
|
|
0
|
987
|
|
|
988 Two causes have been seen for such problems.
|
|
|
989
|
|
|
990 1) On a system where getpagesize is not a system call, it is defined
|
|
|
991 as a macro. If the definition (in both unexec.c and malloc.c) is wrong,
|
|
|
992 it can cause problems like this. You might be able to find the correct
|
|
|
993 value in the man page for a.out (5).
|
|
|
994
|
|
|
995 2) Some systems allocate variables declared static among the
|
|
|
996 initialized variables. Emacs makes all initialized variables in most
|
|
|
997 of its files pure after dumping, but the variables declared static and
|
|
|
998 not initialized are not supposed to be pure. On these systems you
|
|
|
999 may need to add "#define static" to the m- or the s- file.
|
|
|
1000
|
|
373
|
1001 *** Reading and writing files is very very slow.
|
|
0
|
1002
|
|
|
1003 Try evaluating the form (setq lock-directory nil) and see if that helps.
|
|
|
1004 There is a problem with file-locking on some systems (possibly related
|
|
454
|
1005 to NFS) that I don't understand. Please send mail to the address
|
|
1332
|
1006 xemacs-beta@xemacs.org if you figure this one out.
|
|
0
|
1007
|
|
373
|
1008 *** When emacs starts up, I get lots of warnings about unknown keysyms.
|
|
124
|
1009
|
|
|
1010 If you are running the prebuilt binaries, the Motif library expects to find
|
|
|
1011 certain thing in the XKeysymDB file. This file is normally in /usr/lib/X11/
|
|
|
1012 or in /usr/openwin/lib/. If you keep yours in a different place, set the
|
|
454
|
1013 environment variable $XKEYSYMDB to point to it before starting emacs. If
|
|
|
1014 you still have the problem after doing that, perhaps your version of X is
|
|
2536
|
1015 too old. There is a copy of the MIT X11R6 XKeysymDB file in the emacs `etc'
|
|
124
|
1016 directory. Try using that one.
|
|
|
1017
|
|
373
|
1018 *** My X resources used to work, and now some of them are being ignored.
|
|
0
|
1019
|
|
124
|
1020 Check the resources in .../etc/Emacs.ad (which is the same as the file
|
|
1389
|
1021 sample.Xresources). Perhaps some of the default resources built in to
|
|
124
|
1022 emacs are now overriding your existing resources. Copy and edit the
|
|
|
1023 resources in Emacs.ad as necessary.
|
|
|
1024
|
|
373
|
1025 *** I have focus problems when I use `M-o' to switch to another screen
|
|
197
|
1026 without using the mouse.
|
|
124
|
1027
|
|
197
|
1028 The focus issues with a program like XEmacs, which has multiple
|
|
|
1029 homogeneous top-level windows, are very complicated, and as a result,
|
|
|
1030 most window managers don't implement them correctly.
|
|
0
|
1031
|
|
124
|
1032 The R4/R5 version of twm (and all of its descendants) had buggy focus
|
|
197
|
1033 handling. Sufficiently recent versions of tvtwm have been fixed. In
|
|
|
1034 addition, if you're using twm, make sure you have not specified
|
|
|
1035 "NoTitleFocus" in your .tvtwmrc file. The very nature of this option
|
|
|
1036 makes twm do some illegal focus tricks, even with the patch.
|
|
0
|
1037
|
|
197
|
1038 It is known that olwm and olvwm are buggy, and in different ways. If
|
|
|
1039 you're using click-to-type mode, try using point-to-type, or vice
|
|
|
1040 versa.
|
|
0
|
1041
|
|
197
|
1042 In older versions of NCDwm, one could not even type at XEmacs windows.
|
|
|
1043 This has been fixed in newer versions (2.4.3, and possibly earlier).
|
|
0
|
1044
|
|
197
|
1045 (Many people suggest that XEmacs should warp the mouse when focusing
|
|
|
1046 on another screen in point-to-type mode. This is not ICCCM-compliant
|
|
|
1047 behavior. Implementing such policy is the responsibility of the
|
|
|
1048 window manager itself, it is not legal for a client to do this.)
|
|
0
|
1049
|
|
373
|
1050 *** Emacs spontaneously displays "I-search: " at the bottom of the screen.
|
|
0
|
1051
|
|
|
1052 This means that Control-S/Control-Q (XON/XOFF) "flow control" is being
|
|
|
1053 used. C-s/C-q flow control is bad for Emacs editors because it takes
|
|
|
1054 away C-s and C-q as user commands. Since editors do not output long
|
|
|
1055 streams of text without user commands, there is no need for a
|
|
|
1056 user-issuable "stop output" command in an editor; therefore, a
|
|
|
1057 properly designed flow control mechanism would transmit all possible
|
|
|
1058 input characters without interference. Designing such a mechanism is
|
|
|
1059 easy, for a person with at least half a brain.
|
|
|
1060
|
|
|
1061 There are three possible reasons why flow control could be taking place:
|
|
|
1062
|
|
|
1063 1) Terminal has not been told to disable flow control
|
|
|
1064 2) Insufficient padding for the terminal in use
|
|
|
1065 3) Some sort of terminal concentrator or line switch is responsible
|
|
|
1066
|
|
|
1067 First of all, many terminals have a set-up mode which controls whether
|
|
|
1068 they generate XON/XOFF flow control characters. This must be set to
|
|
|
1069 "no XON/XOFF" in order for Emacs to work. Sometimes there is an
|
|
|
1070 escape sequence that the computer can send to turn flow control off
|
|
|
1071 and on. If so, perhaps the termcap `ti' string should turn flow
|
|
|
1072 control off, and the `te' string should turn it on.
|
|
|
1073
|
|
|
1074 Once the terminal has been told "no flow control", you may find it
|
|
|
1075 needs more padding. The amount of padding Emacs sends is controlled
|
|
|
1076 by the termcap entry for the terminal in use, and by the output baud
|
|
|
1077 rate as known by the kernel. The shell command `stty' will print
|
|
|
1078 your output baud rate; `stty' with suitable arguments will set it if
|
|
|
1079 it is wrong. Setting to a higher speed causes increased padding. If
|
|
|
1080 the results are wrong for the correct speed, there is probably a
|
|
|
1081 problem in the termcap entry. You must speak to a local Unix wizard
|
|
|
1082 to fix this. Perhaps you are just using the wrong terminal type.
|
|
|
1083
|
|
|
1084 For terminals that lack a "no flow control" mode, sometimes just
|
|
|
1085 giving lots of padding will prevent actual generation of flow control
|
|
|
1086 codes. You might as well try it.
|
|
|
1087
|
|
|
1088 If you are really unlucky, your terminal is connected to the computer
|
|
|
1089 through a concentrator which sends XON/XOFF flow control to the
|
|
|
1090 computer, or it insists on sending flow control itself no matter how
|
|
|
1091 much padding you give it. Unless you can figure out how to turn flow
|
|
|
1092 control off on this concentrator (again, refer to your local wizard),
|
|
|
1093 you are screwed! You should have the terminal or concentrator
|
|
|
1094 replaced with a properly designed one. In the mean time, some drastic
|
|
|
1095 measures can make Emacs semi-work.
|
|
|
1096
|
|
|
1097 You can make Emacs ignore C-s and C-q and let the operating system
|
|
|
1098 handle them. To do this on a per-session basis, just type M-x
|
|
|
1099 enable-flow-control RET. You will see a message that C-\ and C-^ are
|
|
|
1100 now translated to C-s and C-q. (Use the same command M-x
|
|
|
1101 enable-flow-control to turn *off* this special mode. It toggles flow
|
|
|
1102 control handling.)
|
|
|
1103
|
|
|
1104 If C-\ and C-^ are inconvenient for you (for example, if one of them
|
|
|
1105 is the escape character of your terminal concentrator), you can choose
|
|
|
1106 other characters by setting the variables flow-control-c-s-replacement
|
|
|
1107 and flow-control-c-q-replacement. But choose carefully, since all
|
|
|
1108 other control characters are already used by emacs.
|
|
|
1109
|
|
|
1110 IMPORTANT: if you type C-s by accident while flow control is enabled,
|
|
|
1111 Emacs output will freeze, and you will have to remember to type C-q in
|
|
|
1112 order to continue.
|
|
|
1113
|
|
|
1114 If you work in an environment where a majority of terminals of a
|
|
|
1115 certain type are flow control hobbled, you can use the function
|
|
|
1116 `enable-flow-control-on' to turn on this flow control avoidance scheme
|
|
|
1117 automatically. Here is an example:
|
|
|
1118
|
|
|
1119 (enable-flow-control-on "vt200" "vt300" "vt101" "vt131")
|
|
|
1120
|
|
|
1121 If this isn't quite correct (e.g. you have a mixture of flow-control hobbled
|
|
|
1122 and good vt200 terminals), you can still run enable-flow-control
|
|
|
1123 manually.
|
|
|
1124
|
|
|
1125 I have no intention of ever redesigning the Emacs command set for the
|
|
|
1126 assumption that terminals use C-s/C-q flow control. XON/XOFF flow
|
|
|
1127 control technique is a bad design, and terminals that need it are bad
|
|
|
1128 merchandise and should not be purchased. Now that X is becoming
|
|
|
1129 widespread, XON/XOFF seems to be on the way out. If you can get some
|
|
|
1130 use out of GNU Emacs on inferior terminals, more power to you, but I
|
|
|
1131 will not make Emacs worse for properly designed systems for the sake
|
|
|
1132 of inferior systems.
|
|
|
1133
|
|
373
|
1134 *** Control-S and Control-Q commands are ignored completely.
|
|
0
|
1135
|
|
|
1136 For some reason, your system is using brain-damaged C-s/C-q flow
|
|
|
1137 control despite Emacs's attempts to turn it off. Perhaps your
|
|
|
1138 terminal is connected to the computer through a concentrator
|
|
|
1139 that wants to use flow control.
|
|
|
1140
|
|
|
1141 You should first try to tell the concentrator not to use flow control.
|
|
|
1142 If you succeed in this, try making the terminal work without
|
|
|
1143 flow control, as described in the preceding section.
|
|
|
1144
|
|
|
1145 If that line of approach is not successful, map some other characters
|
|
|
1146 into C-s and C-q using keyboard-translate-table. The example above
|
|
|
1147 shows how to do this with C-^ and C-\.
|
|
|
1148
|
|
373
|
1149 *** Control-S and Control-Q commands are ignored completely on a net
|
|
197
|
1150 connection.
|
|
0
|
1151
|
|
|
1152 Some versions of rlogin (and possibly telnet) do not pass flow
|
|
|
1153 control characters to the remote system to which they connect.
|
|
|
1154 On such systems, emacs on the remote system cannot disable flow
|
|
|
1155 control on the local system.
|
|
|
1156
|
|
|
1157 One way to cure this is to disable flow control on the local host
|
|
|
1158 (the one running rlogin, not the one running rlogind) using the
|
|
|
1159 stty command, before starting the rlogin process. On many systems,
|
|
120
|
1160 `stty start u stop u' will do this.
|
|
0
|
1161
|
|
|
1162 Some versions of tcsh will prevent even this from working. One way
|
|
|
1163 around this is to start another shell before starting rlogin, and
|
|
|
1164 issue the stty command to disable flow control from that shell.
|
|
|
1165
|
|
|
1166 If none of these methods work, the best solution is to type
|
|
120
|
1167 `M-x enable-flow-control' at the beginning of your emacs session, or
|
|
0
|
1168 if you expect the problem to continue, add a line such as the
|
|
|
1169 following to your .emacs (on the host running rlogind):
|
|
|
1170
|
|
|
1171 (enable-flow-control-on "vt200" "vt300" "vt101" "vt131")
|
|
|
1172
|
|
|
1173 See the entry about spontaneous display of I-search (above) for more
|
|
|
1174 info.
|
|
|
1175
|
|
373
|
1176 *** TTY redisplay is slow.
|
|
197
|
1177
|
|
|
1178 XEmacs has fairly new TTY redisplay support (beginning from 19.12),
|
|
|
1179 which doesn't include some basic TTY optimizations -- like using
|
|
|
1180 scrolling regions to move around blocks of text. This is why
|
|
454
|
1181 redisplay on the traditional terminals, or over slow lines can be very
|
|
197
|
1182 slow.
|
|
|
1183
|
|
|
1184 If you are interested in fixing this, please let us know at
|
|
1332
|
1185 <xemacs-beta@xemacs.org>.
|
|
197
|
1186
|
|
373
|
1187 *** Screen is updated wrong, but only on one kind of terminal.
|
|
0
|
1188
|
|
120
|
1189 This could mean that the termcap entry you are using for that terminal
|
|
|
1190 is wrong, or it could mean that Emacs has a bug handing the
|
|
|
1191 combination of features specified for that terminal.
|
|
0
|
1192
|
|
|
1193 The first step in tracking this down is to record what characters
|
|
|
1194 Emacs is sending to the terminal. Execute the Lisp expression
|
|
120
|
1195 (open-termscript "./emacs-script") to make Emacs write all terminal
|
|
|
1196 output into the file ~/emacs-script as well; then do what makes the
|
|
|
1197 screen update wrong, and look at the file and decode the characters
|
|
|
1198 using the manual for the terminal. There are several possibilities:
|
|
0
|
1199
|
|
|
1200 1) The characters sent are correct, according to the terminal manual.
|
|
|
1201
|
|
|
1202 In this case, there is no obvious bug in Emacs, and most likely you
|
|
|
1203 need more padding, or possibly the terminal manual is wrong.
|
|
|
1204
|
|
120
|
1205 2) The characters sent are incorrect, due to an obscure aspect of the
|
|
|
1206 terminal behavior not described in an obvious way by termcap.
|
|
0
|
1207
|
|
120
|
1208 This case is hard. It will be necessary to think of a way for Emacs
|
|
|
1209 to distinguish between terminals with this kind of behavior and other
|
|
|
1210 terminals that behave subtly differently but are classified the same
|
|
|
1211 by termcap; or else find an algorithm for Emacs to use that avoids the
|
|
|
1212 difference. Such changes must be tested on many kinds of terminals.
|
|
0
|
1213
|
|
|
1214 3) The termcap entry is wrong.
|
|
|
1215
|
|
120
|
1216 See the file etc/TERMS for information on changes that are known to be
|
|
|
1217 needed in commonly used termcap entries for certain terminals.
|
|
0
|
1218
|
|
120
|
1219 4) The characters sent are incorrect, and clearly cannot be right for
|
|
|
1220 any terminal with the termcap entry you were using.
|
|
0
|
1221
|
|
120
|
1222 This is unambiguously an Emacs bug, and can probably be fixed in
|
|
197
|
1223 termcap.c, terminfo.c, tparam.c, cm.c, redisplay-tty.c,
|
|
|
1224 redisplay-output.c, or redisplay.c.
|
|
0
|
1225
|
|
373
|
1226 *** My buffers are full of \000 characters or otherwise corrupt.
|
|
|
1227
|
|
|
1228 Some compilers have trouble with gmalloc.c and ralloc.c; try recompiling
|
|
|
1229 without optimization. If that doesn't work, try recompiling with
|
|
|
1230 SYSTEM_MALLOC defined, and/or with REL_ALLOC undefined.
|
|
|
1231
|
|
1389
|
1232 *** A position you specified in .Xresources is ignored, using twm.
|
|
373
|
1233
|
|
|
1234 twm normally ignores "program-specified" positions.
|
|
|
1235 You can tell it to obey them with this command in your `.twmrc' file:
|
|
|
1236
|
|
|
1237 UsePPosition "on" #allow clents to request a position
|
|
|
1238
|
|
|
1239 *** With M-x enable-flow-control, you need to type C-\ twice to do
|
|
|
1240 incremental search--a single C-\ gets no response.
|
|
|
1241
|
|
|
1242 This has been traced to communicating with your machine via kermit,
|
|
|
1243 with C-\ as the kermit escape character. One solution is to use
|
|
|
1244 another escape character in kermit. One user did
|
|
|
1245
|
|
|
1246 set escape-character 17
|
|
|
1247
|
|
|
1248 in his .kermrc file, to make C-q the kermit escape character.
|
|
|
1249
|
|
|
1250 *** The Motif version of Emacs paints the screen a solid color.
|
|
|
1251
|
|
|
1252 This has been observed to result from the following X resource:
|
|
|
1253
|
|
|
1254 Emacs*default.attributeFont: -*-courier-medium-r-*-*-*-140-*-*-*-*-iso8859-*
|
|
|
1255
|
|
|
1256 That the resource has this effect indicates a bug in something, but we
|
|
|
1257 do not yet know what. If it is an Emacs bug, we hope someone can
|
|
|
1258 explain what the bug is so we can fix it. In the mean time, removing
|
|
|
1259 the resource prevents the problem.
|
|
|
1260
|
|
|
1261 *** After running emacs once, subsequent invocations crash.
|
|
|
1262
|
|
|
1263 Some versions of SVR4 have a serious bug in the implementation of the
|
|
|
1264 mmap () system call in the kernel; this causes emacs to run correctly
|
|
|
1265 the first time, and then crash when run a second time.
|
|
|
1266
|
|
|
1267 Contact your vendor and ask for the mmap bug fix; in the mean time,
|
|
|
1268 you may be able to work around the problem by adding a line to your
|
|
|
1269 operating system description file (whose name is reported by the
|
|
|
1270 configure script) that reads:
|
|
|
1271 #define SYSTEM_MALLOC
|
|
|
1272 This makes Emacs use memory less efficiently, but seems to work around
|
|
|
1273 the kernel bug.
|
|
|
1274
|
|
|
1275 *** Inability to send an Alt-modified key, when Emacs is communicating
|
|
|
1276 directly with an X server.
|
|
|
1277
|
|
|
1278 If you have tried to bind an Alt-modified key as a command, and it
|
|
|
1279 does not work to type the command, the first thing you should check is
|
|
|
1280 whether the key is getting through to Emacs. To do this, type C-h c
|
|
|
1281 followed by the Alt-modified key. C-h c should say what kind of event
|
|
|
1282 it read. If it says it read an Alt-modified key, then make sure you
|
|
|
1283 have made the key binding correctly.
|
|
|
1284
|
|
|
1285 If C-h c reports an event that doesn't have the Alt modifier, it may
|
|
|
1286 be because your X server has no key for the Alt modifier. The X
|
|
|
1287 server that comes from MIT does not set up the Alt modifier by
|
|
|
1288 default.
|
|
|
1289
|
|
|
1290 If your keyboard has keys named Alt, you can enable them as follows:
|
|
|
1291
|
|
|
1292 xmodmap -e 'add mod2 = Alt_L'
|
|
|
1293 xmodmap -e 'add mod2 = Alt_R'
|
|
|
1294
|
|
|
1295 If the keyboard has just one key named Alt, then only one of those
|
|
|
1296 commands is needed. The modifier `mod2' is a reasonable choice if you
|
|
|
1297 are using an unmodified MIT version of X. Otherwise, choose any
|
|
|
1298 modifier bit not otherwise used.
|
|
|
1299
|
|
|
1300 If your keyboard does not have keys named Alt, you can use some other
|
|
|
1301 keys. Use the keysym command in xmodmap to turn a function key (or
|
|
|
1302 some other 'spare' key) into Alt_L or into Alt_R, and then use the
|
|
|
1303 commands show above to make them modifier keys.
|
|
|
1304
|
|
|
1305 Note that if you have Alt keys but no Meta keys, Emacs translates Alt
|
|
|
1306 into Meta. This is because of the great importance of Meta in Emacs.
|
|
|
1307
|
|
|
1308 *** In Shell mode, you get a ^M at the end of every line.
|
|
|
1309
|
|
|
1310 This happens to people who use tcsh, because it is trying to be too
|
|
|
1311 smart. It sees that the Shell uses terminal type `unknown' and turns
|
|
|
1312 on the flag to output ^M at the end of each line. You can fix the
|
|
|
1313 problem by adding this to your .cshrc file:
|
|
|
1314
|
|
|
1315 if ($?EMACS) then
|
|
|
1316 if ($EMACS == "t") then
|
|
454
|
1317 unset edit
|
|
373
|
1318 stty -icrnl -onlcr -echo susp ^Z
|
|
|
1319 endif
|
|
|
1320 endif
|
|
|
1321
|
|
|
1322 *** An error message such as `X protocol error: BadMatch (invalid
|
|
|
1323 parameter attributes) on protocol request 93'.
|
|
|
1324
|
|
|
1325 This comes from having an invalid X resource, such as
|
|
|
1326 emacs*Cursor: black
|
|
|
1327 (which is invalid because it specifies a color name for something
|
|
|
1328 that isn't a color.)
|
|
|
1329
|
|
|
1330 The fix is to correct your X resources.
|
|
|
1331
|
|
|
1332 *** Once you pull down a menu from the menubar, it won't go away.
|
|
|
1333
|
|
|
1334 It has been claimed that this is caused by a bug in certain very old
|
|
|
1335 (1990?) versions of the twm window manager. It doesn't happen with
|
|
|
1336 recent vintages, or with other window managers.
|
|
|
1337
|
|
|
1338 *** Emacs ignores the "help" key when running OLWM.
|
|
|
1339
|
|
|
1340 OLWM grabs the help key, and retransmits it to the appropriate client
|
|
|
1341 using XSendEvent. Allowing emacs to react to synthetic events is a
|
|
|
1342 security hole, so this is turned off by default. You can enable it by
|
|
|
1343 setting the variable x-allow-sendevents to t. You can also cause fix
|
|
|
1344 this by telling OLWM to not grab the help key, with the null binding
|
|
|
1345 "OpenWindows.KeyboardCommand.Help:".
|
|
|
1346
|
|
|
1347 *** Programs running under terminal emulator do not recognize `emacs'
|
|
|
1348 terminal type.
|
|
|
1349
|
|
|
1350 The cause of this is a shell startup file that sets the TERMCAP
|
|
|
1351 environment variable. The terminal emulator uses that variable to
|
|
|
1352 provide the information on the special terminal type that Emacs
|
|
|
1353 emulates.
|
|
|
1354
|
|
|
1355 Rewrite your shell startup file so that it does not change TERMCAP
|
|
|
1356 in such a case. You could use the following conditional which sets
|
|
|
1357 it only if it is undefined.
|
|
|
1358
|
|
|
1359 if ( ! ${?TERMCAP} ) setenv TERMCAP ~/my-termcap-file
|
|
|
1360
|
|
|
1361 Or you could set TERMCAP only when you set TERM--which should not
|
|
|
1362 happen in a non-login shell.
|
|
|
1363
|
|
442
|
1364 *** The popup menu appears at the bottom/right of my screen.
|
|
373
|
1365
|
|
1389
|
1366 You probably have something like the following in your ~/.Xresources
|
|
373
|
1367
|
|
|
1368 Emacs.geometry: 81x56--9--1
|
|
|
1369
|
|
|
1370 Use the following instead
|
|
|
1371
|
|
|
1372 Emacs*EmacsFrame.geometry: 81x56--9--1
|
|
|
1373
|
|
1222
|
1374 *** When I try to use the PostgreSQL functions, I get a message about
|
|
|
1375 undefined symbols.
|
|
|
1376
|
|
|
1377 The only known case in which this happens is if you are using gcc, you
|
|
2648
|
1378 configured with --enable-error-checking=all and --enable-modules, and
|
|
|
1379 you compiled with no optimization. If you encounter this problem in any
|
|
1222
|
1380 other situation, please inform xemacs-beta@xemacs.org.
|
|
|
1381
|
|
|
1382 This problem stems from a gcc bug. With no optimization, functions
|
|
|
1383 declared `extern inline' sometimes are not completely compiled away. An
|
|
|
1384 undefined symbol with the function's name is put into the resulting
|
|
|
1385 object file. In this case, when the postgresql module is loaded, the
|
|
|
1386 linker is unable to resolve that symbol, so the module load fails. The
|
|
|
1387 workaround is to recompile the module with optimization turned on. Any
|
|
|
1388 optimization level, including -Os, appears to work.
|
|
|
1389
|
|
1332
|
1390 *** C-z just refreshes the screen instead of suspending Emacs.
|
|
|
1391
|
|
|
1392 You are probably using a shell that doesn't support job control, even
|
|
|
1393 though the system itself is capable of it. Try using a different
|
|
|
1394 shell.
|
|
373
|
1395
|
|
1036
|
1396 ** MacOS/X, Darwin
|
|
|
1397 *** XEmacs crashes on MacOS within font-lock, or when dealing
|
|
|
1398 with large compilation buffers, or in other regex applications.
|
|
|
1399
|
|
3074
|
1400 The default stack size under MacOS/X prior to 10.3 (Panther) is rather
|
|
|
1401 small (512k as opposed to Solaris 8M), hosing the regexp code, which
|
|
|
1402 uses alloca() extensively, overflowing the stack when complex regexps
|
|
|
1403 are used. Workarounds:
|
|
1036
|
1404
|
|
|
1405 1) Increase your stack size, using `ulimit -s 8192' or a (t)csh
|
|
|
1406 equivalent;
|
|
|
1407
|
|
|
1408 2) Recompile regex.c with REGEX_MALLOC defined.
|
|
|
1409
|
|
373
|
1410 ** AIX
|
|
|
1411 *** Your Delete key sends a Backspace to the terminal, using an AIXterm.
|
|
0
|
1412
|
|
1389
|
1413 The solution is to include in your .Xresources the lines:
|
|
0
|
1414
|
|
|
1415 *aixterm.Translations: #override <Key>BackSpace: string(0x7f)
|
|
|
1416 aixterm*ttyModes: erase ^?
|
|
|
1417
|
|
|
1418 This makes your Backspace key send DEL (ASCII 127).
|
|
|
1419
|
|
373
|
1420 *** On AIX 4, some programs fail when run in a Shell buffer
|
|
|
1421 with an error message like No terminfo entry for "unknown".
|
|
124
|
1422
|
|
373
|
1423 On AIX, many terminal type definitions are not installed by default.
|
|
|
1424 `unknown' is one of them. Install the "Special Generic Terminal
|
|
|
1425 Definitions" to make them defined.
|
|
124
|
1426
|
|
373
|
1427 *** On AIX, you get this message when running Emacs:
|
|
0
|
1428
|
|
373
|
1429 Could not load program emacs
|
|
|
1430 Symbol smtcheckinit in csh is undefined
|
|
|
1431 Error was: Exec format error
|
|
124
|
1432
|
|
373
|
1433 or this one:
|
|
0
|
1434
|
|
373
|
1435 Could not load program .emacs
|
|
|
1436 Symbol _system_con in csh is undefined
|
|
|
1437 Symbol _fp_trapsta in csh is undefined
|
|
|
1438 Error was: Exec format error
|
|
124
|
1439
|
|
373
|
1440 These can happen when you try to run on AIX 3.2.5 a program that was
|
|
|
1441 compiled with 3.2.4. The fix is to recompile.
|
|
124
|
1442
|
|
373
|
1443 *** Trouble using ptys on AIX.
|
|
|
1444
|
|
|
1445 People often install the pty devices on AIX incorrectly.
|
|
|
1446 Use `smit pty' to reinstall them properly.
|
|
|
1447
|
|
0
|
1448
|
|
373
|
1449 ** SunOS/Solaris
|
|
|
1450 *** The Emacs window disappears when you type M-q.
|
|
197
|
1451
|
|
373
|
1452 Some versions of the Open Look window manager interpret M-q as a quit
|
|
|
1453 command for whatever window you are typing at. If you want to use
|
|
|
1454 Emacs with that window manager, you should try to configure the window
|
|
|
1455 manager to use some other command. You can disable the
|
|
|
1456 shortcut keys entirely by adding this line to ~/.OWdefaults:
|
|
0
|
1457
|
|
373
|
1458 OpenWindows.WindowMenuAccelerators: False
|
|
|
1459
|
|
|
1460 *** When Emacs tries to ring the bell, you get an error like
|
|
124
|
1461
|
|
|
1462 audio: sst_open: SETQSIZE" Invalid argument
|
|
|
1463 audio: sst_close: SETREG MMR2, Invalid argument
|
|
|
1464
|
|
197
|
1465 you have probably compiled using an ANSI C compiler, but with non-ANSI
|
|
|
1466 include files. In particular, on Suns, the file
|
|
|
1467 /usr/include/sun/audioio.h uses the _IOW macro to define the constant
|
|
|
1468 AUDIOSETQSIZE. _IOW in turn uses a K&R preprocessor feature that is
|
|
|
1469 now explicitly forbidden in ANSI preprocessors, namely substitution
|
|
|
1470 inside character constants. All ANSI C compilers must provide a
|
|
|
1471 workaround for this problem. Lucid's C compiler is shipped with a new
|
|
|
1472 set of system include files. If you are using GCC, there is a script
|
|
|
1473 called fixincludes that creates new versions of some system include
|
|
|
1474 files that use this obsolete feature.
|
|
124
|
1475
|
|
373
|
1476 *** On Solaris 2.6, XEmacs dumps core when exiting.
|
|
0
|
1477
|
|
373
|
1478 This happens if you're XEmacs is running on the same machine as the X
|
|
|
1479 server, and the optimized memory transport has been turned on by
|
|
|
1480 setting the environment variable XSUNTRANSPORT. The crash occurs
|
|
|
1481 during the call to XCloseDisplay.
|
|
124
|
1482
|
|
373
|
1483 If this describes your situation, you need to undefine the
|
|
|
1484 XSUNTRANSPORT environment variable.
|
|
126
|
1485
|
|
373
|
1486 *** On Solaris, C-x doesn't get through to Emacs when you use the console.
|
|
124
|
1487
|
|
373
|
1488 This is a Solaris feature (at least on Intel x86 cpus). Type C-r
|
|
|
1489 C-r C-t, to toggle whether C-x gets through to Emacs.
|
|
124
|
1490
|
|
373
|
1491 *** On Solaris 2.4, Dired hangs and C-g does not work. Or Emacs hangs
|
|
197
|
1492 forever waiting for termination of a subprocess that is a zombie.
|
|
124
|
1493
|
|
|
1494 casper@fwi.uva.nl says the problem is in X11R6. Rebuild libX11.so
|
|
|
1495 after changing the file xc/config/cf/sunLib.tmpl. Change the lines
|
|
|
1496
|
|
|
1497 #if ThreadedX
|
|
|
1498 #define SharedX11Reqs -lthread
|
|
|
1499 #endif
|
|
|
1500
|
|
|
1501 to:
|
|
|
1502
|
|
|
1503 #if OSMinorVersion < 4
|
|
|
1504 #if ThreadedX
|
|
|
1505 #define SharedX11Reqs -lthread
|
|
|
1506 #endif
|
|
|
1507 #endif
|
|
|
1508
|
|
|
1509 Be sure also to edit x/config/cf/sun.cf so that OSMinorVersion is 4
|
|
|
1510 (as it should be for Solaris 2.4). The file has three definitions for
|
|
|
1511 OSMinorVersion: the first is for x86, the second for SPARC under
|
|
|
1512 Solaris, and the third for SunOS 4. Make sure to update the
|
|
|
1513 definition for your type of machine and system.
|
|
|
1514
|
|
|
1515 Then do `make Everything' in the top directory of X11R6, to rebuild
|
|
|
1516 the makefiles and rebuild X. The X built this way work only on
|
|
|
1517 Solaris 2.4, not on 2.3.
|
|
|
1518
|
|
|
1519 For multithreaded X to work it necessary to install patch
|
|
|
1520 101925-02 to fix problems in header files [2.4]. You need
|
|
|
1521 to reinstall gcc or re-run just-fixinc after installing that
|
|
|
1522 patch.
|
|
0
|
1523
|
|
124
|
1524 However, Frank Rust <frust@iti.cs.tu-bs.de> used a simpler solution:
|
|
|
1525 he changed
|
|
|
1526 #define ThreadedX YES
|
|
|
1527 to
|
|
|
1528 #define ThreadedX NO
|
|
|
1529 in sun.cf and did `make World' to rebuild X11R6. Removing all
|
|
|
1530 `-DXTHREAD*' flags and `-lthread' entries from lib/X11/Makefile and
|
|
|
1531 typing 'make install' in that directory also seemed to work.
|
|
|
1532
|
|
373
|
1533 *** On SunOS 4.1.3, Emacs unpredictably crashes in _yp_dobind_soft.
|
|
124
|
1534
|
|
373
|
1535 This happens if you configure Emacs specifying just `sparc-sun-sunos4'
|
|
|
1536 on a system that is version 4.1.3. You must specify the precise
|
|
|
1537 version number (or let configure figure out the configuration, which
|
|
|
1538 it can do perfectly well for SunOS).
|
|
124
|
1539
|
|
373
|
1540 *** Mail is lost when sent to local aliases.
|
|
0
|
1541
|
|
124
|
1542 Many emacs mail user agents (VM and rmail, for instance) use the
|
|
|
1543 sendmail.el library. This library can arrange for mail to be
|
|
|
1544 delivered by passing messages to the /usr/lib/sendmail (usually)
|
|
|
1545 program . In doing so, it passes the '-t' flag to sendmail, which
|
|
|
1546 means that the name of the recipient of the message is not on the
|
|
|
1547 command line and, therefore, that sendmail must parse the message to
|
|
|
1548 obtain the destination address.
|
|
|
1549
|
|
|
1550 There is a bug in the SunOS4.1.1 and SunOS4.1.3 versions of sendmail.
|
|
|
1551 In short, when given the -t flag, the SunOS sendmail won't recognize
|
|
|
1552 non-local (i.e. NIS) aliases. It has been reported that the Solaris
|
|
|
1553 2.x versions of sendmail do not have this bug. For those using SunOS
|
|
|
1554 4.1, the best fix is to install sendmail V8 or IDA sendmail (which
|
|
|
1555 have other advantages over the regular sendmail as well). At the time
|
|
|
1556 of this writing, these official versions are available:
|
|
|
1557
|
|
|
1558 Sendmail V8 on ftp.cs.berkeley.edu in /ucb/sendmail:
|
|
|
1559 sendmail.8.6.9.base.tar.Z (the base system source & documentation)
|
|
|
1560 sendmail.8.6.9.cf.tar.Z (configuration files)
|
|
|
1561 sendmail.8.6.9.misc.tar.Z (miscellaneous support programs)
|
|
|
1562 sendmail.8.6.9.xdoc.tar.Z (extended documentation, with postscript)
|
|
|
1563
|
|
|
1564 IDA sendmail on vixen.cso.uiuc.edu in /pub:
|
|
|
1565 sendmail-5.67b+IDA-1.5.tar.gz
|
|
|
1566
|
|
373
|
1567 *** Emacs fails to understand most Internet host names, even though
|
|
124
|
1568 the names work properly with other programs on the same system.
|
|
197
|
1569 Emacs won't work with X-windows if the value of DISPLAY is HOSTNAME:0.
|
|
|
1570 Gnus can't make contact with the specified host for nntp.
|
|
0
|
1571
|
|
124
|
1572 This typically happens on Suns and other systems that use shared
|
|
|
1573 libraries. The cause is that the site has installed a version of the
|
|
|
1574 shared library which uses a name server--but has not installed a
|
|
|
1575 similar version of the unshared library which Emacs uses.
|
|
0
|
1576
|
|
124
|
1577 The result is that most programs, using the shared library, work with
|
|
|
1578 the nameserver, but Emacs does not.
|
|
|
1579
|
|
|
1580 The fix is to install an unshared library that corresponds to what you
|
|
|
1581 installed in the shared library, and then relink Emacs.
|
|
0
|
1582
|
|
124
|
1583 On SunOS 4.1, simply define HAVE_RES_INIT.
|
|
|
1584
|
|
|
1585 If you have already installed the name resolver in the file libresolv.a,
|
|
|
1586 then you need to compile Emacs to use that library. The easiest way to
|
|
|
1587 do this is to add to config.h a definition of LIBS_SYSTEM, LIBS_MACHINE
|
|
|
1588 or LIB_STANDARD which uses -lresolv. Watch out! If you redefine a macro
|
|
|
1589 that is already in use in your configuration to supply some other libraries,
|
|
|
1590 be careful not to lose the others.
|
|
|
1591
|
|
|
1592 Thus, you could start by adding this to config.h:
|
|
|
1593
|
|
|
1594 #define LIBS_SYSTEM -lresolv
|
|
|
1595
|
|
|
1596 Then if this gives you an error for redefining a macro, and you see that
|
|
|
1597 the s- file defines LIBS_SYSTEM as -lfoo -lbar, you could change config.h
|
|
|
1598 again to say this:
|
|
|
1599
|
|
|
1600 #define LIBS_SYSTEM -lresolv -lfoo -lbar
|
|
|
1601
|
|
373
|
1602 *** With process-connection-type set to t, each line of subprocess
|
|
|
1603 output is terminated with a ^M, making ange-ftp and GNUS not work.
|
|
|
1604
|
|
|
1605 On SunOS systems, this problem has been seen to be a result of an
|
|
|
1606 incomplete installation of gcc 2.2 which allowed some non-ANSI
|
|
|
1607 compatible include files into the compilation. In particular this
|
|
|
1608 affected virtually all ioctl() calls.
|
|
|
1609
|
|
|
1610
|
|
|
1611 ** Linux
|
|
845
|
1612 *** XEmacs crashes on startup, in make-frame.
|
|
|
1613
|
|
|
1614 Typically the Lisp backtrace includes
|
|
|
1615
|
|
|
1616 make-frame(nil #<x-device on ":0.0" 0x2558>)
|
|
|
1617
|
|
2648
|
1618 somewhere near the top. The problem is due to an improvement in GNU ld
|
|
|
1619 that sorts the ELF reloc sections in the executable, giving dramatic
|
|
|
1620 speedups in startup for large executables. It also confuses the
|
|
|
1621 traditional unexec code in XEmacs, leading to the core dump. The
|
|
|
1622 solution is to use the --enable-pdump or --with-ldflags='-z nocombreloc'
|
|
|
1623 options to configure. Recent 21.4 and 12.5 autodetect this in
|
|
|
1624 configure.
|
|
845
|
1625
|
|
|
1626 Red Hat and SuSE (at least) distributed a prerelease version of ld
|
|
|
1627 (versions around 2.11.90.x.y) where autodetection is impossible. The
|
|
|
1628 recommended procedure is to upgrade to binutils >= 2.12 and rerun
|
|
2648
|
1629 configure. Otherwise you must apply the flags by hand. --enable-pdump
|
|
|
1630 is recommended.
|
|
448
|
1631
|
|
|
1632 *** I want XEmacs to use the Alt key, not the XXX key, for Meta commands
|
|
|
1633
|
|
|
1634 For historical reasons, XEmacs looks for a Meta key, then an Alt key.
|
|
|
1635 It binds Meta commands to the X11 modifier bit attached to the first
|
|
|
1636 of these it finds. On PCs, the Windows key is often assigned the Meta
|
|
|
1637 bit, but many desktop environments go to great lengths to get all apps
|
|
|
1638 to use the Alt key, and reserve the Windows key to (sensibly enough)
|
|
|
1639 the window manager.
|
|
|
1640
|
|
|
1641 One correct way to implement this was suggested on comp.emacs.xemacs
|
|
|
1642 (by Kilian Foth and in more detail by Michael Piotrowski): unmap the
|
|
|
1643 Meta modifier using xmodmap or xkb, and then map the Meta/Windows key
|
|
450
|
1644 to the Super or Hyper keysym and an appropriate mod bit. XEmacs will
|
|
|
1645 not find the Meta keysym, and default to using the Alt key for Meta
|
|
|
1646 keybindings. Typically few applications use the (X11) Meta modifier;
|
|
|
1647 it is tedious but not too much so to teach the ones you need to use
|
|
|
1648 Super instead of Meta. There may be further useful hints in the
|
|
|
1649 discussion of keymapping on non-Linux platforms.
|
|
|
1650
|
|
|
1651 *** The color-gcc wrapper
|
|
|
1652
|
|
|
1653 This wrapper colorizes the error messages from gcc. By default XEmacs
|
|
|
1654 does not interpret the escape sequences used to generate colors,
|
|
|
1655 resulting in a cluttered, hard-to-read buffer. You can remove the
|
|
|
1656 wrapper, or defeat the wrapper colorization in Emacs process buffers
|
|
|
1657 by editing the "nocolor" attribute in /etc/colorgccrc:
|
|
|
1658
|
|
|
1659 $ diff -u /etc/colorgccrc.old /etc/colorgccrc
|
|
|
1660 --- /etc/colorgccrc.old Tue Dec 26 02:17:46 2000
|
|
|
1661 +++ /etc/colorgccrc Tue Dec 26 02:15:48 2000
|
|
|
1662 @@ -34,1 +34,1 @@
|
|
|
1663 -nocolor: dumb
|
|
|
1664 +nocolor: dumb emacs
|
|
|
1665
|
|
|
1666 If you want colorization in your Emacs buffers, you may get good
|
|
|
1667 results from the ansi-color.el library:
|
|
|
1668
|
|
|
1669 http://www.geocities.com/kensanata/color-emacs.html#ansicolors
|
|
|
1670
|
|
|
1671 This is written for the mainline GNU Emacs but the author has made
|
|
|
1672 efforts to adapt it to XEmacs. YMMV.
|
|
448
|
1673
|
|
373
|
1674 *** Slow startup on Linux.
|
|
|
1675
|
|
|
1676 People using systems based on the Linux kernel sometimes report that
|
|
448
|
1677 startup takes 10 to 15 seconds longer than `usual'. There are two
|
|
|
1678 problems, one older, one newer.
|
|
|
1679
|
|
|
1680 **** Old problem: IPv4 host lookup
|
|
373
|
1681
|
|
448
|
1682 On older systems, this is because Emacs looks up the host name when it
|
|
|
1683 starts. Normally, this takes negligible time; the extra delay is due
|
|
|
1684 to improper system configuration. (Recent Linux distros usually have
|
|
|
1685 this configuration correct "out of the box".) This problem can occur
|
|
|
1686 for both networked and non-networked machines.
|
|
373
|
1687
|
|
|
1688 Here is how to fix the configuration. It requires being root.
|
|
|
1689
|
|
448
|
1690 ***** Networked Case
|
|
373
|
1691
|
|
|
1692 First, make sure the files `/etc/hosts' and `/etc/host.conf' both
|
|
|
1693 exist. The first line in the `/etc/hosts' file should look like this
|
|
|
1694 (replace HOSTNAME with your host name):
|
|
|
1695
|
|
|
1696 127.0.0.1 localhost HOSTNAME
|
|
|
1697
|
|
|
1698 Also make sure that the `/etc/host.conf' files contains the following
|
|
|
1699 lines:
|
|
|
1700
|
|
454
|
1701 order hosts, bind
|
|
373
|
1702 multi on
|
|
|
1703
|
|
|
1704 Any changes, permanent and temporary, to the host name should be
|
|
|
1705 indicated in the `/etc/hosts' file, since it acts a limited local
|
|
|
1706 database of addresses and names (e.g., some SLIP connections
|
|
|
1707 dynamically allocate ip addresses).
|
|
|
1708
|
|
448
|
1709 ***** Non-Networked Case
|
|
373
|
1710
|
|
|
1711 The solution described in the networked case applies here as well.
|
|
|
1712 However, if you never intend to network your machine, you can use a
|
|
|
1713 simpler solution: create an empty `/etc/host.conf' file. The command
|
|
|
1714 `touch /etc/host.conf' suffices to create the file. The `/etc/hosts'
|
|
|
1715 file is not necessary with this approach.
|
|
|
1716
|
|
448
|
1717 **** New problem: IPv6 CNAME lookup
|
|
|
1718
|
|
|
1719 A newer problem is due to XEmacs changing to use the modern
|
|
|
1720 getaddrinfo() interface from the older gethostbyname() interface. The
|
|
|
1721 solution above is insufficient, because getaddrinfo() by default tries
|
|
|
1722 to get IPv6 information for localhost. This always involves a dns
|
|
|
1723 lookup to get the CNAME, and the strategies above don't work. It then
|
|
724
|
1724 falls back to IPv4 behavior. This is good[tm] according the people at
|
|
|
1725 WIDE who know about IPv6.
|
|
448
|
1726
|
|
|
1727 ***** Robust network case
|
|
|
1728
|
|
|
1729 Configure your network so that there are no nameservers configured
|
|
|
1730 until the network is actually running. getaddrinfo() will not try to
|
|
|
1731 access a nameserver that isn't configured.
|
|
|
1732
|
|
|
1733 ***** Flaky network case
|
|
|
1734
|
|
|
1735 If you have a flaky modem or DSL connection that can be relied on only
|
|
|
1736 to go down whenever you want to bring XEmacs up, you need to force
|
|
|
1737 IPv4 behavior. Explicitly setting DISPLAY=127.0.0.1:0.0 (or whatever
|
|
|
1738 is appropriate) works in most cases.
|
|
|
1739
|
|
|
1740 If you cannot or do not want to do that, you can hard code IPv4
|
|
|
1741 behavior in src/process-unix.c. This is bad[tm], on your own head be
|
|
724
|
1742 it. Use the configure option `--with-ipv6-cname=no'.
|
|
373
|
1743
|
|
845
|
1744 *** Mandrake
|
|
|
1745
|
|
|
1746 The Mandrake Linux distribution is attempting to comprehensively
|
|
|
1747 update the user interface, and make it consistent across
|
|
|
1748 applications. This is very difficult, and will occasionally cause
|
|
|
1749 conflicts with applications like Emacs with their own long-established
|
|
|
1750 interfaces. Known issues specific to Mandrake or especially common:
|
|
|
1751
|
|
|
1752 Some versions of XEmacs (21.1.9 is known) distributed with Mandrake
|
|
|
1753 were patched to make the Meta and Alt keysyms synonymous. These
|
|
|
1754 normally work as expected in the Mandrake environment. However,
|
|
|
1755 custom-built XEmacsen (including all 21.2 betas) will "inexplicably"
|
|
|
1756 not respect the "Alt-invokes-Meta-commands" convention. See "I want
|
|
|
1757 XEmacs to use the Alt key" below.
|
|
|
1758
|
|
|
1759 The color-gcc wrapper (see below) is in common use on the Mandrake
|
|
|
1760 platform.
|
|
|
1761
|
|
|
1762 *** You get crashes in a non-C locale with Linux GNU Libc 2.0.
|
|
|
1763
|
|
|
1764 Internationalization was not the top priority for GNU Libc 2.0.
|
|
|
1765 As of this writing (1998-12-28) you may get crashes while running
|
|
|
1766 XEmacs in a non-C locale. For example, `LC_ALL=en_US xemacs' crashes
|
|
|
1767 while `LC_ALL=C xemacs' runs fine. This happens for example with GNU
|
|
|
1768 libc 2.0.7. Installing libintl.a and libintl.h built from gettext
|
|
|
1769 0.10.35 and re-building XEmacs solves the crashes. Presumably soon
|
|
|
1770 everyone will upgrade to GNU Libc 2.1 and this problem will go away.
|
|
|
1771
|
|
|
1772 *** `C-z', or `M-x suspend-emacs' hangs instead of suspending.
|
|
|
1773
|
|
|
1774 If you build with `gpm' support on Linux, you cannot suspend XEmacs
|
|
|
1775 because gpm installs a buggy SIGTSTP handler. Either compile with
|
|
|
1776 `--with-gpm=no', or don't suspend XEmacs on the Linux console until
|
|
|
1777 this bug is fixed.
|
|
|
1778
|
|
|
1779 *** With certain fonts, when the cursor appears on a character, the
|
|
|
1780 character doesn't appear--you get a solid box instead.
|
|
|
1781
|
|
|
1782 One user on a Linux system reported that this problem went away with
|
|
|
1783 installation of a new X server. The failing server was XFree86 3.1.1.
|
|
|
1784 XFree86 3.1.2 works.
|
|
|
1785
|
|
373
|
1786 ** IRIX
|
|
|
1787 *** On Irix, I don't see the toolbar icons and I'm getting lots of
|
|
|
1788 entries in the warnings buffer.
|
|
|
1789
|
|
|
1790 SGI ships a really old Xpm library in /usr/lib which does not work at
|
|
|
1791 all well with XEmacs. The solution is to install your own copy of the
|
|
2648
|
1792 latest version of Xpm somewhere and then use the --with-site-includes
|
|
|
1793 and --with-site-libraries flags to tell configure where to find it.
|
|
373
|
1794
|
|
|
1795 *** Trouble using ptys on IRIX, or running out of ptys.
|
|
|
1796
|
|
|
1797 The program mkpts (which may be in `/usr/adm' or `/usr/sbin') needs to
|
|
|
1798 be set-UID to root, or non-root programs like Emacs will not be able
|
|
|
1799 to allocate ptys reliably.
|
|
|
1800
|
|
|
1801 *** Beware of the default image & graphics library on Irix
|
|
|
1802
|
|
|
1803 Richard Cognot <cognot@ensg.u-nancy.fr> writes:
|
|
|
1804
|
|
|
1805 You *have* to compile your own jpeg lib. The one delivered with SGI
|
|
|
1806 systems is a C++ lib, which apparently XEmacs cannot cope with.
|
|
|
1807
|
|
|
1808
|
|
|
1809 ** Digital UNIX/OSF/VMS/Ultrix
|
|
|
1810 *** XEmacs crashes on Digital Unix within font-lock, or when dealing
|
|
1036
|
1811 with large compilation buffers, or in other regex applications.
|
|
373
|
1812
|
|
|
1813 The default stack size under Digital Unix is rather small (2M as
|
|
|
1814 opposed to Solaris 8M), hosing the regexp code, which uses alloca()
|
|
|
1815 extensively, overflowing the stack when complex regexps are used.
|
|
|
1816 Workarounds:
|
|
312
|
1817
|
|
373
|
1818 1) Increase your stack size, using `ulimit -s 8192' or a (t)csh
|
|
|
1819 equivalent;
|
|
|
1820
|
|
|
1821 2) Recompile regex.c with REGEX_MALLOC defined.
|
|
|
1822
|
|
|
1823 *** The `Alt' key doesn't behave as `Meta' when running DECwindows.
|
|
|
1824
|
|
|
1825 The default DEC keyboard mapping has the Alt keys set up to generate the
|
|
|
1826 keysym `Multi_key', which has a meaning to xemacs which is distinct from that
|
|
|
1827 of the `Meta_L' and `Meta-R' keysyms. A second problem is that certain keys
|
|
|
1828 have the Mod2 modifier attached to them for no adequately explored reason.
|
|
|
1829 The correct fix is to pass this file to xmodmap upon starting X:
|
|
|
1830
|
|
|
1831 clear mod2
|
|
|
1832 keysym Multi_key = Alt_L
|
|
|
1833 add mod1 = Alt_L
|
|
|
1834 add mod1 = Alt_R
|
|
|
1835
|
|
|
1836 *** The Compose key on a DEC keyboard does not work as Meta key.
|
|
|
1837
|
|
|
1838 This shell command should fix it:
|
|
|
1839
|
|
|
1840 xmodmap -e 'keycode 0xb1 = Meta_L'
|
|
|
1841
|
|
|
1842 *** `expand-file-name' fails to work on any but the machine you dumped
|
|
|
1843 Emacs on.
|
|
|
1844
|
|
|
1845 On Ultrix, if you use any of the functions which look up information
|
|
|
1846 in the passwd database before dumping Emacs (say, by using
|
|
|
1847 expand-file-name in site-init.el), then those functions will not work
|
|
|
1848 in the dumped Emacs on any host but the one Emacs was dumped on.
|
|
|
1849
|
|
|
1850 The solution? Don't use expand-file-name in site-init.el, or in
|
|
|
1851 anything it loads. Yuck - some solution.
|
|
|
1852
|
|
|
1853 I'm not sure why this happens; if you can find out exactly what is
|
|
|
1854 going on, and perhaps find a fix or a workaround, please let us know.
|
|
|
1855 Perhaps the YP functions cache some information, the cache is included
|
|
|
1856 in the dumped Emacs, and is then inaccurate on any other host.
|
|
|
1857
|
|
|
1858
|
|
|
1859 ** HP-UX
|
|
|
1860 *** I get complaints about the mapping of my HP keyboard at startup,
|
|
|
1861 but I haven't changed anything.
|
|
|
1862
|
|
|
1863 The default HP keymap is set up to have Mod1 assigned to two different keys:
|
|
|
1864 Meta_L and Mode_switch (even though there is not actually a Mode_switch key on
|
|
|
1865 the keyboard -- it uses an "imaginary" keycode.) There actually is a reason
|
|
|
1866 for this, but it's not a good one. The correct fix is to execute this command
|
|
|
1867 upon starting X:
|
|
|
1868
|
|
|
1869 xmodmap -e 'remove mod1 = Mode_switch'
|
|
312
|
1870
|
|
373
|
1871 *** On HP-UX, you get "poll: Interrupted system call" message in the
|
|
|
1872 window where XEmacs was launched.
|
|
|
1873
|
|
|
1874 Richard Cognot <cognot@ensg.u-nancy.fr> writes:
|
|
|
1875
|
|
|
1876 I get a very strange problem when linking libc.a dynamically: every
|
|
|
1877 event (mouse, keyboard, expose...) results in a "poll: Interrupted
|
|
|
1878 system call" message in the window where XEmacs was
|
|
|
1879 launched. Forcing a static link of libc.a alone by adding
|
|
|
1880 /usr/lib/libc.a at the end of the link line solves this. Note that
|
|
|
1881 my 9.07 build of 19.14b17 and my (old) build of 19.13 both exhibit
|
|
442
|
1882 the same behavior. I've tried various hpux patches to no avail. If
|
|
373
|
1883 this problem cannot be solved before the release date, binary kits
|
|
|
1884 for HP *must* be linked statically against libc, otherwise this
|
|
|
1885 problem will show up. (This is directed at whoever will volunteer
|
|
|
1886 for this kit, as I won't be available to do it, unless 19.14 gets
|
|
|
1887 delayed until mid-june ;-). I think this problem will be an FAQ soon
|
|
|
1888 after the release otherwise.
|
|
|
1889
|
|
|
1890 Note: The above entry is probably not valid for XEmacs 21.0 and
|
|
|
1891 later.
|
|
|
1892
|
|
|
1893 *** The right Alt key works wrong on German HP keyboards (and perhaps
|
|
|
1894 other non-English HP keyboards too).
|
|
|
1895
|
|
|
1896 This is because HP-UX defines the modifiers wrong in X. Here is a
|
|
|
1897 shell script to fix the problem; be sure that it is run after VUE
|
|
|
1898 configures the X server.
|
|
|
1899
|
|
|
1900 xmodmap 2> /dev/null - << EOF
|
|
|
1901 keysym Alt_L = Meta_L
|
|
|
1902 keysym Alt_R = Meta_R
|
|
|
1903 EOF
|
|
|
1904
|
|
|
1905 xmodmap - << EOF
|
|
|
1906 clear mod1
|
|
|
1907 keysym Mode_switch = NoSymbol
|
|
|
1908 add mod1 = Meta_L
|
|
|
1909 keysym Meta_R = Mode_switch
|
|
|
1910 add mod2 = Mode_switch
|
|
|
1911 EOF
|
|
|
1912
|
|
442
|
1913
|
|
|
1914 *** XEmacs dumps core at startup when native audio is used. Native
|
|
|
1915 audio does not work with recent versions of HP-UX.
|
|
|
1916
|
|
|
1917 Under HP-UX 10.20 and later (e.g., HP-UX 11.XX), with native audio
|
|
|
1918 enabled, the dumped XEmacs binary ("xemacs") core dumps at startup if
|
|
|
1919 recent versions of the libAlib.sl audio shared library is used. Note
|
|
|
1920 that "temacs" will run, but "xemacs" will dump core. This, of course,
|
|
|
1921 causes the XEmacs build to fail. If GNU malloc is enabled, a stack
|
|
|
1922 trace will show XEmacs to have crashed in the "first" call to malloc().
|
|
|
1923
|
|
|
1924 This bug currently exists in all versions of XEmacs, when the undump
|
|
|
1925 mechanism is used. It is not known if using the experimental portable
|
|
|
1926 dumper will allow native audio to work.
|
|
|
1927
|
|
|
1928 **** Cause:
|
|
|
1929
|
|
|
1930 Recent versions of the HP-UX 10.20 (and later) audio shared library (in
|
|
|
1931 /opt/audio/lib), pulls in the libdce shared library, which pulls in a
|
|
|
1932 thread (libcma) library. This prevents the HP-UX undump() routine (in
|
|
|
1933 unexhp9k800.c) from properly working. What's happening is that some
|
|
|
1934 initialization routines are being called in the libcma library, *BEFORE*
|
|
|
1935 main() is called, and these initialization routines are calling
|
|
|
1936 malloc(). Unfortunately, in order for the undumper to work, XEmacs must
|
|
|
1937 adjust (move upwards) the sbrk() value *BEFORE* the first call to
|
|
|
1938 malloc(); if malloc() is called before XEmacs has properly adjusted sbrk
|
|
|
1939 (which is what is happening), dumped memory that is being used by
|
|
|
1940 XEmacs, is improperly re-allocated for use by malloc() and the dumped
|
|
|
1941 memory is corrupted. This causes XEmacs to die an horrible death.
|
|
|
1942
|
|
|
1943 It is believed that versions of the audio library past December 1998
|
|
|
1944 will trigger this problem. Under HP-UX 10.20, you probably have to
|
|
|
1945 install audio library patches to encounter this. It's probable that
|
|
|
1946 recent "fresh, out-of-the-box" HP-UX 11.XX workstations also have this
|
|
|
1947 problem. For HP-UX 10.20, it's believed that audio patch PHSS_17121 (or
|
|
|
1948 a superceeding one, like PHSS_17554, PHSS_17971, PHSS_18777, PHSS_21481,
|
|
|
1949 or PHSS_21662, etc.) will trigger this.
|
|
|
1950
|
|
|
1951 To check if your audio library will cause problems for XEmacs, run
|
|
|
1952 "chatr /opt/audio/lib/libAlib.sl". If "libdce" appears in the displayed
|
|
|
1953 shared library list, XEmacs will probably encounter problems if audio is
|
|
|
1954 enabled.
|
|
|
1955
|
|
|
1956 **** Workaround:
|
|
|
1957
|
|
|
1958 Don't enable native audio. Re-run configure without native audio
|
|
|
1959 support.
|
|
|
1960
|
|
|
1961 If your site supports it, try using NAS (Network Audio Support).
|
|
|
1962
|
|
|
1963 Try using the experimental portable dumper. It may work, or it may
|
|
|
1964 not.
|
|
|
1965
|
|
|
1966
|
|
373
|
1967 *** `Pid xxx killed due to text modification or page I/O error'
|
|
|
1968
|
|
|
1969 On HP-UX, you can get that error when the Emacs executable is on an NFS
|
|
|
1970 file system. HP-UX responds this way if it tries to swap in a page and
|
|
|
1971 does not get a response from the server within a timeout whose default
|
|
|
1972 value is just ten seconds.
|
|
|
1973
|
|
|
1974 If this happens to you, extend the timeout period.
|
|
|
1975
|
|
|
1976 *** Shell mode on HP-UX gives the message, "`tty`: Ambiguous".
|
|
124
|
1977
|
|
|
1978 christos@theory.tn.cornell.edu says:
|
|
|
1979
|
|
|
1980 The problem is that in your .cshrc you have something that tries to
|
|
197
|
1981 execute `tty`. If you are not running the shell on a real tty then tty
|
|
|
1982 will print "not a tty". Csh expects one word in some places, but tty
|
|
|
1983 is giving it back 3.
|
|
124
|
1984
|
|
197
|
1985 The solution is to add a pair of quotes around `tty` to make it a
|
|
|
1986 single word:
|
|
0
|
1987
|
|
454
|
1988 if (`tty` == "/dev/console")
|
|
124
|
1989
|
|
|
1990 should be changed to:
|
|
|
1991
|
|
454
|
1992 if ("`tty`" == "/dev/console")
|
|
124
|
1993
|
|
|
1994 Even better, move things that set up terminal sections out of .cshrc
|
|
|
1995 and into .login.
|
|
0
|
1996
|
|
|
1997
|
|
373
|
1998 ** SCO
|
|
|
1999 *** Regular expressions matching bugs on SCO systems.
|
|
0
|
2000
|
|
373
|
2001 On SCO, there are problems in regexp matching when Emacs is compiled
|
|
|
2002 with the system compiler. The compiler version is "Microsoft C
|
|
|
2003 version 6", SCO 4.2.0h Dev Sys Maintenance Supplement 01/06/93; Quick
|
|
|
2004 C Compiler Version 1.00.46 (Beta). The solution is to compile with
|
|
|
2005 GCC.
|
|
124
|
2006
|
|
88
|
2007
|
|
373
|
2008 ** Windows
|
|
1332
|
2009 *** Conflicts with FSF NTEmacs
|
|
|
2010
|
|
|
2011 Depending on how it is installed, FSF NTEmacs may setup various EMACS*
|
|
|
2012 variables in your environment. The presence of these variables may
|
|
|
2013 cause XEmacs to fail at startup, cause you to see corrupted
|
|
|
2014 doc-strings, or cause other random problems.
|
|
|
2015
|
|
|
2016 You should remove these variables from your environment. These
|
|
|
2017 variables are not required to run FSF NTEmacs if you start it by
|
|
|
2018 running emacs.bat.
|
|
|
2019
|
|
|
2020 *** XEmacs can't find my init file
|
|
|
2021
|
|
|
2022 XEmacs looks for your init in your "home" directory -- either in
|
|
|
2023 `~/.xemacs/init.el' or `~/.emacs'. XEmacs decides that your "home"
|
|
|
2024 directory is, in order of preference:
|
|
|
2025
|
|
|
2026 - The value of the HOME environment variable, if the variable exists.
|
|
|
2027 - The value of the registry entry SOFTWARE\XEmacs\XEmacs\HOME,
|
|
|
2028 if it exists.
|
|
|
2029 - The value of the HOMEDRIVE and HOMEPATH environment variables, if
|
|
|
2030 these variables both exist.
|
|
|
2031 - C:\.
|
|
|
2032
|
|
|
2033 To determine what XEmacs thinks your home directory is, try opening
|
|
|
2034 a file in the `~' directory, and you should see its expansion in the
|
|
|
2035 modeline. If this doesn't work, type ESC : (user-home-directory).
|
|
|
2036
|
|
|
2037 *** XEmacs can't find any packages
|
|
|
2038
|
|
|
2039 XEmacs looks for your packages in subdirectories of a directory which
|
|
|
2040 is set at compile-time (see `config.inc'), and whose default is
|
|
|
2041 `C:\Program Files\XEmacs'. XEmacs also looks in `~/.xemacs', where
|
|
|
2042 `~' refers to your home directory (see previous entry). The variable
|
|
|
2043 `configure-package-path' holds the actual path that was compiled into
|
|
|
2044 your copy of XEmacs.
|
|
|
2045
|
|
|
2046 The compile-time default location can be overridden by the EMACSPACKAGEPATH
|
|
|
2047 environment variable or by the SOFTWARE\XEmacs\XEmacs\EMACSPACKAGEPATH
|
|
|
2048 registry entry. You should check that these variables, if they exist,
|
|
|
2049 point to the actual location of your package tree.
|
|
|
2050
|
|
|
2051 *** XEmacs doesn't die when shutting down Windows 95 or 98
|
|
|
2052
|
|
|
2053 When shutting down Windows 95 or 98 you may see a dialog that says
|
|
|
2054 "xemacs / You must quit this program before you quit Windows".
|
|
|
2055 It is safe to
|
|
|
2056 "Click OK to quit the program and Windows",
|
|
|
2057 but you won't be offered a chance to save any modified XEmacs buffers.
|
|
|
2058
|
|
|
2059 *** Key bindings
|
|
|
2060
|
|
|
2061 The C-z, C-x, C-c, and C-v keystrokes have traditional uses in both
|
|
|
2062 emacs and Windows programs. XEmacs binds these keys to their
|
|
|
2063 traditional emacs uses, and provides Windows 3.x style bindings for
|
|
|
2064 the Cut, Copy and Paste functions.
|
|
|
2065
|
|
|
2066 Function XEmacs binding
|
|
|
2067 -------- --------------
|
|
|
2068 Undo C-_
|
|
|
2069 Cut Sh-Del
|
|
|
2070 Copy C-Insert
|
|
|
2071 Paste Sh-Insert
|
|
|
2072
|
|
|
2073 You can rebind keys to make XEmacs more Windows-compatible; for
|
|
|
2074 example, to bind C-z to undo:
|
|
|
2075
|
|
|
2076 (global-set-key [(control z)] 'undo)
|
|
|
2077
|
|
|
2078 Rebindind C-x and C-c is trickier because by default these are prefix
|
|
|
2079 keys in XEmacs. See the "Key Bindings" node in the XEmacs manual.
|
|
|
2080
|
|
|
2081 *** Behavior of selected regions
|
|
|
2082
|
|
|
2083 Use the pending-del package to enable the standard Windows behavior of
|
|
|
2084 self-inserting deletes region.
|
|
|
2085
|
|
|
2086 *** Limitations on the use of the AltGr key.
|
|
|
2087
|
|
|
2088 In some locale and OS combinations you can't generate M-AltGr-key or
|
|
|
2089 C-M-AltGr-key sequences at all.
|
|
|
2090
|
|
|
2091 To generate C-AltGr-key or C-M-AltGr-key sequences you must use the
|
|
|
2092 right-hand Control key and you must press it *after* AltGr.
|
|
|
2093
|
|
|
2094 These limitations arise from fundamental problems in the way that the
|
|
|
2095 win32 API reports AltGr key events. There isn't anything that XEmacs
|
|
|
2096 can do to work round these problems that it isn't already doing.
|
|
|
2097
|
|
|
2098 You may want to create alternative bindings if any of the standard
|
|
|
2099 XEmacs bindings require you to use some combination of Control or Meta
|
|
|
2100 and AltGr.
|
|
|
2101
|
|
|
2102 *** Limited support for subprocesses under Windows 9x
|
|
|
2103
|
|
|
2104 Attempting to use call-process to run a 16bit program gives a
|
|
|
2105 "Spawning child process: Exec format error". For example shell-command
|
|
|
2106 fails under Windows 95 and 98 if you use command.com or any other
|
|
|
2107 16bit program as your shell.
|
|
|
2108
|
|
|
2109 XEmacs may incorrectly quote your call-process command if it contains
|
|
|
2110 double quotes, backslashes or spaces.
|
|
|
2111
|
|
|
2112 start-process and functions that rely on it are supported under Windows 95,
|
|
|
2113 98 and NT. However, starting a 16bit program that requires keyboard input
|
|
|
2114 may cause XEmacs to hang or crash under Windows 95 and 98, and will leave
|
|
|
2115 the orphaned 16bit program consuming all available CPU time.
|
|
|
2116
|
|
|
2117 Sending signals to subprocesses started by call-process or by
|
|
|
2118 start-process fails with a "Cannot send signal to process" error under
|
|
|
2119 Windows 95 and 98. As a side effect of this, quitting XEmacs while it
|
|
|
2120 is still running subprocesses causes it to crash under Windows 95 and
|
|
|
2121 98.
|
|
524
|
2122
|
|
|
2123
|
|
|
2124 ** Cygwin
|
|
1318
|
2125 *** Signal 11 when building or running a dumped XEmacs.
|
|
|
2126
|
|
|
2127 See the section on Cygwin above, under building.
|
|
|
2128
|
|
1058
|
2129 *** XEmacs fails to start because cygXpm-noX4.dll was not found.
|
|
|
2130
|
|
|
2131 Andy Piper <andy@xemacs.org> sez:
|
|
|
2132
|
|
|
2133 cygXpm-noX4 is part of the cygwin distribution under libraries or
|
|
|
2134 graphics, but is not installed by default. You need to run the
|
|
|
2135 cygwin setup again and select this package.
|
|
|
2136
|
|
524
|
2137 *** Subprocesses do not work.
|
|
|
2138
|
|
|
2139 You do not have "tty" in your CYGWIN environment variable. This must
|
|
|
2140 be set in your autoexec.bat (win95) or the system properties (winnt)
|
|
|
2141 as it must be read before the cygwin DLL initializes.
|
|
|
2142
|
|
|
2143 *** ^G does not work on hung subprocesses.
|
|
124
|
2144
|
|
524
|
2145 This is a known problem. It can be remedied by defining BROKEN_SIGIO
|
|
|
2146 in src/s/cygwin.h, however this currently leads to instability in XEmacs.
|
|
|
2147 (#### is this still true?)
|
|
|
2148
|
|
|
2149 *** Errors from make like `/c:not found' when running `M-x compile'.
|
|
308
|
2150
|
|
524
|
2151 Make sure you set the environment variable MAKE_MODE to UNIX in your
|
|
|
2152 init file (.xemacs/init.el), Control Panel (Windows 2000/NT), or
|
|
|
2153 AUTOEXEC.BAT (Windows 98/95).
|
|
|
2154
|
|
|
2155 *** There are no images in the toolbar buttons.
|
|
|
2156
|
|
|
2157 You need version 4.71 of commctrl.dll which does not ship with windows
|
|
|
2158 95. You can get this by installing IE 4.0 or downloading it from the
|
|
|
2159 microsoft website.
|
|
308
|
2160
|
|
197
|
2161
|
|
124
|
2162 * Compatibility problems (with Emacs 18, GNU Emacs, or previous XEmacs/lemacs)
|
|
197
|
2163 ==============================================================================
|
|
88
|
2164
|
|
373
|
2165 *** "Symbol's value as variable is void: unread-command-char".
|
|
197
|
2166 "Wrong type argument: arrayp, #<keymap 143 entries>"
|
|
|
2167 "Wrong type argument: stringp, [#<keypress-event return>]"
|
|
88
|
2168
|
|
124
|
2169 There are a few incompatible changes in XEmacs, and these are the
|
|
|
2170 symptoms. Some of the emacs-lisp code you are running needs to be
|
|
|
2171 updated to be compatible with XEmacs.
|
|
|
2172
|
|
|
2173 The code should not treat keymaps as arrays (use `define-key', etc.),
|
|
|
2174 should not use obsolete variables like `unread-command-char' (use
|
|
197
|
2175 `unread-command-events'). Many (most) of the new ways of doing things
|
|
124
|
2176 are compatible in GNU Emacs and XEmacs.
|
|
88
|
2177
|
|
197
|
2178 Modern Emacs packages (Gnus, VM, W3, efs, etc) are written to support
|
|
|
2179 GNU Emacs and XEmacs. We have provided modified versions of several
|
|
|
2180 popular emacs packages (dired, etc) which are compatible with this
|
|
|
2181 version of emacs. Check to make sure you have not set your load-path
|
|
|
2182 so that your private copies of these packages are being found before
|
|
|
2183 the versions in the lisp directory.
|
|
124
|
2184
|
|
|
2185 Make sure that your load-path and your $EMACSLOADPATH environment
|
|
|
2186 variable are not pointing at an Emacs18 lisp directory. This will
|
|
|
2187 cripple emacs.
|
|
88
|
2188
|
|
124
|
2189 ** Some packages that worked before now cause the error
|
|
223
|
2190 Wrong type argument: arrayp, #<face ... >
|
|
124
|
2191
|
|
197
|
2192 Code which uses the `face' accessor functions must be recompiled with
|
|
|
2193 xemacs 19.9 or later. The functions whose callers must be recompiled
|
|
|
2194 are: face-font, face-foreground, face-background,
|
|
|
2195 face-background-pixmap, and face-underline-p. The .elc files
|
|
|
2196 generated by version 19.9 will work in 19.6 and 19.8, but older .elc
|
|
|
2197 files which contain calls to these functions will not work in 19.9.
|
|
124
|
2198
|
|
|
2199 ** Signaling: (error "Byte code stack underflow (byte compiler bug), pc 38")
|
|
88
|
2200
|
|
120
|
2201 This error is given when XEmacs 20 is compiled without MULE support
|
|
88
|
2202 but is attempting to load a .elc which requires MULE support. The fix
|
|
|
2203 is to rebytecompile the offending file.
|
|
|
2204
|
|
124
|
2205 ** Signaling: (wrong-type-argument ...) when loading mail-abbrevs
|
|
88
|
2206
|
|
197
|
2207 The is seen when installing the Insidious Big Brother Data Base (bbdb)
|
|
|
2208 which includes an outdated copy of mail-abbrevs.el. Remove the copy
|
|
|
2209 that comes with bbdb and use the one that comes with XEmacs.
|
|
|
2210
|
|
144
|
2211
|
|
|
2212 * MULE issues
|
|
197
|
2213 =============
|
|
144
|
2214
|
|
223
|
2215 ** A reminder: XEmacs/Mule work does not currently receive *any*
|
|
|
2216 funding, and all work is done by volunteers. If you think you can
|
|
|
2217 help, please contact the XEmacs maintainers.
|
|
|
2218
|
|
278
|
2219 ** XEmacs/Mule doesn't support TTY's satisfactorily.
|
|
223
|
2220
|
|
|
2221 This is a major problem, which we plan to address in a future release
|
|
|
2222 of XEmacs. Basically, XEmacs should have primitives to be told
|
|
|
2223 whether the terminal can handle international output, and which
|
|
|
2224 locale. Also, it should be able to do approximations of characters to
|
|
|
2225 the nearest supported by the locale.
|
|
|
2226
|
|
197
|
2227 ** Internationalized (Asian) Isearch doesn't work.
|
|
144
|
2228
|
|
|
2229 Currently, Isearch doesn't directly support any of the input methods
|
|
|
2230 that are not XIM based (like egg, canna and quail) (and there are
|
|
223
|
2231 potential problems with XIM version too...). If you're using egg
|
|
|
2232 there is a workaround. Hitting <RET> right after C-s to invoke
|
|
|
2233 Isearch will put Isearch in string mode, where a complete string can
|
|
|
2234 be typed into the minibuffer and then processed by Isearch afterwards.
|
|
|
2235 Since egg is now supported in the minibuffer using string mode you can
|
|
|
2236 now use egg to input your Japanese, Korean or Chinese string, then hit
|
|
|
2237 return to send that to Isearch and then use standard Isearch commands
|
|
|
2238 from there.
|
|
144
|
2239
|
|
223
|
2240 ** Using egg and mousing around while in 'fence' mode screws up my
|
|
|
2241 buffer.
|
|
144
|
2242
|
|
|
2243 Don't do this. The fence modes of egg and canna are currently very
|
|
|
2244 modal, and messing with where they expect point to be and what they
|
|
|
2245 think is the current buffer is just asking for trouble. If you're
|
|
|
2246 lucky they will realize that something is awry, and simply delete the
|
|
|
2247 fence, but worst case can trash other buffers too. We've tried to
|
|
|
2248 protect against this where we can, but there still are many ways to
|
|
|
2249 shoot yourself in the foot. So just finish what you are typing into
|
|
|
2250 the fence before reaching for the mouse.
|
|
223
|
2251
|
|
|
2252 ** Not all languages in Quail are supported like Devanagari and Indian
|
|
|
2253 languages, Lao and Tibetan.
|
|
|
2254
|
|
|
2255 Quail requires more work and testing. Although it has been ported to
|
|
|
2256 XEmacs, it works really well for Japanese and for the European
|
|
|
2257 languages.
|
|
|
2258
|
|
|
2259 ** Right-to-left mode is not yet implemented, so languages like
|
|
|
2260 Arabic, Hebrew and Thai don't work.
|
|
|
2261
|
|
|
2262 Getting this right requires more work. It may be implemented in a
|
|
|
2263 future XEmacs version, but don't hold your breath. If you know
|
|
|
2264 someone who is ready to implement this, please let us know.
|
|
|
2265
|
|
|
2266 ** We need more developers and native language testers. It's extremely
|
|
|
2267 difficult (and not particularly productive) to address languages that
|
|
|
2268 nobody is using and testing.
|
|
|
2269
|
|
|
2270 ** The kWnn and cWnn support for Chinese and Korean needs developers
|
|
|
2271 and testers. It probably doesn't work.
|
|
|
2272
|
|
|
2273 ** There are no `native XEmacs' TUTORIALs for any Asian languages,
|
|
454
|
2274 including Japanese. FSF Emacs and XEmacs tutorials are quite similar,
|
|
223
|
2275 so it should be sufficient to skim through the differences and apply
|
|
|
2276 them to the Japanese version.
|
|
|
2277
|
|
|
2278 ** We only have localized menus translated for Japanese, and the
|
|
|
2279 Japanese menus are developing bitrot (the Mule menu appears in
|
|
|
2280 English).
|
|
|
2281
|
|
|
2282 ** XIM is untested for any language other than Japanese.
|
