January 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: Gnuclient -nw strangeness 25 years, 10 months

Jan Vroonhof

Robert_Pluim(a)BayNetworks.COM (Robert Pluim) writes: > if I do: xemacs -vanilla & (which creates an X frame) > and then: gnuclient -nw from the same xterm, gnuclient hangs. I can ^Z > it, and then bring xemacs to the foreground, and I'll get a tty frame. > > If I do the gnuclient -nw from a different xterm, everything works as > expected. Unfortunately this a known problem. It is basically the unix terminal group mechanism which is getting our way here. The problem could be avoid if you could do 'xemacs -unmapped </dev/null &' or XEmacs could itself detach from its terminal. However this cannot currently be as XEmacs needs stdin to be a tty. This could be solved by -batch like mode (which has a stream device[1] and thus does not need a tty) that does not exit when some flag is set. Gnuserv-start could then set this flag. Alternatively 'gnuclient' could be me made to proxy the stuff to its own pseudo terminal like 'script' does. This would also make the signal forwarding a lot cleaner. Nobody has done the coding yet however. Jan Footnotes: [1] Unix XEmacs has 3! device types: X, tty, stream.

3 participants
2 comments

[crash] image display problem on 24bpp 25 years, 10 months

Kazuo Oishi

XEmacs inline image display cause crash on 24bpp X. 1. $ xemacs -vanilla 2. C-x C-f imagefile After broken (monochrome, vertical lined) image or nothing is displayed, XEmacs crashes. PNG, JPEG, TIFF, GIF formated image has this problem, and XPM does't. This is 100% reproductive in my one environment, but not occur in other environment. I heard some X server (for example, XFree86 SVGA I am using in the environment) handle 24bpp images without padding to 32bit and this cause image display problem in some software which handle image directly. I think XEmacs is one of them. uname -a: Linux agenv4 2.0.36 #1 Thu Nov 19 12:33:18 JST 1998 i586 unknown ./configure '--compiler=egcc' '--with-mule' '--with-xim=no' XEmacs 21.0-b61 "Poitou61" configured for `i586-pc-linux'. Where should the build process find the source code? /var/local/src/xemacs/xemacs-21.0.61 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? egcc -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 support for Canna on Mule. 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. 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: --------------------------------------------------------- Lisp backtrace is empty, and $ gdb /usr/local/bin/xemacs core GNU gdb 4.17.m68k.objc.threads.hwwp.fpu.gnat 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 "i486-pc-linux-gnu"... Core was generated by `/usr/local/bin/xemacs -vanilla'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libwcsmbs.so.0...done. Reading symbols from /usr/X11R6/lib/libXm.so.1...done. Reading symbols from /usr/lib/libcanna.so.1...done. Reading symbols from /usr/lib/libRKC.so.1...done. Reading symbols from /usr/lib/libcompface.so.1...done. Reading symbols from /usr/lib/libtiff.so.3...done. Reading symbols from /usr/lib/libpng.so.2...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.2...done. Reading symbols from /usr/lib/libgdbm.so.1...done. Reading symbols from /usr/lib/libgpm.so.1...done. Reading symbols from /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.1...done. Reading symbols from /lib/libnss_dns.so.1...done. Reading symbols from /lib/libresolv.so.2...done. Reading symbols from /lib/libnss_compat.so.1...done. Reading symbols from /lib/libnsl.so.1...done. #0 0x4041159d in malloc () (gdb) where #0 0x4041159d in malloc () #1 0x40411335 in malloc () #2 0x8083a2e in xmalloc_and_zero (size=20) at alloc.c:392 #3 0x80afc5e in Dynarr_newf (elsize=1) at dynarr.c:117 #4 0x80efcbf in convert_to_external_format ( ptr=0xbfff4a48 " ü:\b¸Jÿ¿îû\013\b\202", len=1, len_out=0xbfff4a00, fmt=FORMAT_TERMINAL) at file-coding.c:2386 #5 0x8175164 in write_string_to_stdio_stream (stream=0x8360658, con=0x0, str=0xbfff4a48 " ü:\b¸Jÿ¿îû\013\b\202", offset=0, len=1, fmt=FORMAT_TERMINAL) at print.c:120 #6 0x81786ef in Fexternal_debugging_output (char_or_string=130, stdout_p=137974484, device=137974484) at print.c:1536 #7 0x80bfbee in funcall_recording_as (recorded_as=138083332, nargs=1, args=0xbfff4ad0) at eval.c:3193 #8 0x80c3614 in call1 (fn=138083332, arg0=130) at eval.c:3238 #9 0x8175789 in output_string (function=138083332, nonreloc=0x821f2f0 " # (unwind-protect ...)\n", reloc=137974484, offset=0, len=25) at print.c:252 #10 0x8178f03 in write_c_string (str=0x821f2f0 " # (unwind-protect ...)\n", stream=138083332) at print.c:370 #11 0x80c2860 in Fbacktrace (stream=138083332, detailed=137974512) at eval.c:4815 #12 0x80b9e95 in fatal_error_signal (sig=11) at emacs.c:245 #13 <signal handler called> (gdb) -- 大石一雄 (OISHI Kazuo)

1 participants
0 comments

Re: Dynamic linking needs -Wl,-E on glibc2 Unix 25 years, 10 months

SL Baur

[I am using Linux kernel 2.2.0-pre6, pgcc/egcs-1.1.1 w/ GNU libc 2.0.109] SL Baur <steve(a)xemacs.org> writes in xemacs-beta(a)xemacs.org: > Jan Vroonhof <vroonhof(a)math.ethz.ch> writes in xemacs-beta(a)xemacs.org: >> I was playing with the new dl code on my debian hamm system at home >> which must be a fairly typical glibc2 linux and it only worked when I >> hand patched the makefile to add a "-Wl,-E" to the link flags. > What happens when you feed `--with-shlib=yes' to configure? sysdll.o: In function `dll_open': sysdll.o(.text+0x1b): undefined reference to `dlopen' sysdll.o: In function `dll_close': sysdll.o(.text+0x36): undefined reference to `dlclose' sysdll.o: In function `dll_function': sysdll.o(.text+0x4b): undefined reference to `dlsym' sysdll.o: In function `dll_variable': sysdll.o(.text+0x6b): undefined reference to `dlsym' collect2: ld returned 1 exit status make[1]: *** [temacs] Error 1 make[1]: Leaving directory `/devel/xemacs/xemacs-21.2/src' make: *** [src] Error 2 >> I guess this should have been configure's job. I did not investigate >> further. > Yup. I've run one test and autodetection didn't work. It looks like > it might be a logic error in configure because -ldl is being detected > and added to the link command, Something is hosed. `-ldl' is only being added if `--with-shlib' is not specified on the command line. It is _not_ added if `--with-shlib=yes' is used. > It appears to work when I explicitly add --with-shlib. I should have let the build complete ... uname -a: Linux demeter.xemacs.org 2.2.0-pre6 #2 SMP Sat Jan 9 02:20:26 PST 1999 i686 unknown ./configure '--cflags=-mpentiumpro -O6 -fno-exceptions' '--error-checking=none' '--debug=no' '--with-mule=yes' '--with-dialogs=athena3d' '--with-scrollbars=athena3d' '--use-union-type=no' '--with-xim=xlib' '--with-xfs' '--mail-locking=file' '--extra-verbose=no' '--with-shlib=yes' XEmacs 21.2-b8 "Artemis" configured for `i686-pc-linux'. Where should the build process find the source code? /devel/xemacs/xemacs-21.2 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 -mpentiumpro -O6 -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 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 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 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 Lisp_Objects with minimal tagbits.

