January 1999 - XEmacs-Beta - XEmacs Mailing List Archives

dhawkins＠rmas.com

Thanks for the great work on xemacs! I have hit this bug and hope that this bug report will be helpful. Again, keep up the great work! This bug report will be sent to the XEmacs Development Team, not to your local site managers!! Please write in English, because the XEmacs maintainers do not have translators to read other languages for them. In XEmacs 21.2 "Artemis" [Lucid] (i586-pc-linux) of Sat Jan 2 1999 on gollum.rmas.com Please describe exactly what actions triggered the bug and the precise symptoms of the bug: M-x doctor Recent keystrokes: C-x b RET C-x 1 button2 button2up button2 button2up button2 button2up button2 button2up C-x m misc-use r Recent messages (most recent first): Loading emacsbug...done Loading emacsbug... Type C-c C-x C-z to exit MIME mode, and type C-c C-x ? to get help. Parsing BBDB... (frobnicating...done) Parsing BBDB... (frobnicating...) Parsing BBDB... (reading...) Parsing BBDB... Loading bbdb-hooks...done Loading bbdb-hooks... Loading gnus-xmas...done Other useful information: bash$ xemacs & [1] 2208 bash$ Fatal error: assertion failed, file bytecode.c, line 532, specpdl_ptr->func == 0 Fatal error (6). Your files have been auto-saved. Use `M-x recover-session' to recover them. Please report this bug by running the send-pr script included with XEmacs, or selecting `Send Bug Report' from the help menu. As a last resort send ordinary email to `crashes(a)xemacs.org'. *MAKE SURE* to include the information in the command M-x describe-installation. If at all possible, *please* try to obtain a C stack backtrace; it will help us immensely in determining what went wrong. To do this, locate the core file that was produced as a result of this crash (it's usually called `core' and is located in the directory in which you started the editor, or maybe in your home directory), and type gdb /usr/local/bin/xemacs core then type `where' when the debugger prompt comes up. (If you don't have GDB on your system, you might have DBX, or XDB, or SDB. A similar procedure should work for all of these. Ask your system administrator if you need more help.) Lisp backtrace follows: doctor-make-string(i) # bind (word) doctor-type-symbol(i) mapcar(doctor-type-symbol (i am the psychotherapist \. please\, describe your problems \. each time you are finished talking\, type RET twice \.)) # bind (ans) doctor-txtype((i am the psychotherapist \. please\, describe your problems \. each time you are finished talking\, type RET twice \.)) # bind (x) doctor-type((i am the psychotherapist \. ($ please) ($ describe) your ($ problems) \. each time you are finished talking\, type RET twice \.)) doctor-mode() #<compiled-function nil "...(7)" [switch-to-buffer "*doctor*" doctor-mode] 2 ("/usr/local/lib/xemacs/xemacs-packages/man/lisp/misc-games/doctor.elc" . 17513) nil>() call-interactively(doctor) command-execute(doctor t) # bind (_execute_command_keys_ _execute_command_name_ prefix-arg) execute-extended-command(nil) # bind (command-debug-status) call-interactively(execute-extended-command) # (condition-case ... . error) # (catch top-level ...) [1]+ Aborted (core dumped) xemacs bash$ gdb /usr/local/bin/xemacs core GNU gdb 4.17.0.4 with Linux/x86 hardware watchpoint and FPU support Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux"... Core was generated by `xemacs'. Program terminated with signal 6, Aborted. Reading symbols from /usr/X11R6/lib/libXm.so.1...done. Reading symbols from /usr/lib/libtiff.so.3...done. Reading symbols from /usr/lib/libjpeg.so.62...done. Reading symbols from /usr/lib/libz.so.1...done. Reading symbols from /usr/X11R6/lib/libXpm.so.4...done. Reading symbols from /usr/X11R6/lib/libXmu.so.6...done. Reading symbols from /usr/X11R6/lib/libXt.so.6...done. Reading symbols from /usr/X11R6/lib/libXext.so.6...done. Reading symbols from /usr/X11R6/lib/libX11.so.6...done. Reading symbols from /usr/X11R6/lib/libSM.so.6...done. Reading symbols from /usr/X11R6/lib/libICE.so.6...done. Reading symbols from /lib/libdl.so.2...done. Reading symbols from /lib/libdb.so.3...done. Reading symbols from /usr/lib/libgpm.so.1...done. Reading symbols from /usr/lib/libncurses.so.4...done. Reading symbols from /lib/libm.so.6...done. Reading symbols from /lib/libc.so.6...done. Reading symbols from /lib/ld-linux.so.2...done. Reading symbols from /lib/libnss_files.so.2...done. #0 0x403b56e1 in __kill () (gdb) where #0 0x403b56e1 in __kill () #1 0x80b59e1 in fatal_error_signal (sig=6) at emacs.c:264 #2 <signal handler called> #3 0x4004a400 in XmCreateCascadeButton () #4 0x403b6983 in abort () at ../sysdeps/generic/abort.c:88 #5 0x80b5947 in assert_failed () at emacs.c:2631 #6 0x808f74e in funcall_compiled_function (fun=141122028, nargs=1, args=0xbfffe750) at bytecode.c:532 #7 0x80bb7b3 in Ffuncall (nargs=2, args=0xbfffe74c) at eval.c:3221 #8 0x808fb39 in execute_optimized_program ( program=0x86a952c "=c0\t!\211\021=c2\230=ab\003=c3\021\f=ab\f=c5\t!\021\016\006=ab\004=c7c\210=c8=c9\t\"=ac\005\016\006=ac\006\tc\210=aa\006=ca\t=b1\002\210\016\013=ab\013i\016\fV=ab\005\016\013 \210=c8=cd\t\"\024=ce\211\026\006\207=baA\b1", stack_depth=4, constants_data=0x83e7100) at bytecode.c:750 #9 0x808f709 in funcall_compiled_function (fun=141121972, nargs=1, args=0xbfffe85c) at bytecode.c:530 #10 0x80bb7b3 in Ffuncall (nargs=2, args=0xbfffe858) at eval.c:3221 #11 0x8117489 in mapcar1 (leni=20, vals=0xbfffe884, fn=141191836, seq=140793788) at fns.c:3127 #12 0x811770b in Fmapcar (fn=141191836, seq=140793788) at fns.c:3209 #13 0x80bb760 in Ffuncall (nargs=3, args=0xbfffe95c) at eval.c:3206 #14 0x808fb39 in execute_optimized_program ( program=0x86a9504 "=c0\021=c2\023=c4=c5\016\006\"\210=c7c\207=baA\ba", stack_depth=3, constants_data=0x85e86e0) at bytecode.c:750 #15 0x808f709 in funcall_compiled_function (fun=141121944, nargs=1, args=0xbfffea5c) at bytecode.c:530 #16 0x80bb7b3 in Ffuncall (nargs=2, args=0xbfffea58) at eval.c:3221 #17 0x808fb39 in execute_optimized_program ( program=0x865e744 "=c0\t!\021=c2=c3\t!!\207", stack_depth=3, constants_data=0x86b7a60) at bytecode.c:750 #18 0x808f709 in funcall_compiled_function (fun=141121692, nargs=1, args=0xbfffeb58) at bytecode.c:530 #19 0x80bb7b3 in Ffuncall (nargs=2, args=0xbfffeb54) at eval.c:3221 #20 0x808fb39 in execute_optimized_program ( program=0x865e8fc "=c0 \210=c1 \210=c2\013!\210=c4\025=c6\026\a=c8 \210=c9=ca!\210=cbc\207s4\bls4\b1", stack_depth=2, constants_data=0x86b68c8) at bytecode.c:750 #21 0x808f709 in funcall_compiled_function (fun=141120628, nargs=0, args=0xbfffec50) at bytecode.c:530 #22 0x80bb7b3 in Ffuncall (nargs=1, args=0xbfffec4c) at eval.c:3221 #23 0x808fb39 in execute_optimized_program (program=0x8654d9c "=c0=c1!\210=c2 \207", stack_depth=2, constants_data=0x86a4be8) at bytecode.c:750 #24 0x808f709 in funcall_compiled_function (fun=141120768, nargs=0, args=0xbfffed60) at bytecode.c:530 #25 0x80bb7b3 in Ffuncall (nargs=1, args=0xbfffed5c) at eval.c:3221 #26 0x80bea40 in apply1 (fn=141120768, arg=137655148) at eval.c:3803 #27 0x80937d4 in Fcall_interactively (function=138493776, record_flag=137655176, keys=137655148) at callint.c:397 #28 0x80b9de4 in Fcommand_execute (cmd=138493776, record=137655176, keys=137655148) at eval.c:2623 #29 0x80bb66a in Ffuncall (nargs=3, args=0xbfffef9c) at eval.c:3189 #30 0x808fb39 in execute_optimized_program ( program=0x826c89c "\b\030=c1\b=c2a=ab\004=c3=aa$\b=c4k=ab\004=c5=aa\034\b=a8=ab\a=c6=c7\b\"=aa\022\b:=ab\r\b＠=a8=ab\b=c6=c7\b＠\"=aa\002=c8!\026\t)\016\n=ab=t=ab:=cb\016\t!\016\t\036\f\036\r=ce\016\t=cf\"\210\016\r=ad$=d0=d1!=ad\037=d2=d3=c6=d4\016\f\016\rA=ab\004=d5=aa\002=d6=d7\016\r!$\"\210=d0\016\030!\210=d9=d3!*\207=ce\016\t=cf\"\207=a0=c6/\b\020", stack_depth=8, constants_data=0x826c754) at bytecode.c:750 #31 0x808f709 in funcall_compiled_function (fun=136759036, nargs=1, args=0xbffff0b4) at bytecode.c:530 #32 0x80bb7b3 in Ffuncall (nargs=2, args=0xbffff0b0) at eval.c:3221 #33 0x80951ec in Fcall_interactively (function=138048716, record_flag=137655148, keys=137655148) at callint.c:949 #34 0x80b9de4 in Fcommand_execute (cmd=138048716, record=137655148, keys=137655148) at eval.c:2623 #35 0x80eee77 in execute_command_event (command_builder=0x84c3f58, event=141102772) at event-stream.c:4345 #36 0x80efc2e in Fdispatch_event (event=141102772) at event-stream.c:4684 #37 0x809ab30 in Fcommand_loop_1 () at cmdloop.c:578 #38 0x809ad75 in command_loop_1 (dummy=137655148) at cmdloop.c:493 #39 0x80b85ba in condition_case_1 (handlers=137655260, bfun=0x809ad28 <command_loop_1>, barg=137655148, hfun=0x8099cc0 <cmd_error>, harg=137655148) at eval.c:1640 #40 0x809ae4c in command_loop_2 (dummy=137655148) at cmdloop.c:255 #41 0x80bf49f in internal_catch (tag=137729884, func=0x809ae18 <command_loop_2>, arg=137655148, threw=0x0) at eval.c:1315 #42 0x809a181 in initial_command_loop (load_me=137655148) at cmdloop.c:304 #43 0x80b4095 in xemacs_21_2_b8_i586_pc_linux () at emacs.c:1718 #44 0x80b5bcf in main () at emacs.c:2147 #45 0x403af877 in __libc_start_main (main=0x80b5ad0 <main>, argc=1, argv=0xbffff634, init=0x807a370 <_init>, fini=0x81e0b30 <_fini>, rtld_fini=0x4000a710 <_dl_fini>, stack_end=0xbffff62c) at ../sysdeps/generic/libc-start.c:78

