August 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Neal D. Becker

>>>>> "P" == P E Jareth Hein <jareth(a)camelot.co.jp> writes: >>>>> "nbecker" == nbecker <nbecker(a)fred.net> writes: nbecker> I'm trying to build on i686-pc-linux-gnu RH5.1. It seems I nbecker> need libpng-1.0.2. nbecker> OK, I built libpng-1.0.2 modifying the makefile to build nbecker> share lib via libtool. nbecker> What to call the soname? I'm assuming that libpng-1.0.2 is nbecker> not binary compatible with 1.0.1. On RH5.1 libpng-1.0.2 is nbecker> called libpng-2.1.0 (I think that was actually my doing when nbecker> I put it into libgr, IIRC). P> 1.0.2 is binary compatible with what little testing I gave it. There P> are a couple of new functions/features, but the rest is bugfixes. nbecker> So I'm calling libpng-1.0.2 libpng-3.0.0. What do you think? P> I don't quite understand where your question comes from... The P> libpng-1.0.2 makefile should create for you a shared library with the P> soname of 2.1.0.2. If you look at the top of png.h, you will see the P> following: OK, I used the makefile.std script and didn't see anything about shared libs. The correct script is makefile.lnx for linux. What about other systems that support shared libs? I suggest using libtool.

1 participants
0 comments

Re: (Insta)Death to XEmacs 21 26 years, 1 month

Andreas Jaeger

