May 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Coredumping bug in 21 (read-kbd-macro) 26 years

SL Baur

This causes a core dump for me, beware. There's probably a dependency on XEmacs/Mule. XEmacs 20.4 gives similarly weird displays. $ xemacs-21.0-b38 -vanilla (read-kbd-macro "\H-a") The buffer moves all the way to the bottom as shown by the scrollbar and only the line: [?a<Black Square>] is displayed. The `<Black Square>' is a single black square the size of a character. Now move the cursor around a bit with a combination of key strokes and mouse clicks, eventually: Starting program: /usr/src/build20/mule/src/xemacs -vanilla Fatal error: assertion failed, file /home/xemacs/xemacs-20.0/src/editfns.c, line 338, XINT (Fpoint (Qnil)) == XINT (Fmarker_position (Fpoint_marker (Qt, Qnil))) Program received signal SIGABRT, Aborted. 0x4034c5f1 in kill () at soinit.c:27 soinit.c:27: No such file or directory. (gdb) where #0 0x4034c5f1 in kill () at soinit.c:27 #1 0x4034c451 in raise (sig=136527043) at ../sysdeps/posix/raise.c:27 #2 0x80b18b9 in save_excursion_save () at /home/xemacs/xemacs-20.0/src/editfns.c:337 #3 0x809235a in Fbyte_code (bytestr={gu = {type = Lisp_Type_Record, val = 34427168}, s = {bits = 0, val = 68854336}, u = {bits = 0, val = 68854336}, ui = 137708672, i = 137708672, v = 0x8354480, cv = 0x8354480}, vector={gu = {type = Lisp_Type_Record, val = 34427251}, s = {bits = 0, val = 68854502}, u = {bits = 0, val = 68854502}, ui = 137709004, i = 137709004, v = 0x83545cc, cv = 0x83545cc}, maxdepth={ gu = {type = Lisp_Type_Int_Even, val = 3}, s = {bits = 1, val = 6}, u = { bits = 1, val = 6}, ui = 13, i = 13, v = 0xd, cv = 0xd}) at /home/xemacs/xemacs-20.0/src/bytecode.c:545 #4 0x80c1eaa in funcall_lambda (fun={gu = {type = Lisp_Type_Record, val = 34427309}, s = {bits = 0, val = 68854618}, u = {bits = 0, val = 68854618}, ui = 137709236, i = 137709236, v = 0x83546b4, cv = 0x83546b4}, nargs=1, arg_vector=0xbfffd3b4) at /home/xemacs/xemacs-20.0/src/eval.c:3597 #5 0x80c0e64 in funcall_recording_as (recorded_as={gu = { type = Lisp_Type_Record, val = 34802314}, s = {bits = 0, val = 69604628}, u = {bits = 0, val = 69604628}, ui = 139209256, i = 139209256, v = 0x84c2a28, cv = 0x84c2a28}, nargs=1, args=0xbfffd3b0) at /home/xemacs/xemacs-20.0/src/eval.c:3200 #6 0x80c0f94 in Ffuncall (nargs=2, args=0xbfffd3b0) at /home/xemacs/xemacs-20.0/src/eval.c:3238 #7 0x8091866 in Fbyte_code (bytestr={gu = {type = Lisp_Type_Record, val = 34427617}, s = {bits = 0, val = 68855234}, u = {bits = 0, val = 68855234}, ui = 137710468, i = 137710468, v = 0x8354b84, cv = 0x8354b84}, vector={gu = {type = Lisp_Type_Record, val = 34427630}, s = {bits = 0, val = 68855260}, u = {bits = 0, val = 68855260}, ui = 137710520, i = 137710520, v = 0x8354bb8, cv = 0x8354bb8}, maxdepth={ gu = {type = Lisp_Type_Int_Even, val = 2}, s = {bits = 1, val = 4}, u = { bits = 1, val = 4}, ui = 9, i = 9, v = 0x9, cv = 0x9}) at /home/xemacs/xemacs-20.0/src/bytecode.c:416 #8 0x80c1eaa in funcall_lambda (fun={gu = {type = Lisp_Type_Record, val = 34427645}, s = {bits = 0, val = 68855290}, u = {bits = 0, val = 68855290}, ui = 137710580, i = 137710580, v = 0x8354bf4, cv = 0x8354bf4}, nargs=3, arg_vector=0xbfffd84c) at /home/xemacs/xemacs-20.0/src/eval.c:3597 #9 0x80c0e64 in funcall_recording_as (recorded_as={gu = { type = Lisp_Type_Record, val = 34802363}, s = {bits = 0, val = 69604726}, u = {bits = 0, val = 69604726}, ui = 139209452, i = 139209452, v = 0x84c2aec, cv = 0x84c2aec}, nargs=3, args=0xbfffd848) at /home/xemacs/xemacs-20.0/src/eval.c:3200 #10 0x80c0f94 in Ffuncall (nargs=4, args=0xbfffd848) at /home/xemacs/xemacs-20.0/src/eval.c:3238 #11 0x8091866 in Fbyte_code (bytestr={gu = {type = Lisp_Type_Record, val = 34427821}, s = {bits = 0, val = 68855642}, u = {bits = 0, val = 68855642}, ui = 137711284, i = 137711284, v = 0x8354eb4, cv = 0x8354eb4}, vector={gu = {type = Lisp_Type_Record, val = 34427831}, s = {bits = 0, val = 68855662}, u = {bits = 0, val = 68855662}, ui = 137711324, i = 137711324, v = 0x8354edc, cv = 0x8354edc}, maxdepth={ gu = {type = Lisp_Type_Int_Even, val = 2}, s = {bits = 1, val = 4}, u = { bits = 1, val = 4}, ui = 9, i = 9, v = 0x9, cv = 0x9}) at /home/xemacs/xemacs-20.0/src/bytecode.c:416 #12 0x80c1eaa in funcall_lambda (fun={gu = {type = Lisp_Type_Record, val = 34427841}, s = {bits = 0, val = 68855682}, u = {bits = 0, val = 68855682}, ui = 137711364, i = 137711364, v = 0x8354f04, cv = 0x8354f04}, nargs=2, arg_vector=0xbfffdfd8) at /home/xemacs/xemacs-20.0/src/eval.c:3597 #13 0x80c0e64 in funcall_recording_as (recorded_as={gu = { type = Lisp_Type_Record, val = 34802398}, s = {bits = 0, val = 69604796}, u = {bits = 0, val = 69604796}, ui = 139209592, i = 139209592, v = 0x84c2b78, cv = 0x84c2b78}, nargs=2, args=0xbfffdfd4) at /home/xemacs/xemacs-20.0/src/eval.c:3200 #14 0x80c0f94 in Ffuncall (nargs=3, args=0xbfffdfd4) at /home/xemacs/xemacs-20.0/src/eval.c:3238 #15 0x80c161e in Fapply (nargs=3, args=0xbfffdfd4) at /home/xemacs/xemacs-20.0/src/eval.c:3408 #16 0x80c09ef in funcall_recording_as (recorded_as={gu = { type = Lisp_Type_Record, val = 34537712}, s = {bits = 0, val = 69075424}, u = {bits = 0, val = 69075424}, ui = 138150848, i = 138150848, v = 0x83c03c0, cv = 0x83c03c0}, nargs=3, args=0xbfffdfd0) at /home/xemacs/xemacs-20.0/src/eval.c:3178 #17 0x80c0f94 in Ffuncall (nargs=4, args=0xbfffdfd0) at /home/xemacs/xemacs-20.0/src/eval.c:3238 #18 0x8091866 in Fbyte_code (bytestr={gu = {type = Lisp_Type_Record, val = 34425415}, s = {bits = 0, val = 68850830}, u = {bits = 0, val = 68850830}, ui = 137701660, i = 137701660, v = 0x835291c, cv = 0x835291c}, vector={gu = {type = Lisp_Type_Record, val = 34425466}, s = {bits = 0, val = 68850932}, u = {bits = 0, val = 68850932}, ui = 137701864, i = 137701864, v = 0x83529e8, cv = 0x83529e8}, maxdepth={ gu = {type = Lisp_Type_Int_Odd, val = 2}, s = {bits = 1, val = 5}, u = { bits = 1, val = 5}, ui = 11, i = 11, v = 0xb, cv = 0xb}) at /home/xemacs/xemacs-20.0/src/bytecode.c:416 #19 0x80c1eaa in funcall_lambda (fun={gu = {type = Lisp_Type_Record, val = 34425485}, s = {bits = 0, val = 68850970}, u = {bits = 0, val = 68850970}, ui = 137701940, i = 137701940, v = 0x8352a34, cv = 0x8352a34}, nargs=3, arg_vector=0xbfffe8bc) at /home/xemacs/xemacs-20.0/src/eval.c:3597 #20 0x80c0e64 in funcall_recording_as (recorded_as={gu = { type = Lisp_Type_Record, val = 34802048}, s = {bits = 0, val = 69604096}, u = {bits = 0, val = 69604096}, ui = 139208192, i = 139208192, v = 0x84c2600, cv = 0x84c2600}, nargs=3, args=0xbfffe8b8) at /home/xemacs/xemacs-20.0/src/eval.c:3200 #21 0x80c0f94 in Ffuncall (nargs=4, args=0xbfffe8b8) at /home/xemacs/xemacs-20.0/src/eval.c:3238 #22 0x8091866 in Fbyte_code (bytestr={gu = {type = Lisp_Type_Record, val = 34425554}, s = {bits = 0, val = 68851108}, u = {bits = 0, val = 68851108}, ui = 137702216, i = 137702216, v = 0x8352b48, cv = 0x8352b48}, vector={gu = {type = Lisp_Type_Record, val = 34425658}, s = {bits = 0, val = 68851316}, u = {bits = 0, val = 68851316}, ui = 137702632, i = 137702632, v = 0x8352ce8, cv = 0x8352ce8}, maxdepth={ gu = {type = Lisp_Type_Int_Even, val = 4}, s = {bits = 1, val = 8}, u = { bits = 1, val = 8}, ui = 17, i = 17, v = 0x11, cv = 0x11}) at /home/xemacs/xemacs-20.0/src/bytecode.c:416 #23 0x80c1eaa in funcall_lambda (fun={gu = {type = Lisp_Type_Record, val = 34425765}, s = {bits = 0, val = 68851530}, u = {bits = 0, val = 68851530}, ui = 137703060, i = 137703060, v = 0x8352e94, cv = 0x8352e94}, nargs=1, arg_vector=0xbfffed2c) at /home/xemacs/xemacs-20.0/src/eval.c:3597 #24 0x80c0e64 in funcall_recording_as (recorded_as={gu = { type = Lisp_Type_Record, val = 34791914}, s = {bits = 0, val = 69583828}, u = {bits = 0, val = 69583828}, ui = 139167656, i = 139167656, v = 0x84b87a8, cv = 0x84b87a8}, nargs=1, args=0xbfffed28) at /home/xemacs/xemacs-20.0/src/eval.c:3200 #25 0x80c0f94 in Ffuncall (nargs=2, args=0xbfffed28) at /home/xemacs/xemacs-20.0/src/eval.c:3238 #26 0x80970e8 in Fcall_interactively (function={gu = {type = Lisp_Type_Record, val = 34791914}, s = {bits = 0, val = 69583828}, u = {bits = 0, val = 69583828}, ui = 139167656, i = 139167656, v = 0x84b87a8, cv = 0x84b87a8}, record_flag={gu = {type = Lisp_Type_Record, val = 34516825}, s = {bits = 0, val = 69033650}, u = {bits = 0, val = 69033650}, ui = 138067300, i = 138067300, v = 0x83abd64, cv = 0x83abd64}, keys={gu = {type = Lisp_Type_Record, val = 34516825}, s = {bits = 0, val = 69033650}, u = {bits = 0, val = 69033650}, ui = 138067300, i = 138067300, v = 0x83abd64, cv = 0x83abd64}) at /home/xemacs/xemacs-20.0/src/callint.c:935 #27 0x80bf228 in Fcommand_execute (cmd={gu = {type = Lisp_Type_Record, val = 34791914}, s = {bits = 0, val = 69583828}, u = {bits = 0, val = 69583828}, ui = 139167656, i = 139167656, v = 0x84b87a8, cv = 0x84b87a8}, record={gu = {type = Lisp_Type_Record, val = 34516825}, s = {bits = 0, val = 69033650}, u = {bits = 0, val = 69033650}, ui = 138067300, i = 138067300, v = 0x83abd64, cv = 0x83abd64}, keys={ gu = {type = Lisp_Type_Record, val = 34516825}, s = {bits = 0, val = 69033650}, u = {bits = 0, val = 69033650}, ui = 138067300, i = 138067300, v = 0x83abd64, cv = 0x83abd64}) at /home/xemacs/xemacs-20.0/src/eval.c:2584 #28 0x8116984 in execute_command_event (command_builder=0x84f68d0, event={ gu = {type = Lisp_Type_Record, val = 35040819}, s = {bits = 0, val = 70081638}, u = {bits = 0, val = 70081638}, ui = 140163276, i = 140163276, v = 0x85ab8cc, cv = 0x85ab8cc}) at /home/xemacs/xemacs-20.0/src/event-stream.c:4335 #29 0x811707b in Fdispatch_event (event={gu = {type = Lisp_Type_Record, val = 35040819}, s = {bits = 0, val = 70081638}, u = {bits = 0, val = 70081638}, ui = 140163276, i = 140163276, v = 0x85ab8cc, cv = 0x85ab8cc}) at /home/xemacs/xemacs-20.0/src/event-stream.c:4629 #30 0x809eb1c in Fcommand_loop_1 () at /home/xemacs/xemacs-20.0/src/cmdloop.c:583 #31 0x809e8a0 in command_loop_1 (dummy={gu = {type = Lisp_Type_Record, val = 34516825}, s = {bits = 0, val = 69033650}, u = {bits = 0, val = 69033650}, ui = 138067300, i = 138067300, v = 0x83abd64, cv = 0x83abd64}) at /home/xemacs/xemacs-20.0/src/cmdloop.c:494 #32 0x80bd8bb in condition_case_1 (handlers={gu = {type = Lisp_Type_Record, val = 34516853}, s = {bits = 0, val = 69033706}, u = {bits = 0, val = 69033706}, ui = 138067412, i = 138067412, v = 0x83abdd4, cv = 0x83abdd4}, bfun=0x809e874 <command_loop_1>, barg={gu = { type = Lisp_Type_Record, val = 34516825}, s = {bits = 0, val = 69033650}, u = {bits = 0, val = 69033650}, ui = 138067300, i = 138067300, v = 0x83abd64, cv = 0x83abd64}, hfun=0x809e07b <cmd_error>, harg={gu = {type = Lisp_Type_Record, val = 34516825}, s = {bits = 0, val = 69033650}, u = {bits = 0, val = 69033650}, ui = 138067300, i = 138067300, v = 0x83abd64, cv = 0x83abd64}) at /home/xemacs/xemacs-20.0/src/eval.c:1653 #33 0x809e1c3 in command_loop_3 () at /home/xemacs/xemacs-20.0/src/cmdloop.c:256 #34 0x809e1e8 in command_loop_2 (dummy={gu = {type = Lisp_Type_Record, val = 34516825}, s = {bits = 0, val = 69033650}, u = {bits = 0, val = 69033650}, ui = 138067300, i = 138067300, v = 0x83abd64, cv = 0x83abd64}) at /home/xemacs/xemacs-20.0/src/cmdloop.c:267 #35 0x80bd40d in internal_catch (tag={gu = {type = Lisp_Type_Record, val = 34535502}, s = {bits = 0, val = 69071004}, u = {bits = 0, val = 69071004}, ui = 138142008, i = 138142008, v = 0x83be138, cv = 0x83be138}, func=0x809e1dc <command_loop_2>, arg={gu = { type = Lisp_Type_Record, val = 34516825}, s = {bits = 0, val = 69033650}, u = {bits = 0, val = 69033650}, ui = 138067300, i = 138067300, v = 0x83abd64, cv = 0x83abd64}, threw=0x0) at /home/xemacs/xemacs-20.0/src/eval.c:1328 #36 0x809e43e in initial_command_loop (load_me={gu = {type = Lisp_Type_Record, val = 34516825}, s = {bits = 0, val = 69033650}, u = {bits = 0, val = 69033650}, ui = 138067300, i = 138067300, v = 0x83abd64, cv = 0x83abd64}) at /home/xemacs/xemacs-20.0/src/cmdloop.c:305 #37 0x80b92ad in xemacs_21_0_b38_i586_pc_linux (argc=2, argv=0xbffff2d4, envp=0xbffff2e0, restart=0) at /home/xemacs/xemacs-20.0/src/emacs.c:1673 #38 0x80b9dce in main (argc=2, argv=0xbffff2d4, envp=0xbffff2e0) at /home/xemacs/xemacs-20.0/src/emacs.c:2090 uname -a: Linux altair.xemacs.org 2.0.32 #2 Sun Nov 16 18:52:14 PST 1997 i586 /home/xemacs/xemacs-20.0/configure '--with-gnu-make' '--srcdir=/home/xemacs/xemacs-20.0' '--cflags=-g -fno-exceptions' '--error-checking=all' '--debug=yes' '--with-mule=yes' '--with-dialogs=athena3d' '--with-scrollbars=athena3d' '--with-xim=xlib' '--mail-locking=file' '--extra-verbose=yes' '--use-union-type=yes' '--with-xfs=yes' '--with-pop=no' '--with-toolbars=yes' '--compiler=pgcc' XEmacs 21.0-b38 "Repartida-pre3" configured for `i586-pc-linux'. Where should the build process find the source code? /home/xemacs/xemacs-20.0 What installation prefix should install use? /usr/local What operating system and machine description files should XEmacs use? `s/linux.h' and `m/intel386.h' What compiler should XEmacs be built with? pgcc -g -fno-exceptions Should XEmacs use the GNU version of malloc? yes (Using Doug Lea's new malloc from the GNU C Library.) Should XEmacs use the relocating allocator for buffers? yes What window system should XEmacs use? x11 Where do we find X Windows header files? /usr/X11/include Where do we find X Windows libraries? /usr/X11/lib Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for X-Face message headers. Compiling in support for GIF image conversion. Compiling in support for JPEG image conversion. Compiling in support for PNG image conversion. Compiling in support for TIFF image conversion. Compiling in native sound support. Compiling in support for Berkeley DB. Compiling in support for GNU DBM. Compiling in support for ncurses. Compiling in support for GPM (General Purpose Mouse). Compiling in Mule (multi-lingual) support. Compiling in XIM (X11R5+ I18N input method) support. Using raw Xlib to provide XIM support. Using XFontSet to provide bilingual menubar. Compiling in support for Canna on Mule. Compiling in support for the WNN input method on Mule. Using WNN version 6. Compiling in support for OffiX. Compiling in support for proper session-management. Using Lucid menubars. Using Athena-3d scrollbars. Using Athena-3d dialog boxes. Compiling in DLL support. movemail will use "dot-locking" for locking mail spool files. Using the union type for Lisp_Objects. Using Lisp_Objects with minimal tagbits. Compiling in extra code for debugging. Compiling in code for checking XEmacs memory usage. WARNING: --------------------------------------------------------- WARNING: Compiling in support for runtime error checking. WARNING: XEmacs will run noticeably more slowly as a result. WARNING: Error checking is on by default for XEmacs beta releases. WARNING: ---------------------------------------------------------