1 participants
0 comments

Spelling error - "separate" 25 years, 3 months

Charles G Waldman

The listing of packages displayed by package-admin contains the line: speedbar 1.10 1.10 Provides a seperate frame with convenient reference The word is "separate", not "seperate". I had this drilled into my head by elementary school teachers - I used to always misspell that word!

1 participants
0 comments

Distribution Build Report for XEmacs-21.0.62 25 years, 3 months

Steven Baur

Greetings XEmacs beta testers. I am in the process of building the next distribution of XEmacs 21.0. I have tested the attached configuration. Sincerely, The XEmacs Build 'Bot -- uname -a: BSD/OS camelot-soft.camelot-soft.com 3.0 BSDI BSD/OS 3.0 Kernel #0: Thu Jul 17 23:30:01 PDT 1997 root＠camelot-soft.camelot-soft.com:/usr/src/sys/compile/CAMELOT i386 ./configure '--prefix=/usr/home/steveb/staging' '--cflags=-O' '--with-mule' '--without-x11' '--debug=no' '--error-checking=none' XEmacs 21.0-b62 "Pyrenean" configured for `i386-pc-bsdi3.0'. Where should the build process find the source code? /usr/home/steveb/staging/xemacs-21.0 What installation prefix should install use? /usr/home/steveb/staging What operating system and machine description files should XEmacs use? `s/bsdos3.h' and `m/intel386.h' What compiler should XEmacs be built with? gcc -O Should XEmacs use the GNU version of malloc? yes Should XEmacs use the relocating allocator for buffers? yes What window system should XEmacs use? none Compiling in native sound support. Compiling in support for Berkeley DB. Compiling in support for GNU DBM. Compiling in Mule (multi-lingual) support. Compiling in DLL support. movemail will use "flock" for locking mail spool files.

