April 1998 - XEmacs-Beta - XEmacs Mailing List Archives

[Success] XEmacs 21.0-b38-pre2 on Linux 26 years, 8 months

Kazuyoshi Furutaka

[i686-GNU-linux] Source : patched up from 21.0 beta37 Patch : patch 2.4 Make : GNU Make version 3.76.1 CC : pgcc-2.90.27 980315 (egcs-1.0.2 release) OS : Linux 2.0.33 (RedHat 5.0) X : X11R6.3 (Accelerated-X ver.4.1 w/ XFree86 3.3.1) gdb : GDB 4.16 [alpha-GNU-linux] Source : patched up from 21.0 beta37 Patch : Patch version 2.1 Make : GNU Make version 3.75 CC : egcs-2.90.23 980102 (egcs-1.0.1 release) OS : Linux 2.1.89 (StataboWare) X : X11R6.3 (XFree86 3.3.2) gdb : GDB 4.16 -- Kazuyoshi Furutaka furutaka(a)tokai.pnc.go.jp furutaka(a)jb3.so-net.ne.jp

1 participants
0 comments

Re: [Success without sgi's ifl] 21.0 "Repartida-pre1" XEmacs Lucid (beta38) on mips-sgi-irix6.2 26 years, 8 months

Martin Buchholz

>>>>> "Chr" == Christian Nybø <chr(a)mediascience.no> writes: Chr> In the man dir, I had to use gmake instead of sgi's make. Is it a Chr> goal of the XEmacs project to build with native cc's and make Chr> utilities, or is the object rather to breed a gnu generation of Chr> gcc/ecgs users? We'd like to support all makes, but the functionality specified by Posix is pretty weak. The construct in question is the use of % in make rules in man/Makefile. I think I'm to blame for this. My motivation at the time was that only developers should have to do a `make' in man. The XEmacs tarball would have pre-built info files, so there's nothing to do in man/. But I think later Steve made compilation in man a required part of every build. It could be fixed by making the `man' part of the build be error-resistant, or by rewriting man/Makefile for portability. Any volunteers? Martin

1 participants
0 comments

Re: Plea for minimal tagbits 26 years, 8 months

SL Baur

Olivier Galibert <galibert(a)pobox.com> writes: ... > And please Steve, at least when code freeze is enforced, settle for a > common set of options and enforce them in configure.in. By that reasoning, minimal tagbits is in, because I never want a binary without it on the architecture I do my development on. > I, for instance, have access to 7 different systems[1], 13 compilers > total. I won't try 16[2] different options combinations on each. So don't. Do the best you have time for. I would consider it sufficient to test configurations every option you can turn on are turned on, and a minimal configuration with tty support and *nothing* else. > [1] More if you count e.g. Irix 6.2, 6.4 and 6.5 as different. > [2] mule, indexed lrecord, minimal tagbits, union type. I may have > missed something. Double the number for each option. No one is expected to test both Mule and non-Mule, pick one. `indexed lrecord' should not be required for a working XEmacs binary, I'd prefer testing done without it at this point. `minimal tagbits' should not be set -- it should be set by configure. `union type' is a developers option and not expected to be used by end-users. --More-- ?

1 participants
0 comments

[Failure] 21.0 "Repartida-pre1" XEmacs Lucid (beta38) on sparc-sun-solaris2.6 26 years, 8 months

Gunnar Evermann

beta38-pre1 works if I compile without workshop support (see build-report below) If I compile --with-workshop xemacs crashes (see Lisp/C backtraces this looks very similar to the crash George reported in his bleeding edge OS/cc environment) If I start the xemacs-with-workshop using 'xemacs -nw' it seems to work fine (it complains about the missing pending-del but behaves quite normal). Hrvoje, I'm afraid I didn't understand your comment to George about 'pobj (?)'. If you could provide more detailed instructions for a novice debugger user, I'd be glad to help. Gunnar > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /data/source/gunnar/xemacs-20/Installation: > (Output from most recent run of ./configure) uname -a: SunOS nats7 5.6 Generic_105181-04 sun4u sparc SUNW,Ultra-1 ./configure '--gung-ho' '--compiler=cc' '--site-prefixes=/opt' '-cflags=-v -g' '--package-path=/data/source/gunnar/xemacs/packages' XEmacs 21.0-b38 "Repartida-pre1" configured for `sparc-sun-solaris2.6'. Where should the build process find the source code? /data/source/gunnar/xemacs-20 What installation prefix should install use? /usr/local What operating system and machine description files should XEmacs use? `s/sol2.h' and `m/sparc.h' What compiler should XEmacs be built with? cc -v -g 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 /usr/X11/include Where do we find X Windows libraries? /usr/dt/lib /usr/openwin/lib Additional prefixes: /opt Runtime library search path: /opt/lib:/usr/dt/lib:/usr/openwin/lib:/opt/SUNWdt/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 native sound support. Compiling in support for GNU DBM. Compiling in support for ncurses. Compiling in support for CDE. Compiling in support for ToolTalk. Compiling in support for OffiX. Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Motif dialog boxes. Compiling in DLL support. 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: --------------------------------------------------------- > Contents of /data/source/gunnar/xemacs-20/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\|/data/source/gunnar/xemacs-20/lisp/[^ ]+ hides " core temacs.exe puresize-adjust.h sheap-adjust.h Resetting `src/puresize-adjust.h'. "/data/source/gunnar/xemacs-20/lib-src/gnuserv.c", line 912: warning: statement not reached "fileio.c", line 749: warning: statement not reached "print.c", line 1465: warning: /* encountered inside a comment Purespace usage: 775720 of 1524300 (51% -- 731k wasted). XEmacs: Pure size adjusted, Don't Panic! I will restart the `make' *** Error code 1 (ignored) Purespace usage: 775720 of 775720 (100%). ---------------------------------------------------------------------- xemacs -vanilla Lisp backtrace follows: # bind (print-message-label) display-error((wrong-type-argument stringp Illegal Instruction (core dumped) C backtrace: program terminated by signal ILL (illegal opcode) Current function is print_internal 1203 (obj, printcharfun, escapeflag)); (dbx) where [1] 0x4b0280(0x5c9524, 0x5d21e0, 0x1, 0xefffda6c, 0x13, 0x0), at 0x4b027f =>[2] print_internal(obj = 6067492, printcharfun = 6103520, escapeflag = 1), line 1203 in "print.c" [3] print_cons(obj = 7307436, printcharfun = 6103520, escapeflag = 1), line 904 in "print.c" [4] print_internal(obj = 7307496, printcharfun = 6103520, escapeflag = 1), line 1203 in "print.c" [5] Fprin1(object = 7307496, stream = 6103520), line 502 in "print.c" [6] Fbacktrace(stream = 6103520, detailed = 5992480), line 4927 in "eval.c" [7] fatal_error_signal(sig = 4), line 243 in "emacs.c" ---- called from signal handler with signal 4 (SIGILL) ------ [8] 0x4b0280(), at 0x4b027f [9] Fprin1(object = 6067492, stream = 5992480), line 502 in "print.c" [10] print_error_message(error_object = 7307496, stream = 5992480), line 669 in "print.c" [11] Fdisplay_error(error_object = 7307496, stream = 5992480), line 700 in "print.c" [12] funcall_recording_as(recorded_as = 6103268, nargs = 2, args = 0xefffe7c0), line 3197 in "eval.c" [13] Ffuncall(nargs = 3, args = 0xefffe7c0), line 3238 in "eval.c" [14] Fbyte_code(bytestr = 5073856, vector = 5073996, maxdepth = 11), line 416 in "bytecode.c" [15] funcall_lambda(fun = 5074200, nargs = 1, arg_vector = 0xefffeb54), line 3599 in "eval.c" [16] funcall_recording_as(recorded_as = 6070724, nargs = 1, args = 0xefffeb50), line 3200 in "eval.c" [17] Ffuncall(nargs = 2, args = 0xefffeb50), line 3238 in "eval.c" [18] call1(fn = 6070724, arg0 = 7307496), line 3912 in "eval.c" [19] cmd_error(data = 7307496, dummy = 5992452), line 195 in "cmdloop.c" [20] condition_case_1(handlers = 5992564, bfun = 0x1004f0 = &Feval(Lisp_Object form), barg = 6498668, hfun = 0xa5690 = &`xemacs`cmdloop.c`cmd_error(Lisp_Object data, Lisp_Object dummy), harg = 5992452), line 1636 in "eval.c" [21] top_level_1(dummy = 5992452), line 206 in "cmdloop.c" [22] internal_catch(tag = 6070780, func = 0xa5770 = &`xemacs`cmdloop.c`top_level_1(Lisp_Object dummy), arg = 5992452, threw = (nil)), line 1328 in "eval.c" [23] initial_command_loop(load_me = 5992452), line 285 in "cmdloop.c" [24] xemacs_21_0_b38_sparc_sun_solaris2_6(argc = 2, argv = 0xefffeff4, envp = 0xeffff000, restart = 0), line 1672 in "emacs.c" [25] main(argc = 2, argv = 0xefffeff4, envp = 0xeffff000), line 2089 in "emacs.c" (dbx)

2 participants
1 comments

[OK] 21.0 "Repartida-pre2" XEmacs Lucid (beta38) on i686-pc-linux 26 years, 8 months

Tetsuya HOYANO

Patched up from beta37 and steve's fix against `make install'[1]. works fine and PNG image handling just works good too. --HOYANO > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /home2/beta/xemacs-21.0-beta/Installation: > (Output from most recent run of ./configure)

1 participants
0 comments

[PATCH] center-to-window-line 26 years, 8 months

Hrvoje Niksic

I don't know how about you, but for me it's terribly annoying that C-l redisplays the frame (I often use C-l to recenter the point). After thinking about it for a while, I realized that under X I've *never* really needed the "redisplay" side-effect of C-l. This patch creates a new function `center-to-window-line' (analogous to `move-to-window-line'), and makes `recenter' use that internally. The advantage is that you can, if you desire, bind C-l to this new function and avoid the redisplay flicker. 1998-04-30 Hrvoje Niksic <hniksic(a)srce.hr> * window.c (Fcenter_to_window_line): New function. (Frecenter): Use it. --- etc/NEWS.orig Thu Apr 30 04:38:19 1998 +++ etc/NEWS Thu Apr 30 04:39:50 1998 ＠＠ -50,6 +50,9 ＠＠ (setq echo-keystrokes 0.1) +** The new command `center-to-window-line' works like `recenter' +(bound to `C-l'), only it does not redisplay the whole display area. + ** The `M-.' command will now first search through exact tags matches, and then through inexact matches, as one would expect. --- src/window.c.orig Thu Apr 30 04:03:19 1998 +++ src/window.c Thu Apr 30 04:52:48 1998 ＠＠ -1371,9 +1371,8 ＠＠ */ (window)) { - struct window *w; + struct window *w = decode_window (window); - w = decode_window (window); return (WINDOW_HAS_MODELINE_P (w)) ? make_int (w->modeline_hscroll) : Qnil; } ＠＠ -1384,12 +1383,11 ＠＠ */ (window, ncol)) { - struct window *w; - int ncols; + struct window *w = decode_window (window); - w = decode_window (window); if (WINDOW_HAS_MODELINE_P (w)) { + int ncols; CHECK_INT (ncol); ncols = XINT (ncol); if (ncols < 0) ncols = 0; ＠＠ -4188,47 +4186,24 ＠＠ return Fset_window_hscroll (window, make_int (w->hscroll - XINT (arg))); } -DEFUN ("recenter", Frecenter, 0, 2, "_P", /* -Center point in WINDOW and redisplay frame. With N, put point on line N. +DEFUN ("center-to-window-line", Fcenter_to_window_line, 0, 2, "_P", /* +Center point in WINDOW. With N, put point on line N. The desired position of point is always relative to the window. -Just C-u as prefix means put point in the center of the window. -No N (i.e., it is nil) erases the entire frame and then -redraws with point in the center of the window. If WINDOW is nil, the selected window is used. */ (n, window)) { - struct window *w; - struct buffer *b; + struct window *w = decode_window (window); + struct buffer *b = XBUFFER (w->buffer); + Bufpos opoint = BUF_PT (b); Bufpos startp; - Bufpos opoint; - if (NILP (window)) - window = Fselected_window (Qnil); - else - CHECK_WINDOW (window); - w = XWINDOW (window); - b = XBUFFER (w->buffer); - - opoint = BUF_PT (b); - - if (LISTP (n)) - { - struct frame *f = XFRAME (w->frame); - - if (NILP (n)) - { - MARK_FRAME_CHANGED (f); - SET_FRAME_CLEAR (f); - } - - startp = start_with_line_at_pixpos (w, opoint, window_half_pixpos (w)); - } + if (NILP (n)) + startp = start_with_line_at_pixpos (w, opoint, window_half_pixpos (w)); else { n = Fprefix_numeric_value (n); CHECK_INT (n); - startp = start_with_point_on_display_line (w, opoint, XINT (n)); } ＠＠ -4239,6 +4214,29 ＠＠ MARK_WINDOWS_CHANGED (w); return Qnil; } + +DEFUN ("recenter", Frecenter, 0, 2, "_P", /* +Center point in WINDOW and redisplay frame. With N, put point on line N. +The desired position of point is always relative to the window. +Just C-u as prefix means put point in the center of the window. +No N (i.e., it is nil) erases the entire frame and then +redraws with point in the center of the window. +If WINDOW is nil, the selected window is used. +*/ + (n, window)) +{ + if (NILP (n)) + { + struct frame *f = XFRAME (decode_window (window)->frame); + MARK_FRAME_CHANGED (f); + SET_FRAME_CLEAR (f); + } + else if (CONSP (n)) + n = Qnil; + Fcenter_to_window_line (n, window); + return Qnil; +} + DEFUN ("move-to-window-line", Fmove_to_window_line, 1, 2, "_P", /* Position point relative to WINDOW. ＠＠ -4255,6 +4253,8 ＠＠ Bufpos start, new_point; int selected; + /* Don't use decode_window() because we need the new value of + WINDOW. */ if (NILP (window)) window = Fselected_window (Qnil); else ＠＠ -5568,6 +5568,7 ＠＠ DEFSUBR (Fscroll_right); DEFSUBR (Fother_window_for_scrolling); DEFSUBR (Fscroll_other_window); + DEFSUBR (Fcenter_to_window_line); DEFSUBR (Frecenter); DEFSUBR (Fmove_to_window_line); #ifdef MEMORY_USAGE_STATS -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- A radioactive cat has eighteen half-lives.

2 participants
1 comments

device-type: #<EMACS BUG: ILLEGAL DATATYPE 26 years, 8 months

Didier Verna

* gdb xemacs * break Fmake_device * run -vanilla Breakpoint 1, Fmake_device (type=-268435457, connection=-1606340604, props=-1606340604) at device.c:504 * call debug_print (type) #<EMACS BUG: ILLEGAL DATATYPE (#o 7) Save your buffers immediately and please report this bug> What's going on ? Martin, any idea ? My configure line is: '--prefix=/inf/metheny' '--site-prefixes=/inf/metheny' '--with-gnu-make' '--with-mule' -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / E.N.S.T. INF C214 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 80 72 75634 Paris cedex 13 Fax. (33) 01 45 81 31 19

2 participants
1 comments

Re: giflib, what version and WHERE? 26 years, 8 months

SL Baur

Hrvoje Niksic <hniksic(a)srce.hr> writes: > jareth(a)camelot-soft.com (P. E. Jareth Hein) writes: >> Jens Lautenbacher <jens(a)tellux.de> writes: >> >> > OK, it seems XEmacs wants version 3.1, but I've been unable to find >> > this somewhere... all I see are rpms for 3.04 or such... >> > >> > any pointers would be welcome.. >> >> giflib 3.1 is mine, but I'm getting cold feet... Unisys is apparently >> getting frisky (again) about enforcing patents, and my publicly >> releasing giflib sounds like I could be opening myself up for a world >> of hurt. > Why don't you release a giflib lite that knows only how to read GIFs, > not write them? Then you could wash your hands off the full version, > until the dust settles. I don't believe that resolves the patent problem. I also don't think it would matter if a copy of giflib got magically posted on Usenet via an anonymous remailer. Maybe now _is_ a good time to convert all our GIFs to PNGs. The (potential) lack of GIF support is going to hurt W3 though. XEmacs[1] is small-fry as things in the world go. We've always been in violation of US export laws[2] (crypto hooks/Mailcrypt), but have never been hassled about it. Footnotes: [1] And apparently FSF Emacs as well. [2] Well, depending upon _who_ is interpreting it _how_, today ... :-(

1 participants
0 comments

Re: Changing the package organization 26 years, 8 months

Oscar Figueiredo

>>>>> "Olivier" == Olivier Galibert <galibert(a)pobox.com> writes: Olivier> As of today, package-1.0.tar.gz unpacks into: Olivier> lisp/package Olivier> etc/package Olivier> info/ Olivier> What you you think about having instead: Olivier> package/lisp Olivier> package/etc Olivier> package/info Olivier> Pros: Olivier> - One can easily remove/upgrade a package by hand even if some files Olivier> dissepeared without any special tool, even if we add other Olivier> directories along the way Olivier> - We can stop recursively searching for packages as soon as we find Olivier> one of the {lisp,etc,info} directories Olivier> Cons: Olivier> - info files won't be in one directory anymore. Can our dir Olivier> regereating code handle three doxen different directories ? Aside from the dir autogeneration, the whole info structure is based on the existence of dir files in *a few* directories containing *many* info files. Your change leads to an important change of the concept and hence of the code. A workaround could be to create a single dir file at the root of the packages tree containing entries such as: * MyPackage: (mypackage/info/mypackage). My own package But this would add extra clutter to the Info menu. A second option could be maintaining two sets of info directories: one to search for dir files and the other one look for the info files themselves. One would include the package root in the first one only and maintain a single dir file there. Oscar

1 participants
0 comments

[Success] 21.0 "Repartida-pre2" XEmacs Lucid (beta38) on i586-pc-linux 26 years, 8 months

Kai Haberzettl

No problems. > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /usr/src/packages/xemacs/xemacs-21.0-b35/Installation: > (Output from most recent run of ./configure)

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 April 1998