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