1 participants
0 comments

Re: DLL stuff (BIG patch) 25 years, 3 months

Richard Coleman

> Attached is a rather large patch to 21.0.61 to support DLL loading. I > havent done changelog entries yet but this is pretty complete, even a > manual. This has the new ellcc compiler program, and a much more complete > and well defined interface. Modules are now 100% the same as built-in > code, so it should be easy to migrate stuff out of the dumped Emacs into > loadable modules. Please apply this (with -E to remove some empty files) > and try it out. I think this works pretty well. No doubt I will have to > polish things a little but I would really like to see this stuff in the > tree sooner rather than later so that people can get used to the idea, > and we can start thinking about which parts of the currently dumped > Emacs we want to turn into modules. It might make sense to make future patches against 21.2.8 (or 21.2.9 when Martin releases it), rather than 21.0.61? I doubt such a large change will make it into the 21.0 series this late into its development. I tried to use this patch on 21.2.8 and got several rejections. -- Richard Coleman coleman(a)math.gatech.edu

3 participants
2 comments

Re: DLL stuff (BIG patch) 25 years, 3 months

Hrvoje Niksic

"J. Kean Johnston" <jkj(a)sco.com> writes: > On Mon, Jan 04, 1999 at 09:33:33PM -0500, Richard Coleman wrote: > > It might make sense to make future patches against 21.2.8 (or 21.2.9 > > when Martin releases it), rather than 21.0.61? I doubt such a large > > change will make it into the 21.0 series this late into its > > development. > > I will make a diff (this time a unified diff) against 21.2.8 but I > *REALLY* think we should get this into 21.0 and any future releases > so that people get used to the idea. 21.0 has been in feature and code freeze for some time now. Adding this to 21.0 should be out of the question. > This technology can make a huge difference to the usefulness of > XEmacs, and delaying its inclusion serves little purpose. This has > been very well tested You cannot say that until you have a bunch of people banging on it. By delaying this for 21.2 you lose nothing -- 21.0 is not the last XEmacs release.

