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