comparison PROBLEMS @ 1098:25f567f6ab2a

[xemacs-hg @ 2002-11-11 16:13:28 by stephent] IRIX PROBLEM <871y5sytkx.fsf@tleepslib.sk.tsukuba.ac.jp>
author stephent
date Mon, 11 Nov 2002 16:13:28 +0000
parents d7285d54aa5f
children d50ab2546522
comparison
equal deleted inserted replaced
1097:26274e0d7794 1098:25f567f6ab2a
41 41
42 ** General 42 ** General
43 Much general information is in INSTALL. If it's covered in 43 Much general information is in INSTALL. If it's covered in
44 INSTALL, we don't repeat it here. 44 INSTALL, we don't repeat it here.
45 45
46 *** How does I configure to get the buffer tabs/progress bars? 46 *** How do I configure to get the buffer tabs/progress bars?
47 47
48 These features depend on support for "native widgets". Use the 48 These features depend on support for "native widgets". Use the
49 --with-widgets option to configure. Configuration of widgets is 49 --with-widgets option to configure. Configuration of widgets is
50 automatic for "modern" toolkits (MS Windows, GTK, and Motif), but if 50 automatic for "modern" toolkits (MS Windows, GTK, and Motif), but if
51 you are using Xt and the Athena widgets, you will probably want to 51 you are using Xt and the Athena widgets, you will probably want to
400 This is a Linux problem where you've compiled the XEmacs binary on a libc 400 This is a Linux problem where you've compiled the XEmacs binary on a libc
401 5.4 with version higher than 5.4.19 and attempted to run the binary against 401 5.4 with version higher than 5.4.19 and attempted to run the binary against
402 an earlier version. The solution is to upgrade your old library. 402 an earlier version. The solution is to upgrade your old library.
403 403
404 ** IRIX 404 ** IRIX
405
406 *** More coredumping in Irix (6.5 known to be vulnerable)
407
408 No fix is known yet. Here's the best information we have:
409
410 Valdis Kletnieks <Valdis.Kletnieks@vt.edu> writes:
411
412 Were xemacs and [any 3rd party, locally-compiled] libraries [you use]
413 all compiled with the same ABI ( -o32, -n32, -64) and
414 mips2/mips3/mips4 flags, and are they appropriate for the machine in
415 question? I know the IP30 implies an Octane, so it should be an R10K
416 chipset and above such nonsense, but I've seen the most astoundingly
417 bizzare crashes when somebody managed to compile with -mips4 and get
418 it to run on an R4400 or R5K system. ;)
419
420 Also, since you're using gcc, try re-running fixincludes and *then*
421 rebuilding xemacs and [any] libraries - mismatched headers can do that
422 sort of thing to you with little or no clue what's wrong (often you
423 get screwed when one routine does an malloc(sizeof(foo_struct)) and
424 passes the result to something that things foo_struct is a bit bigger,
425 trashing memory....
426
427 Here's typical crash backtrace. With --pdump, this occurs usually at
428 startup under X windows and xemacs -nw at least starts, while without
429 --pdump a similar crash is observed during build.
430
431 #0 0x0fa460b8 in kill () at regcomp.c:637
432 637 regcomp.c: No such file or directory.
433 in regcomp.c
434 (gdb) where
435 #0 0x0fa460b8 in kill () at regcomp.c:637
436 #1 0x10087f34 in fatal_error_signal ()
437 (gdb) quit
438
439 This is confusing because there is no such file in the XEmacs
440 distribution. This is seen on (at least) the following configurations:
441
442 uname -a: IRIX64 oct202 6.5 01091821 IP30
443 XEmacs 21.4.9 "Informed Management" configured for `mips-sgi-irix6.5'.
444 XEmacs 21.5-b9 "brussels sprouts" configured for `mips-sgi-irix6.5'.
405 445
406 *** On Irix 6.5, the MIPSpro compiler gets an internal compiler error 446 *** On Irix 6.5, the MIPSpro compiler gets an internal compiler error
407 447
408 The MIPSpro Compiler (at least version 7.2.1) can't seem to handle the 448 The MIPSpro Compiler (at least version 7.2.1) can't seem to handle the
409 union type properly, and fails to compile src/glyphs.c. To avoid this 449 union type properly, and fails to compile src/glyphs.c. To avoid this