1 participants
0 comments

Re: DLL stuff (BIG patch) 25 years, 3 months

Richard Coleman

> Attached is a rather large patch to 21.0.61 to support DLL loading. I > havent done changelog entries yet but this is pretty complete, even a > manual. This has the new ellcc compiler program, and a much more complete > and well defined interface. Modules are now 100% the same as built-in > code, so it should be easy to migrate stuff out of the dumped Emacs into > loadable modules. Please apply this (with -E to remove some empty files) > and try it out. I think this works pretty well. No doubt I will have to > polish things a little but I would really like to see this stuff in the > tree sooner rather than later so that people can get used to the idea, > and we can start thinking about which parts of the currently dumped > Emacs we want to turn into modules. I just tried to build 21.0.61 (patched up from 21.0.60) which this DLL patch added, and I get the error message. gcc -I. -O2 -fno-caller-saves -Demacs -I../src -DHAVE_CONFIG_H -I/usr/local/include -I/home/rcoleman/xemacs/xemacs-21.0.60/lib-src -I/home/rcoleman/xemacs/xemacs-21.0.60/lib-src/../src -DVERSION='"21.0-b61"' /home/rcoleman/xemacs/xemacs-21.0.60/lib-src/ootags.c getopt.o getopt1.o regex.o -L/usr/local/lib -Xlinker -R/usr/local/lib -ltermcap -lkvm -lm -lutil -lxpg4 -o ootags make: don't know how to make ellcc.h. Stop *** Error code 2 I configured with ./configure '--prefix=/usr/local' '--site-includes=/usr/local/include' '--site-libraries=/usr/local/lib' '--cflags=-O2 -fno-caller-saves' '--debug=no' '--error-checking=no' '--gung-ho' -- Richard Coleman coleman(a)math.gatech.edu

