July 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: [OK] 21.2 (beta18) "Toshima" XEmacs Lucid on i386-unknown-freebsd3.2 25 years, 4 months

Kai Haberzettl

SL Baur <steve(a)xemacs.org> writes: [...] > Yours is the first Unix build report sans-Mule that is a success. Here's another one. No problems. gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release) glibc 2.0.7pre6 uname -a: Linux zaphod 2.2.10 #19 Tue Jul 13 20:01:02 CEST 1999 i586 unknown ./configure '--cflags=-mpentium -O4' '--with-toolbars=no' '--with-mule=no' '--with-offix=yes' '--with-scrollbars=motif' '--with-dialogs=motif' '--prefix=/opt/xemacs' XEmacs 21.2-b18 "Toshima" configured for `i586-pc-linux'. Where should the build process find the source code? /home/khaberz/sources/xemacs/xemacs-beta/xemacs What installation prefix should install use? /opt/xemacs 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 -mpentium -O4 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 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 support for OffiX. Compiling in EXPERIMENTAL support for Drag'n'Drop ( OffiX ). Compiling in support for proper WM_COMMAND handling. Using Lucid menubars. Using Motif scrollbars. Using Motif dialog boxes. Compiling in DLL support. movemail will use "dot-locking" for locking mail spool files. Compiling in extra code for debugging. 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

Re: Doc string patch for XEmacs/InfoDock. 25 years, 4 months

SL Baur

I agree. Comments? Bob Weiner <weiner(a)altrasoft.com> writes: >> It would be really nice if format-time-string could take this format >> (date in seconds since 1970) as an input and output a formatted date >> from it. > Said another way, the emacs_strftime should be converted to a Lisp subr and > the system type `time_t' should be made into a Lisp type with easy back and > forth conversion operators where needed. Then we'd have pretty much native > UNIX time handling. Right now, I can't see a clear way to convert a given > UNIX time to a formatted date. > Bob -- 頭隠して尻隠さず

3 participants
2 comments

Re: XEmacs 21.1.4 (Arches) is released 25 years, 4 months

Karl M. Hegbloom

:-)

1 participants
0 comments

Packages under WinNT 25 years, 4 months

Damon Lipparelli

I'm trying to figure out what should work with respect to updating packages under WinNT (native). Is this supposed to work? Without messing with efs-tmp-name-template, I'm able to update the package list. But, when a new package file is pulled down there appears to be a problem with how temporary file names are generated. For example, when I try to update APEL to version 1.13, the file apel-1.13-pkg.tar.gz is pulled down, but rather than being put into "C:\TEMP\apel-1.13-pkg.tar.gz", a file called "C:\TEMPapel-1.13-pkg.tar.gz" is created; package update fails pretty quickly with that. Is this a problem in EFS? A problem with how names are concatenated together under the native WinNT build? A problem in my configuration? Thanks for any info, -lipp

1 participants
0 comments

Re: [success] 21.2.18 25 years, 4 months

Karl Kleinpaste

nbecker(a)fred.net writes: > I forget - how am I supposed to create and mail these reports? M-x load-library RET build-report RET M-x build-report RET

1 participants
0 comments

[success] 21.2.18 25 years, 4 months

Neal D. Becker

I forget - how am I supposed to create and mail these reports? uname -a: Linux nbeckerpc.hns.com 2.2.10 #14 Wed Jul 7 08:45:55 EDT 1999 i686 unknown ../../xemacs-21/configure '--error-checking=none' XEmacs 21.2-b18 "Toshima" configured for `i686-pc-linux'. Where should the build process find the source code? /usr/local/src/xemacs-21 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/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 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 ncurses. Compiling in support for GPM (General Purpose Mouse). Compiling in support for proper WM_COMMAND handling. Using Lucid menubars. Using Lucid scrollbars. Using Motif dialog boxes. Compiling in DLL support. movemail will use "dot-locking" for locking mail spool files. Compiling in extra code for debugging.

1 participants
0 comments

Re: New package system design draft 25 years, 4 months

Jan Vroonhof

Didier Verna <verna(a)inf.enst.fr> writes: > Because, as I've already explained, I already have network-ally shared > standard directories, that your design won't use and it's a shame because I > would have to make the concerned packages directories sharable by hand (or > script) each time a new package appears. Why are share/.../lib-src/<system type>/.. directories not shareable. You need more space on the server and you cannot have your usr/share file system mounted noexec, but apart from that? Jan

1 participants
0 comments

Re: XEmacs 21.2.18 -- "$BK-Eg(B" is released 25 years, 4 months

Tor Arntsen