1 participants
0 comments

(current-time) vs (current-time-string) 25 years, 10 months

Truls Arnegaard

Hi, (current-time-string) "Tue Jan 12 20:27:05 1999" (current-time-string (current-time)) "Fri Jan 16 13:33:28 1970" Any hints? -Truls uname -a: CYGWIN_NT-4.0 MARKVEIEN 20.1 (0.3/1/1) 1998-12-3 20:39:18 i586 unknown ./configure '--debug=no' '--site-prefixes=/local' '--gung-ho' '--error-checking=no' '--prefix=/local' '--extra-verbose=no' XEmacs 21.0-b62 "Pyrenean" configured for `i586-pc-cygwin32'. Where should the build process find the source code? /src/xemacs-21.0 What installation prefix should install use? /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? msw Additional prefixes: /local 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 GNU DBM. Compiling in support for ncurses. Compiling in File coding support. Compiling in EXPERIMENTAL support for Drag'n'Drop ( msw ). movemail will use "dot-locking" for locking mail spool files. Using Lisp_Objects with minimal tagbits. Using indexed lrecord implementation.

3 participants
2 comments

Re: Dynamic linking needs -Wl,-E on glibc2 Unix 25 years, 10 months

SL Baur

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes in xemacs-beta(a)xemacs.org: > I was playing with the new dl code on my debian hamm system at home > which must be a fairly typical glibc2 linux and it only worked when I > hand patched the makefile to add a "-Wl,-E" to the link flags. What happens when you feed `--with-shlib=yes' to configure? > I guess this should have been configure's job. I did not investigate > further. Yup. I've run one test and autodetection didn't work. It looks like it might be a logic error in configure because -ldl is being detected and added to the link command, but ld_dynamic_link_flags isn't getting set correctly. It appears to work when I explicitly add --with-shlib.