2 participants
1 comments

SEGV core, -b8 25 years, 3 months

Karl Kleinpaste

Running pGnus 0.69 inside 21.2-b8 under X, I have gotten a couple of these errors. (gdb) bt #0 0x816035d in x_to_emacs_keysym (event=0xbffff298, simple_p=0) at event-Xt.c:782 #1 0x8160862 in x_event_to_emacs_event (x_event=0xbffff298, emacs_event=0x8947184) at event-Xt.c:997 #2 0x8161849 in emacs_Xt_event_handler (wid=0x830f550, closure=0x0, event=0xbffff298, continue_to_dispatch=0xbffff1d3 "\0018½D\b,") at event-Xt.c:2440 #3 0x400ee6dc in XtDispatchEventToWidget () #4 0x400eefbf in _XtDefaultDispatcher () #5 0x400ef1da in XtDispatchEvent () #6 0x400f8ab4 in XtAppProcessEvent () #7 0x8161caf in emacs_Xt_event_pending_p (user_p=1) at event-Xt.c:2596 #8 0x80d7cd9 in Fnext_event (event=145759552, prompt=137066236) at event-stream.c:945 #9 0x8091f99 in Fcommand_loop_1 () at cmdloop.c:569 #10 0x8091e3a in command_loop_1 (dummy=137066236) at cmdloop.c:493 #11 0x80a9cc9 in condition_case_1 (handlers=137066348, bfun=0x8091e24 <command_loop_1>, barg=137066236, hfun=0x8091a48 <cmd_error>, harg=137066236) at eval.c:1640 #12 0x80921c0 in command_loop_2 (dummy=137066236) at cmdloop.c:255 #13 0x80a9af4 in internal_catch (tag=137141252, func=0x809218c <command_loop_2>, arg=137066236, threw=0x0) at eval.c:1315 #14 0x8091c7e in initial_command_loop (load_me=137066236) at cmdloop.c:304 #15 0x80a6ff9 in xemacs_21_2_b8_i686_pc_linux (argc=5, argv=0xbffff714, envp=0xbffff72c, restart=0) at emacs.c:1718 #16 0x80a76c1 in main (argc=5, argv=0xbffff714, envp=0xbffff72c) at emacs.c:2147 That's the trace "as the error occurred," since I've taken at times lately to running 21.2 under gdb directly, in order to avoid trashed core files and whatnot. XEmacs 21.2 "Artemis" [Lucid] (i686-pc-linux, Mule) of Fri Jan 1 1999 on beaver.jprc.com uname -a: Linux beaver.jprc.com 2.1.131 #5 SMP Thu Dec 17 16:46:02 EST 1998 i686 unknown (RedHat 5.1, XFree 3.3.2.3-18) ./configure '--with-pop' '--with-mule' '--with-png' '--error-checking=none' '--debug=no' XEmacs 21.2-b8 "Artemis" configured for `i686-pc-linux'. Where should the build process find the source code? /home/karl/src/x/xemacs-21/xemacs-21.2.8 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 -O3 -Wall -Wno-switch 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 PNG image handling. Compiling in support for (builtin) GIF image handling. Compiling in support for JPEG image handling. Compiling in support for TIFF image handling. Compiling in support for X-Face message headers. 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. Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Athena dialog boxes. Compiling in DLL support. movemail will use "dot-locking" for locking mail spool files. Using POP for mail access. Using Lisp_Objects with minimal tagbits.

1 participants
0 comments

Building 21.0.60 on AIX 4.3.1 25 years, 3 months

David Kropman