>>>>> SL Baur writes: sb> Someone please try this on MS Windows (if processes are supported) and sb> XEmacs/No-Mule. XEmacs-21.0 "Erzgeberg-pre1" without Mule on Linux 2.1.115, glibc 2.0.95+, egcs 1.1 snapshot gives: Fatal error (11). Your files have been auto-saved. Use `M-x recover-session' to recover them. ... Lisp backtrace follows: process-send-region(#<process "*Boom*" pid 3067 state:exit> 1 434944) # bind (p) (let ((p ...)) (process-send-region p (point-min) (point-max))) ) # (unwind-protect ...) (save-current-buffer (set-buffer temp-buffer) (insert-file-contents-literally file) (let (...) (process-send-region p ... ...))) ) ... If you need more details, please tell me. Andreas P.S. Here's the backtrace: #0 0x818bb60 in lrecord_symbol () #1 0x80fbe39 in Lstream_flush_out (lstr=0x828e754) at /mnt/xemacs/cvs-sources/xemacs-20/src/lstream.c:364 #2 0x80fc89d in Lstream_flush (lstr=0x828e754) at /mnt/xemacs/cvs-sources/xemacs-20/src/lstream.c:372 #3 0x80b9ed9 in unix_send_process (proc=138613144, lstream=0x841eb88) at /mnt/xemacs/cvs-sources/xemacs-20/src/process-unix.c:1191 #4 0x81063b0 in Fprocess_send_region (process=138613144, start=3, end=869889) at /mnt/xemacs/cvs-sources/xemacs-20/src/process.c:974 #5 0x80a2552 in Feval (form=137867932) at /mnt/xemacs/cvs-sources/xemacs-20/src/eval.c:3063 #6 0x80a0519 in Flet (args=137867944) at /mnt/xemacs/cvs-sources/xemacs-20/src/eval.c:758 #7 0x80a221d in Feval (form=137855932) at /mnt/xemacs/cvs-sources/xemacs-20/src/eval.c:2997 #8 0x80a6d3b in Fprogn (args=137869692) at /mnt/xemacs/cvs-sources/xemacs-20/src/eval.c:758 #9 0x809b085 in Fsave_current_buffer (args=137869692) at /mnt/xemacs/cvs-sources/xemacs-20/src/editfns.c:428 #10 0x80a221d in Feval (form=137869680) at /mnt/xemacs/cvs-sources/xemacs-20/src/eval.c:2997 #11 0x80a268e in Feval (form=137866036) at /mnt/xemacs/cvs-sources/xemacs-20/src/eval.c:3083 #12 0x80a7655 in Funwind_protect (args=137869932) at /mnt/xemacs/cvs-sources/xemacs-20/src/eval.c:1497 #13 0x80a221d in Feval (form=137869908) at /mnt/xemacs/cvs-sources/xemacs-20/src/eval.c:2997 #14 0x80a0519 in Flet (args=137869884) at /mnt/xemacs/cvs-sources/xemacs-20/src/eval.c:758 #15 0x80a221d in Feval (form=137869872) at /mnt/xemacs/cvs-sources/xemacs-20/src/eval.c:2997 #16 0x80a268e in Feval (form=137855992) at /mnt/xemacs/cvs-sources/xemacs-20/src/eval.c:3083 #17 0x80a37f9 in funcall_lambda (fun=137856964, nargs=2, arg_vector=0xbfffed00) at /mnt/xemacs/cvs-sources/xemacs-20/src/eval.c:758 #18 0x80a342d in apply_lambda (fun=137856964, numargs=2, unevalled_args=136898388) at /mnt/xemacs/cvs-sources/xemacs-20/src/eval.c:3501 #19 0x80a26ac in Feval (form=137866108) at /mnt/xemacs/cvs-sources/xemacs-20/src/eval.c:3085 #20 0x80a2ba6 in funcall_recording_as (recorded_as=136982216, nargs=1, args=0xbffff064) at /mnt/xemacs/cvs-sources/xemacs-20/src/eval.c:3197 #21 0x80a6cf3 in Ffuncall (nargs=2, args=0xbffff064) at /mnt/xemacs/cvs-sources/xemacs-20/src/eval.c:3238 #22 0x808528e in Fbyte_code (bytestr=136504296, vector=136504408, maxdepth=11) at /mnt/xemacs/cvs-sources/xemacs-20/src/bytecode.c:416 #23 0x80a386a in funcall_lambda (fun=136504592, nargs=1, arg_vector=0xbffff32c) at /mnt/xemacs/cvs-sources/xemacs-20/src/eval.c:3597 #24 0x80a2d0e in funcall_recording_as (recorded_as=137774564, nargs=1, args=0xbffff328) at /mnt/xemacs/cvs-sources/xemacs-20/src/eval.c:3214 #25 0x80a6cf3 in Ffuncall (nargs=2, args=0xbffff328) at /mnt/xemacs/cvs-sources/xemacs-20/src/eval.c:3238 #26 0x808528e in Fbyte_code (bytestr=136504744, vector=136504852, maxdepth=17) at /mnt/xemacs/cvs-sources/xemacs-20/src/bytecode.c:416 #27 0x80a386a in funcall_lambda (fun=136505040, nargs=1, arg_vector=0xbffff4c8) at /mnt/xemacs/cvs-sources/xemacs-20/src/eval.c:3597 #28 0x80a2d0e in funcall_recording_as (recorded_as=137468264, nargs=1, args=0xbffff4c4) at /mnt/xemacs/cvs-sources/xemacs-20/src/eval.c:3214 #29 0x80a6cf3 in Ffuncall (nargs=2, args=0xbffff4c4) at /mnt/xemacs/cvs-sources/xemacs-20/src/eval.c:3238 #30 0x808528e in Fbyte_code (bytestr=136504076, vector=136504108, maxdepth=5) at /mnt/xemacs/cvs-sources/xemacs-20/src/bytecode.c:416 #31 0x80a386a in funcall_lambda (fun=136504140, nargs=0, arg_vector=0xbffff628) at /mnt/xemacs/cvs-sources/xemacs-20/src/eval.c:3597 #32 0x80a2d0e in funcall_recording_as (recorded_as=136504140, nargs=0, args=0xbffff624) at /mnt/xemacs/cvs-sources/xemacs-20/src/eval.c:3214 #33 0x80a5d5c in apply1 (fn=136504140, arg=136898388) at /mnt/xemacs/cvs-sources/xemacs-20/src/eval.c:3238 #34 0x80867b7 in Fcall_interactively (function=137774480, record_flag=136898388, keys=136898388) at /mnt/xemacs/cvs-sources/xemacs-20/src/callint.c:397 #35 0x80a194b in Fcommand_execute (cmd=137774480, record=136898388, keys=136898388) at /mnt/xemacs/cvs-sources/xemacs-20/src/eval.c:2584 #36 0x80bef34 in execute_command_event (command_builder=0x83dccc0, event=138501756) at /mnt/xemacs/cvs-sources/xemacs-20/src/event-stream.c:4346 #37 0x80bf646 in Fdispatch_event (event=138501756) at /mnt/xemacs/cvs-sources/xemacs-20/src/event-stream.c:4685 #38 0x808b492 in Fcommand_loop_1 () at /mnt/xemacs/cvs-sources/xemacs-20/src/cmdloop.c:579 #39 0x808b676 in command_loop_1 (dummy=136898388) at /mnt/xemacs/cvs-sources/xemacs-20/src/cmdloop.c:494 #40 0x80a698b in condition_case_1 (handlers=136898500, bfun=0x808b660 <command_loop_1>, barg=136898388, hfun=0x808af70 <cmd_error>, harg=136898388) at /mnt/xemacs/cvs-sources/xemacs-20/src/eval.c:1653 #41 0x808b762 in command_loop_2 (dummy=136898388) at /mnt/xemacs/cvs-sources/xemacs-20/src/cmdloop.c:256 #42 0x80a6859 in internal_catch (tag=136972760, func=0x808b730 <command_loop_2>, arg=136898388, threw=0x0) at /mnt/xemacs/cvs-sources/xemacs-20/src/eval.c:1328 #43 0x808b1bc in initial_command_loop (load_me=136898388) at /mnt/xemacs/cvs-sources/xemacs-20/src/cmdloop.c:305 #44 0x809e34c in xemacs_21_0_i486_pc_linux () at /mnt/xemacs/cvs-sources/xemacs-20/src/emacs.c:1702 #45 0x809f902 in main (argc=2, argv=0xbffffae4, envp=0xbffffaf0) at /mnt/xemacs/cvs-sources/xemacs-20/src/emacs.c:2119 #46 0x4027e20f in __libc_start_main (main=0x809f800 <main>, argc=2, argv=0xbffffae4, init=0x80776b0 <_init>, fini=0x8175570 <_fini>, rtld_fini=0x4000bae0 <_dl_fini>, stack_end=0xbffffadc) at ../sysdeps/generic/libc-start.c:78 -- Andreas Jaeger aj(a)arthur.rhein-neckar.de jaeger(a)informatik.uni-kl.de for pgp-key finger ajaeger(a)alma.student.uni-kl.de

1 participants
0 comments

Re: Faster lisp engine 26 years, 1 month

Hrvoje Niksic

SL Baur <steve(a)xemacs.org> writes: > Glynn Clements <glynn(a)sensei.co.uk> writes in xemacs-beta(a)xemacs.org: > ... > > Strong typing probably wouldn't hurt either. > > We already have strong typing. Do we? I think Glynn meant something like Common Lisp's DECLARE, DECLAIM and THE forms, neither of which we have. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- 4. Thou shalt not warlorde a sig if it bee the sig of Kibo, nor if it bee the sig of the Inner Circle.

1 participants
0 comments

Re: (Insta)Death to XEmacs 21 26 years, 1 month

SL Baur

Olivier Galibert <galibert(a)pobox.com> writes in xemacs-beta(a)xemacs.org: > On Thu, Aug 13, 1998 at 11:30:22PM -0700, SL Baur wrote: >> [I'm trying to cons up a test case that will give SIGPIPE, but I >> definitely did not expect to see a segmentation fault.] > XEmacs straight-out-of-cvs, IRIX 6.5SE, no crash, only "nil". > Gonna try on solaris. Thanks, please do. If it's only Linux+glibc that's somewhat different.

2 participants
1 comments

Re: Faster lisp engine 26 years, 1 month

Michael Sperber

>>>>> "Oscar" == Oscar Figueiredo <Oscar.Figueiredo(a)di.epfl.ch> writes: >>>>> "sb" == SL Baur <steve(a)xemacs.org> writes: sb> Glynn Clements <glynn(a)sensei.co.uk> writes in xemacs-beta(a)xemacs.org: sb> ... >>> Strong typing probably wouldn't hurt either. sb> We already have strong typing. sb> Static typing is inappropriate. Oscar> I recently have a discussion with a colleague about typing issues, can somebody Oscar> point me out to a web site with definitions of variable typing in programming Oscar> languages ? The best introductory reference is still ＠ARTICLE{CardelliWegner1985, OLDKEY = {CW1985}, AUTHOR = "Luca Cardelli and Peter Wegner", TITLE = "On Understanding Types, Data Abstraction, and Polymorphism", JOURNAL = acmcs, YEAR = "1985", VOLUME = "17", PAGES = "471-522", MONTH = dec } There's a copy at: http://www-pu.informatik.uni-tuebingen.de/users/sperber/proglang-3/cardel... -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

Re: Faster lisp engine 26 years, 1 month

Michael Sperber

>>>>> "Oscar" == Oscar Figueiredo <Oscar.Figueiredo(a)di.epfl.ch> writes: >>>>> "sb" == SL Baur <steve(a)xemacs.org> writes: sb> Glynn Clements <glynn(a)sensei.co.uk> writes in xemacs-beta(a)xemacs.org: sb> ... >>> Strong typing probably wouldn't hurt either. sb> We already have strong typing. sb> Static typing is inappropriate. Oscar> I recently have a discussion with a colleague about typing issues, can somebody Oscar> point me out to a web site with definitions of variable typing in programming Oscar> languages ? The best introductory reference is still: ＠ARTICLE{CardelliWegner1985, OLDKEY = {CW1985}, AUTHOR = "Luca Cardelli and Peter Wegner", TITLE = "On Understanding Types, Data Abstraction, and Polymorphism", JOURNAL = acmcs, YEAR = "1985", VOLUME = "17", PAGES = "471-522", MONTH = dec } There's a copy at: http://www-pu.informatik.uni-tuebingen.de/users/sperber/proglang-3/cardel... -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

Re: Faster lisp engine 26 years, 1 month

Oscar Figueiredo

>>>>> "sb" == SL Baur <steve(a)xemacs.org> writes: sb> Glynn Clements <glynn(a)sensei.co.uk> writes in xemacs-beta(a)xemacs.org: sb> ... >> Strong typing probably wouldn't hurt either. sb> We already have strong typing. sb> Static typing is inappropriate. I recently have a discussion with a colleague about typing issues, can somebody point me out to a web site with definitions of variable typing in programming languages ? Oscar

1 participants
0 comments

Re: Faster lisp engine 26 years, 1 month

Didier Verna

jareth(a)camelot.co.jp (P. E. Jareth Hein) writes: > I'm interested in messing around with redisplay, and have been picking > at it, but do not have the time free to make any commitments as to > when things happen... I have a couple of glyph-related patches that > I'll post when we've got 21.0 to bed, and then will add my dialogs to > lwlib, but after that I'd like to work on perhaps implementing Joel > Peterson's ideas. Anyone else interested in the same area, or have > more ideas on what needs doing there? (I do want to get pixel-level > scrolling and proper scroll-bar behavior in there as well...) I'd be interested too, but I won't be able to get involved before 1999, I think. Pixel based scrolling is one thing indeed. There are many others, like rethinking the redisplay engine in terms of whole page formatting and not only visible-part formatting, the ability to have multiple lines on the side of/around an image and above all, we have to improve the concepts of display-line/rune/block. There are some oddities in there. I won't explain the problems here, but I've planned to make a web page for Ben's site to identify the problems and the things that can't currently easily be done[1]. Hopefully, this page will be ready before the end of the year. Footnotes: [1] like a bevel text extent. I know, I've tried ;-) -- / / _ _ 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

1 participants
0 comments

Re: Showstopper: unix_send_process is badly broken 26 years, 1 month

SL Baur

Here are two stack backtraces illustrating how XEmacs can get SIGPIPE on Unix. The first backtrace is from a gdb> prompt, the second is after a `cont' command. The third attachment is the Installation file for the build. I'm still working on a short test case. `unix_send_process' is clearly foobar'ed, at least for me. uname -a: Linux altair.xemacs.org 2.0.34 #1 Wed Jun 3 23:15:41 PDT 1998 i586 /home/xemacs/xemacs-20.0/configure '--with-gnu-make' '--srcdir=/home/xemacs/xemacs-20.0' '--cflags=-g' '--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 "Erzgeberg-pre1" 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 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 X-Face message headers. 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 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 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

Re: Faster lisp engine 26 years, 1 month

Michael Sperber

>>>>> "Olivier" == Olivier Galibert <galibert(a)pobox.com> writes: Olivier> Strong typing (or more precisely type inference) can, I think, make a Olivier> hell of a difference when you're generating native code. In Olivier> particular if you allow inline generation of lrecord member accessors Olivier> for simple types. But type inference is not the same thing and does not imply strong typing. It still doesn't buy you much. (Between 5% and 10% is all you can hope for.) -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

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