1 participants
0 comments

[success] 21.0 "Repartida-pre3" XEmacs Lucid (beta38) on i586-pc-linux 26 years

Stefanie Teufel

Nice and easy. Stefanie > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /usr/local/xemacs-20.0/Installation: > (Output from most recent run of ./configure)

1 participants
0 comments

Re: [Success] XEmacs 21.0-b38 "Repartida-pre2" on i686-linux 26 years

SL Baur

toge <toge(a)accad1.kek.jp> writes: > ------ BEGIN ----- > Signaling: (file-error "Cannot open load file" "images") > signal(file-error ("Cannot open load file" "images")) > load("images" nil t nil) > require(images) > byte-code("..." [require tm-view running-xemacs ... Hmm, that's not Gnus, that's tm and the images.el file is useful in its own right ...

1 participants
0 comments

[SUCCESS] 21.0 "Repartida-pre3" XEmacs Lucid (beta38) on i586-pc-linux 26 years

Michael Harnois

Via CVS. egcs-2.91.25 > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /usr/src/xemacs/Installation: > (Output from most recent run of ./configure) uname -a: Linux mharnois 2.1.99 #31 Fri May 1 21:54:37 CDT 1998 i586 unknown ../xemacs-20/configure '--with-mule' '--extra-verbose' '--cflags=-g -O6 -mpentium -fno-expensive-optimizations -fno-exceptions -fno-omit-frame-pointer' '--with-scrollbars=athena3d' '--with-dialogs=athena3d' '--gung-ho' '--with-gnu-make' '--srcdir=/usr/src/xemacs-20' '--with-database=no' '--error-checking=none' '--use-union-type' XEmacs 21.0-b38 "Repartida-pre3" configured for `i586-pc-linux'. Where should the build process find the source code? /usr/src/xemacs-20 What installation prefix should install use? /usr/local What operating system and machine description files should XEmacs use? `s/linux.h' and `m/intel386.h' What compiler should XEmacs be built with? gcc -g -O6 -mpentium -fno-expensive-optimizations -fno-exceptions -fno-omit-frame-pointer Should XEmacs use the GNU version of malloc? yes (Using Doug Lea's new malloc from the GNU C Library.) Should XEmacs use the relocating allocator for buffers? yes What window system should XEmacs use? x11 Where do we find X Windows header files? /usr/X11R6/include Where do we find X Windows libraries? /usr/X11R6/lib Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for X-Face message headers. Compiling in support for JPEG image conversion. Compiling in support for PNG image conversion. Compiling in support for TIFF image conversion. Compiling in native sound support. Compiling in support for ncurses. Compiling in support for GPM (General Purpose Mouse). Compiling in Mule (multi-lingual) support. Compiling in XIM (X11R5+ I18N input method) support. Using Motif to provide XIM support. Compiling in support for Canna on Mule. Compiling in support for OffiX. Compiling in support for proper session-management. Using Lucid menubars. Using Athena-3d scrollbars. Using Athena-3d dialog boxes. Compiling in DLL support. movemail will use "dot-locking" for locking mail spool files. Using the union type for Lisp_Objects. Using Lisp_Objects with minimal tagbits. Using indexed lrecord implementation. Compiling in extra code for debugging. Compiling in code for checking XEmacs memory usage. > Contents of /usr/src/xemacs/beta.err > keeping lines matching > "^--\[\[\|\]\]$\|make\[\|error\|warn\|pure.*$space\|size$\|hides\b\|strange\|shadowings\|^Compilation\|not\s-+found" > and then deleting lines matching > "confl.*with.*auto-inlining\|/usr/src/xemacs/lisp/[^ ]+ hides " make[1]: Entering directory `/usr/src/xemacs/lib-src' make[1]: Leaving directory `/usr/src/xemacs/lib-src' make[1]: Entering directory `/usr/src/xemacs/lwlib' make[1]: Leaving directory `/usr/src/xemacs/lwlib' make[1]: Entering directory `/usr/src/xemacs/src' core temacs.exe puresize-adjust.h sheap-adjust.h make[1]: Leaving directory `/usr/src/xemacs/src' make[1]: Entering directory `/usr/src/xemacs-20/man' make[2]: Entering directory `/usr/src/xemacs-20/man/xemacs' make[2]: Leaving directory `/usr/src/xemacs-20/man/xemacs' make[2]: Entering directory `/usr/src/xemacs-20/man/lispref' make[2]: Leaving directory `/usr/src/xemacs-20/man/lispref' make[2]: Entering directory `/usr/src/xemacs-20/man/new-users-guide' make[2]: Leaving directory `/usr/src/xemacs-20/man/new-users-guide' make[2]: Entering directory `/usr/src/xemacs-20/man/internals' make[2]: Leaving directory `/usr/src/xemacs-20/man/internals' make[2]: Entering directory `/usr/src/xemacs-20/man/xemacs' make[2]: Leaving directory `/usr/src/xemacs-20/man/xemacs' make[2]: Entering directory `/usr/src/xemacs-20/man/lispref' make[2]: Leaving directory `/usr/src/xemacs-20/man/lispref' make[2]: Entering directory `/usr/src/xemacs-20/man/new-users-guide' make[2]: Leaving directory `/usr/src/xemacs-20/man/new-users-guide' make[2]: Entering directory `/usr/src/xemacs-20/man/internals' make[2]: Leaving directory `/usr/src/xemacs-20/man/internals' make[1]: Leaving directory `/usr/src/xemacs-20/man' Resetting `src/puresize-adjust.h'. make[1]: Entering directory `/usr/src/xemacs/lib-src' make[1]: Leaving directory `/usr/src/xemacs/lib-src' make[1]: Entering directory `/usr/src/xemacs/lwlib' make[1]: Leaving directory `/usr/src/xemacs/lwlib' make[1]: Entering directory `/usr/src/xemacs/src' Purespace usage: 102808 of 1599000 (6% -- 1461k wasted). make[1]: Leaving directory `/usr/src/xemacs/src' make[1]: Entering directory `/usr/src/xemacs/src' Purespace usage: 914128 of 1599000 (57% -- 668k wasted). XEmacs: Pure size adjusted, Don't Panic! I will restart the `make' make[1]: [xemacs] Error 1 (ignored) make[2]: Entering directory `/usr/src/xemacs/src' Purespace usage: 914128 of 914128 (100%). make[2]: Leaving directory `/usr/src/xemacs/src' make[1]: Leaving directory `/usr/src/xemacs/src' get-fontset-info, mswindows-font-canicolize-name, font-warn,

1 participants
0 comments

Re: De-GIFfing (was Re: beta38-pre3 has been uploaded) 26 years

SL Baur

Glynn Clements <glynn(a)sensei.co.uk> writes: > Why PNG, as opposed to Xpm? Size.

1 participants
0 comments

[bug] Uninterruptible regexp search 26 years

Hrvoje Niksic

This example is pasted from the manual, and C-g doesn't work. :-( (string-match "\$x+y*\$*a" "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxz") Fortunately, `kill -FPE PID' works. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- Jone's law: The man who smiles when things go wrong has thought of someone to blame it on.

1 participants
0 comments

Re: [Success] 21.0 "Repartida-pre2" XEmacs Lucid (beta38-pre2) on i 386-pc-cygwin32 26 years

SL Baur

Ian MacKinnon <IMacKinnon(a)telia.co.uk> writes: > Does any one else have to hack the filename of the pre patches so > patch-xemacs will work ? Is this the case? The pre-patches are generated the same way the beta-n -> beta-n+1 patches are generated and should work with any reasonable version of patch. I know `cvs diff' causes heartache, weeping and gnashing of teeth with malformed filenames in patches, but this is the first I've heard of `cvs rdiff' having a problem. Index: xemacs-20.0/CHANGES-beta diff -u xemacs-20.0/CHANGES-beta:1.125 xemacs-20.0/CHANGES-beta:1.128 --- xemacs-20.0/CHANGES-beta:1.125 Sat Apr 25 21:07:11 1998 +++ xemacs-20.0/CHANGES-beta Wed Apr 29 16:03:42 1998 You have to specify `-p1' to patch to make the first part of the path go away, but that should be all.

2 participants
1 comments

DND for XEmacs 21 26 years

Hrvoje Niksic

This is likely the last chance to fix up the DND code for XEmacs 21. Do the maintainers plan to work on it? -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- Old numerical analysts never die, they just get disarrayed.

1 participants
0 comments

[Success] 21.0 "Repartida-pre3" XEmacs Lucid (beta38) on i386-pc -cygwin32 26 years

Michael Hill

With Andy's cygwin32.h patch. Dialog boxes don't co-exist with enabled toolbar. Configured --with-toolbars=no they work. If I first invoke Info from the toolbar, I get: Wrong type argument: stringp, nil followed by an empty Info frame (with the Info toolbar). If I first invoke it from the keyboard or menubar, then it works from all three. Mike > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /binary/xemacs-21.0-b37/Installation: > (Output from most recent run of ./configure) uname -a: CYGWIN32_NT DILBERT 4.0 19.1 i686 unknown ./configure '--site-includes=/usr/local/include' XEmacs 21.0-b38 "Repartida-pre3" configured for `i386-pc-cygwin32'. Where should the build process find the source code? /binary/xemacs-21.0-b37 What installation prefix should install use? /usr/local What operating system and machine description files should XEmacs use? `s/cygwin32.h' and `m/intel386.h' What compiler should XEmacs be built with? gcc -g -O2 -Wall -Wno-switch Should XEmacs use the GNU version of malloc? yes Should XEmacs use the relocating allocator for buffers? default What window system should XEmacs use? x11 Where do we find X Windows header files? /usr/X11R6.3/include Where do we find X Windows libraries? /usr/X11R6.3/lib Additional header files: /usr/local/include Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for GIF image conversion. Compiling in support for JPEG image conversion. Compiling in support for PNG image conversion. Compiling in support for TIFF image conversion. Compiling in support for GNU DBM. Compiling in support for ncurses. Compiling in File coding support. Compiling in support for OffiX. Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Athena dialog boxes. movemail will use "dot-locking" for locking mail spool files. Using Lisp_Objects with minimal tagbits. Using indexed lrecord implementation. Compiling in extra code for debugging. Compiling in code for checking XEmacs memory usage. WARNING: --------------------------------------------------------- WARNING: Compiling in support for runtime error checking. WARNING: XEmacs will run noticeably more slowly as a result. WARNING: Error checking is on by default for XEmacs beta releases. WARNING: --------------------------------------------------------- > /binary/xemacs-21.0-b37/beta.err does not exist!

1 participants
0 comments

xemacs-patches: new list, new patch approval process 26 years

Jason R Mastaler

Announcing a new mailing list, xemacs-patches(a)xemacs.org. Also, please see the forwarded message below for changes in the XEmacs patch approval process that are effective immediately. xemacs-patches is an open, moderated list for submission of patches to the XEmacs distribution and its packages. Anyone may subscribe or submit to xemacs-patches, but all submissions are reviewed by the list moderator before they are distributed to the list. Discussion is not appropriate on xemacs-patches. To subscribe to xemacs-patches, send an email message to xemacs-patches-request(a)xemacs.org with `subscribe' (without the quotes) as the BODY of the message. ------- Forwarded Message Date: 02 May 1998 02:52:03 +0200 From: Hrvoje Niksic <hniksic(a)srce.hr> To: XEmacs Admin <xemacs-admin(a)xemacs.org>, XEmacs Beta List <xemacs-beta(a)xemacs.org> Subject: Change in patches approval process In order to achieve greater efficiency and spread the maintainership load, the XEmacs development team has decided to formalize the process of approving patches. If you have a patch that you would like applied to the XEmacs distribution, you should mail it to <xemacs-patches(a)xemacs.org>. The patches review board will look at your patch and approve or reject it (informing you of either decision). A rejection will always be accompanied by the rationale written by the board member who vetoed the patch. Rejected patches may be modified and resubmitted for re-evaluation. People interested in tracking the patches can subscribe to the patches list by mailing to <xemacs-patches-request(a)xemacs.org>. This list is moderated, and serves *only* for sending patches. Discussion on this list will not be allowed -- that is what xemacs-beta is for. The patches review board are, in alphabetical order: * Steve Baur <steve(a)xemacs.org> * Martin Buchholz <martin(a)xemacs.org> * Olivier Galibert <galibert(a)pobox.com> * P. E. Jareth Hein <jareth(a)camelot-soft.com> * Kyle Jones <kyle_jones(a)wonderworks.com> * Kirill M. Katsnelson <kkm(a)kis.ru> * Hrvoje Niksic <hniksic(a)srce.hr> * Andy Piper <andyp(a)parallax.co.uk> * Michael Sperber [Mr. Preprocessor] <sperber(a)informatik.uni-tuebingen.de> - -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia - --------------------------------+-------------------------------- Speak softly and carry a +6 two-handed sword. ------- End of Forwarded Message

1 participants
0 comments

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

XEmacs-Beta May 1998