Hi have had several problems compiling xemacs on AIX 4.3.1 I have many different versions. The most success I have is with the version above. I now have the following problem that I hope somone will give me some help on! Error: Fatal error: assertion failed, file EmacsFrame.c, line 383, RECORD_TYPEP (frame, lrecord_frame) || MARKED_RECORD_P (frame) Fatal error (6). Your files have been auto-saved. Use `M-x recover-session' to recover them. ---- later on screen Lisp backtrace follows: # bind (frame-being-created) make-frame(nil #<x-device on "172.16.4.235:0.0" 0x716>) frame-initialize() # bind (debugger debug-on-error command-line-args-left) command-line() # (unwind-protect ...) normal-top-level() # (condition-case ... . error) # (catch top-level ...) IOT/Abort trap(coredump) The output of configure below : uname -a: AIX neptune 3 4 004221874C00 configure '--site-includes=/usr/local/include' '--site-libraries=/usr/local/lib' '--cflags=-O - qmaxmem=-1' '--with-png' '--with-dragndrop=no' XEmacs 21.0-b60 "Poitou60" configured for `powerpc-ibm-aix4.3.1.0'. Where should the build process find the source code? /retek/temp/xemacs-21.0.60 What installation prefix should install use? /usr/local What operating system and machine description files should XEmacs use? `s/aix4-2.h' and `m/ibmrs6000.h' What compiler should XEmacs be built with? cc_r -O -qmaxmem=-1 Should XEmacs use the GNU version of malloc? yes 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/dt/include Where do we find X Windows libraries? /usr/dt/lib Additional header files: /usr/local/include Additional libraries: /usr/local/lib Compiling in support for XAUTH. No Xmu; substituting equivalent routines. Compiling in support for XPM images. Compiling in support for PNG image handling. Compiling in support for (builtin) GIF image handling. Compiling in support for GNU DBM. Compiling in support for ToolTalk. Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Motif dialog boxes. Compiling in DLL support. movemail will use "lockf" for locking mail spool files. 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: --------------------------------------------------------- Please help as since we have updated to AIX 4.3.1 I have not had Xemacs!!! Thanks -- ****************************************************************************** The use of the Truworths e-mail facility is not permitted for the distribution of chain letters or offensive email of any nature whatsoever. Truworths hereby distances itself from and accepts no liability in respect of the unauthorised use of its e-mail facility or the sending of e-mail communications for other than strictly business purposes. Truworths furthermore disclaims liability for any unauthorised instruction for which permission was not granted. Any recipient of an unacceptable communication, a chain letter or offensive material of any nature is requested to report it to abuse(a)truworths.co.za

1 participants
0 comments

Re: xemacs & redhat 25 years, 3 months

Stig Bjorlykke

kifer(a)cs.sunysb.edu (Michael Kifer) writes: | [...] I remember that I also had problems with installing | the xemacs rpm because of the conflict with the gnuserv rpm. | This conflict might be turning off other potential users. I think I am responsible for most of the rpm's available for XEmacs, because I made the rpm's available from ftp.xemacs.org, and I am the RHCN (RedHat Contrib|Net) maintainer for XEmacs. I have tried very hard to make it work on most RedHat systems, and the files I found in conflict with Emacs (or the ctags package) I moved to a separate rpm (xemacs-extras). I did not find any conflicts with gnuserv whatsoever... Another problem with making a rpm for XEmacs is all the libraries, because they change version each time RedHat comes with a new release (libpng changed from so.1 to so.0 to so.2), and most people does not want a totaly static xemacs binary. But if anyone have any ideas what could be done better I will gladly make some changes ;) (PS; I have not read this list for some time now, and may be outdated on some issues...) -- Stig Bjørlykke Linux user

1 participants
0 comments

Re: update mailcrypt? 25 years, 3 months

Karl Kleinpaste

nbecker(a)fred.net writes: > I'd like to see a newer mailcrypt. Both 3.4 and 3.5b7 are in the packages area at ftp://ftp.xemacs.org/pub/xemacs/packages/, but are not in the sumo tarball: mailcrypt-1.06-pkg.tar.gz 103 Kb Mon Oct 12 19:28:00 1998 Unix Tape Archive mailcryptng-1.01-pkg.tar.gz 117 Kb Mon Oct 12 19:28:00 1998 Unix Tape Archive On the other hand, updating 3.5b7 to the finalized release would be nice.

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 January 1999