On Jul 14, 16:14, Colin Rafferty wrote: >Good point. > >So I have no control over cvs at my job. Do you happen to know how I >can change the port from the command line (or .cvsrc or .cvspass or ...)? You can't if you have a standard cvs, it's hardcoded (so somebody changed a #define and recompiled cvs if it's using 2410 instead of 2401). There are patches around which will let you define other ports as part of CVS/Root or -d<repository> strings, but that won't help you unless the cvs at your job are using those patches (the syntax also depends on exactly which patches are used). What you probably *could* do is to make a simple proxy (perlscript or something) that will accept 2410 on localhost and redirect to 2401 on cvs.xemacs.org, and then use cvs -d localhost:/<etc> -Tor

1 participants
0 comments

Re: New package system design draft 25 years, 4 months

Didier Verna

sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) writes: > dv> [...] You'd understood that it doesn't fit mine. > > Ah! No, I hadn't. Please explain why. Because, as I've already explained, I already have network-ally shared standard directories, that your design won't use and it's a shame because I would have to make the concerned packages directories sharable by hand (or script) each time a new package appears. > I don't even see your problem yet. See above. > Moreover (and please acknowledge this, Didier), there are software yes > setups *other* than yours (notably, ours) where hard-wiring what > you're suggesting is going to royally fuck things up. Please explain precisely why and how. > Once the package is spread out as you suggest, installation is still > easy enough, but suddenly, if I want to uninstall or move or ship a > package, I have to remember where all its bits are. You told me to use scripts to make my links, so I tell you to use scripts to uninstall. Moreover, remembering to look in *two* places, like share/ and lib/, is not that much to remember I think. > Seriously, links *are* Unix's native mechanism for expressing sharing. > You may not like it, but it's the only thing there is. There are NFS, automount ... > dv> But please, don't say things like "I won't change it". > > I never said that. How come you claim this? First paragraph, 6th line of your message ;-) : <y9ld7xvhfem.fsf(a)brabantio.informatik.uni-tuebingen.de>. But I've just reread it, and I might have misinterpreted it: you were probably talking about your system setup, not the package design, sorry... -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / ENST, INFRES C201.1 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. +33 (1) 45 81 73 46 75013 Paris, France Fax. +33 (1) 45 81 31 19

1 participants
0 comments

21.2.18 SEGV failure -- null frame pointer 25 years, 4 months

Karl Kleinpaste

21.2.18 built and installed fine under Linux, but I've gotten a couple of these this morning already. I always attach gdb to my XEmacs which runs Gnus. I have the core, but the core's stack (being post- continuation after death-dealing signal) shows only the final __kill() and fatal_error_signal() stack frames. Thoughts on what might be wrong here? Program received signal SIGSEGV, Segmentation fault. x_to_emacs_keysym (event=0x7ffff528, simple_p=0) at frame.h:248 248 assert (EQ (FRAME_TYPE (f), sym)); (gdb) bt #0 x_to_emacs_keysym (event=0x7ffff528, simple_p=0) at frame.h:248 #1 0x81a9468 in x_event_to_emacs_event (x_event=0x7ffff528, emacs_event=0x8be9ad4) at event-Xt.c:999 #2 0x81ab6c7 in emacs_Xt_event_handler (wid=0x85a0718, closure=0x0, event=0x7ffff528, continue_to_dispatch=0x7ffff463 "\001pö1\b,") at event-Xt.c:2472 #3 0x2ab9cc9f in XtDispatchEventToWidget () #4 0x2ab9d6fd in _XtDefaultDispatcher () #5 0x2ab9d975 in XtDispatchEvent () #6 0x2aba83d5 in XtAppProcessEvent () #7 0x81abe33 in emacs_Xt_event_pending_p (user_p=1) at event-Xt.c:2628 #8 0x80d954d in detect_input_pending () at event-stream.c:945 #9 0x80dba9d in Fnext_event (event=142911672, prompt=137112340) at event-stream.c:2237 #10 0x807330e in Fcommand_loop_1 () at cmdloop.c:569 #11 0x807309d in command_loop_1 (dummy=137112340) at cmdloop.c:493 #12 0x8091741 in condition_case_1 (handlers=137112436, bfun=0x807304c <command_loop_1>, barg=137112340, hfun=0x80724d0 <cmd_error>, harg=137112340) at eval.c:1640 #13 0x8073538 in command_loop_2 (dummy=137112340) at cmdloop.c:255 #14 0x809131c in internal_catch (tag=137186628, func=0x8073504 <command_loop_2>, arg=137112340, threw=0x0) at eval.c:1315 #15 0x8072937 in initial_command_loop (load_me=137112340) at cmdloop.c:304 #16 0x808cf5d in xemacs_21_2_b18_i686_pc_linux (argc=5, argv=0x7ffff9b4, envp=0x7ffff9cc, restart=0) at emacs.c:1759 #17 0x808d6e9 in main (argc=5, argv=0x7ffff9b4, envp=0x7ffff9cc) at emacs.c:2184 (gdb) list 243 INLINE struct frame * 244 error_check_frame_type (struct frame * f, Lisp_Object sym); 245 INLINE struct frame * 246 error_check_frame_type (struct frame * f, Lisp_Object sym) 247 { 248 assert (EQ (FRAME_TYPE (f), sym)); 249 return f; 250 } 251 # define FRAME_TYPE_DATA(f, type) \ 252 ((struct type##_frame *) (error_check_frame_type (f, Q##type))->frame_data) (gdb) p f $1 = (struct frame *) 0x0 System is RedHat 5.2. Installation file: uname -a: Linux beaver.jprc.com 2.2.10-ac10 #1 SMP Tue Jul 13 13:23:27 EDT 1999 i686 unknown ./configure '--with-pop' '--with-mule' '--with-png' XEmacs 21.2-b18 "Toshima" configured for `i686-pc-linux'. Where should the build process find the source code? /home/karl/src/x/xemacs-21/xemacs-21.2.18 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/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 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 WM_COMMAND handling. 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. Compiling in extra code for debugging. 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

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