1 participants
0 comments

Re: What to do with modules now ... 25 years, 10 months

William M. Perry

Hrvoje Niksic <hniksic(a)srce.hr> writes: > Paul Flinders <paul(a)dawa.demon.co.uk> writes: > > > Hrvoje Niksic writes: > > > Paul Flinders <paul(a)dawa.demon.co.uk> writes: > > > > > > > > 1) How will you handle this on systems without dynamic linking > > > > > (e.g. Ultrix)? > > > > > > > > You could use the (new) XFree module loader > > > > > > I don't understand this. Could you please elaborate? > > > > XFree 4.0 uses a module loader donated by MetroLink which can load > > elf, a.out and coff object files (or archive libraries for that > > matter). I don't see why systems without dynamic linkage couldn't > > use it. > > Because systems without dynamic linkage do not offer low-level runtime > loading semantics? It may be my short-sightedness, but I've never > seen executables dynamically loading object files under Ultrix. It > might be done through heavy machine-dependent hackery, though, but I > don't believe XFree does it until I see it. > > Even if it worked under Ultrix, XEmacs needn't strictly depend on X > and, more importantly, the machine running XEmacs needn't host an X > server and the associated libraries. > > I'm not saying that Ultrix should hamper progress; my point is that: > > 1) if we do make decisions that will affect ancient systems like > Ultrix, we should make them consciously and openly. > > 2) before doing that, we might want to look into others' solution; it > might be interesting to see what Perl 5 and zsh 3.1 do under > Ultrix. Doesn't GNU dld work with ultrix? -bp

1 participants
0 comments

Re: What to do with modules now ... 25 years, 10 months

Hrvoje Niksic

Paul Flinders <paul(a)dawa.demon.co.uk> writes: > > 1) How will you handle this on systems without dynamic linking > > (e.g. Ultrix)? > > > > You could use the (new) XFree module loader I don't understand this. Could you please elaborate?

2 participants
1 comments

Re: What to do with modules now ... 25 years, 10 months

Paul Flinders

Hrvoje Niksic <hniksic(a)srce.hr> writes: > "J. Kean Johnston" <jkj(a)sco.com> writes: > > > Once the module loading technology is in place and people are > > happier with it, I would like to start work on ripping out major > > parts of XEmacs and putting them in modules. I havem in my > > prototype tree, a mechanism in place where a given source file can > > either be compiled in as part of the dumped Emacs, or as a module. > > If module loading is availible, the makefile is constructed in such > > a way that it compiles things as modules rather than part of the > > dumped Emacs. This is a good thing. > > This is very cool. Two questions: > > 1) How will you handle this on systems without dynamic linking > (e.g. Ultrix)? > You could use the (new) XFree module loader

1 participants
0 comments

Re: 21.0 vs 21.2 25 years, 10 months

SL Baur

I wrote: > Wrong. Tarballs are for those with bandwidth to burn. Getting and > staying up to date via CVS is *much* faster with limited bandwidth. Matthew O Persico <mpersico(a)erols.com> writes in xemacs-beta(a)xemacs.org: > Gee, the perl folks said the exact opposite. The last time I checked, Perl was a _much_ smaller bundle. Full XEmacs sources are around 25MB compressed with `gzip -9'. With a perl-sized bundle the opposite is probably true. > I'll take your word for it - it's your software.

1 participants
0 comments

Re: rssh.el interactions with ange-ftp/efs 25 years, 10 months

Jan Vroonhof

Richard Stallman <rms(a)gnu.org> writes: > I mean /user＠host＠method:path > > This syntax seems problem-free to me, but why do we want the feature? Because when Kai is finished we have at least 2 different methods for remote editing. /user＠host:path is currently taken by EFS/ange-ftp but I think it should be generalised to just mean "remote filename"/"special file name" and have Emacs figure out the best way of accessing based on user and site configuration. I think the above is a convenient syntax for those occasions you DO want to specify a specific method. Jan

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