December 1998 - XEmacs-Beta - XEmacs Mailing List Archives

"Pyrenean-pre8" problems on WinNT 26 years

Charles G Waldman

The good news: I have XEmacs 21.0 "Pyrenean-pre8" built on Win32/MSVC6.0, with Jonathan Harris' unofficial EFS patches, and it mostly all works beautifully.... The bad news: it doesn't all quite work so beautifully. EFS works fine on my network, but I get these warnings: (1) (warning/warning) Error caught in `make-auto-save-file-name': Creating directory: No such file or directory, c:\home\cgw\home\cgw\/.autosave (HOME is /home/cgw; this is apparently getting doubled up somehow) Updating packages using EFS: XEmacs successfully fetches the .pkg.tar.gz files from xemacs.org, but when they are installed, I get a warning in the *Package Output* buffer: gunzip: stdout: Bad file number and the new package is not installed. Worse, the old files are removed from /Program Files/XEmacs/xemacs-packages and I'm left with no packages at all.... If updating packages via EFS is going to require a gunzip and tar, we better include suitable versions with the Windows distribution. I'm using the gunzip and tar from the Cygnus toolkit (in a non-Cygnus XEmacs) and they seem to be not suitable. Ditto for the FTP.EXE that comes with Cygnus: EFS works with \WINNT\System32\ftp.exe but not with the "ftp.exe" from Andy Piper's "local.tar.gz" distribution.

2 participants
1 comments

Where is this message coming from and why? 26 years

SL Baur

I'm trying to build XEmacs packages from a bare-ass buck-naked binary with no installed packages besides mule-base. What is happening with this error message? For the moment, I'm ignoring the cause of the core dump. Issuing a prompt when running -batch is a programming error. $ make TAR=tar XEMACS=$(pwd)/../xemacs-21.0/src/xemacs ... make[2]: Entering directory `/usr/home/steveb/staging/xemacs-packages/comm/tm' make EMACS=/usr/home/steveb/staging/xemacs-packages/../xemacs-21.0/src/xemacs -C texi info make[3]: Entering directory `/usr/home/steveb/staging/xemacs-packages/comm/tm/texi' /usr/home/steveb/staging/xemacs-packages/../xemacs-21.0/src/xemacs -batch -q -no-site-file tm-ja.texi \ -eval '(unless (featurep (quote mule)) (kill-emacs 0))' \ -l texinfmt -f texinfo-format-buffer \ -eval '(setq file-coding-system (quote iso-2022-7))' \ -eval '(save-buffer 0)' No mailcrypt; can't verify package-get DB signature, continue? (yes or no) Typing "Yes" at the prompt results in a coredump. Fatal error: assertion failed, file event-tty.c, line 145, c Fatal error (6). ... 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 '--cflags=-O' '--with-mule' '--without-x11' '--prefix=/usr/home/steveb/staging' XEmacs 21.0 "Pyrenean-pre9" 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.

2 participants
1 comments

Assertion while pui-list-packages 26 years

Norbert Koch

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 "Aglaophonos" [Lucid] (i686-pc-linux, Mule) of Mon Nov 30 1998 on apollonius.delta-ii.de configured using `configure --with-mule --gung-ho --with-png --site-includes=/usr/local/include --site-libraries=/usr/local/lib' Please describe exactly what actions triggered the bug and the precise symptoms of the bug: I've done a M-x pui-list-packages (after installing pgp-5.0i on my machine). I suppose the pgp file is not where it should be (hmm, where would that be?) Lisp-backtrace: Signaling: (error "Package-get PGP signature failed to verify") signal(error ("Package-get PGP signature failed to verify")) cerror("Package-get PGP signature failed to verify") apply(cerror "Package-get PGP signature failed to verify") error("Package-get PGP signature failed to verify") package-get-update-base-from-buffer(#<buffer "*package database*">) package-get-update-base(nil t) package-get-require-base(t) #<compiled-function nil "...(188)" [package-get-require-base t get-buffer-create pui-info-buffer "===============================================================================\n" nil start sep-string outbuf message "Creating package list ..." sit-for 0 buffer-read-only buffer-disable-undo erase-buffer use-local-map pui-display-keymap pui-list-verbose " Latest Installed\n Package name Vers. Vers. Description\n" " Latest\n Package name Vers. Description\n" mapcar #<compiled-function ... "...(306)" ... 10> sort copy-sequence package-get-base (lambda ... ...) pui-help-string set-buffer-modified-p pop-to-buffer delete-other-windows pui-selected-packages featurep menubar set-buffer-menubar current-menubar add-submenu pui-menu mode-popup-menu clear-message] 5 ("/usr/local/lib/xemacs-21.2-b4/lisp/package-ui.elc" . 10930) nil>() call-interactively(pui-list-packages) command-execute(pui-list-packages t) execute-extended-command(nil) call-interactively(execute-extended-command) Error message: Fatal error: assertion failed, file eval.c, line 1877, abort() Fatal error (6). C-backtrace: #0 0x4022c6a1 in ?? () from /lib/libc.so.6 #1 0xbfffda04 in ?? () #2 0x4022d6df in ?? () from /lib/libc.so.6 #3 0x80b9caf in assert_failed (file=0x822b15d "eval.c", line=1877, expr=0x822b155 "abort()") at emacs.c:2601 #4 0x80bd6ba in signal_1 (sig=138034788, data=144047552) at eval.c:1877 #5 0x80bddc9 in Fsignal (error_symbol=138034788, data=144047552) at eval.c:2044 #6 0x80be37b in signal_simple_error ( reason=0x8251fac "Internal error: lstream not open", frob=144178376) at eval.c:2053 harg=139007236) at eval.c:1653 #7 0x816565f in Lstream_flush_out (lstr=0x897fcc8) at lstream.c:289 #8 0x81657f5 in Lstream_flush (lstr=0x897fcc8) at lstream.c:372 #9 0x80f0454 in encoding_flusher (stream=0x840b698) at file-coding.c:2342 #10 0x81657cd in Lstream_flush_out (lstr=0x840b698) at lstream.c:364 #11 0x8165f42 in Lstream_close (lstr=0x840b698) at lstream.c:655 #12 0x81673c6 in finalize_lstream (header=0x840b698, for_disksave=0) at lstream.c:178 #13 0x8083075 in sweep_lcrecords_1 (prev=0x836f6e4, used=0xbfffdd68) at alloc.c:3560 #14 0x8084be5 in garbage_collect_1 () at alloc.c:4235 #15 0x8084e99 in Fgarbage_collect () at alloc.c:4663 #16 0x80c02e2 in funcall_recording_as (recorded_as=138036076, nargs=0, args=0xbfffe1e4) at eval.c:3197 #17 0x80c0539 in Ffuncall (nargs=1, args=0xbfffe1e4) at eval.c:3238 #18 0x80913c6 in Fbyte_code (bytestr=137559168, vector=137559428, maxdepth=11) at bytecode.c:416 #19 0x80c154a in funcall_lambda (fun=137559612, nargs=0, arg_vector=0xbfffe3c4) at eval.c:3597 #20 0x80c044d in funcall_recording_as (recorded_as=139125128, nargs=0, args=0xbfffe3c0) at eval.c:3214 #21 0x80c0539 in Ffuncall (nargs=1, args=0xbfffe3c0) at eval.c:3238 #22 0x80913c6 in Fbyte_code (bytestr=137555640, vector=137555740, maxdepth=9) at bytecode.c:416 #23 0x80bfc1c in Feval (form=137555616) at eval.c:3063 #24 0x80bd1a1 in condition_case_1 (handlers=137555864, bfun=0x80bf040 <Feval>, barg=137555616, hfun=0x80c46e4 <run_condition_case_handlers>, #25 0x80bd3ab in condition_case_3 (bodyform=137555616, var=139007236, handlers=137555864) at eval.c:1715 #26 0x8091793 in Fbyte_code (bytestr=137554904, vector=137555276, maxdepth=17) at bytecode.c:576 #27 0x80c154a in funcall_lambda (fun=137556276, nargs=1, arg_vector=0xbfffec3c) at eval.c:3597 #28 0x80c044d in funcall_recording_as (recorded_as=139007040, nargs=1, args=0xbfffec38) at eval.c:3214 #29 0x80c0539 in Ffuncall (nargs=2, args=0xbfffec38) at eval.c:3238 #30 0x80913c6 in Fbyte_code (bytestr=137558568, vector=137558652, maxdepth=11) at bytecode.c:416 #31 0x80c154a in funcall_lambda (fun=137558736, nargs=1, arg_vector=0xbfffed40) at eval.c:3597 #32 0x80c044d in funcall_recording_as (recorded_as=139124764, nargs=1, args=0xbfffed3c) at eval.c:3214 #33 0x80c1b5c in call1 (fn=139124764, arg0=138034676) at eval.c:3921 #34 0x8106f0c in execute_internal_event (event=144263660) at event-stream.c:3044 #35 0x810a8f2 in Fdispatch_event (event=144263660) at event-stream.c:4690 #36 0x809de29 in Fcommand_loop_1 () at cmdloop.c:579 #37 0x809dba5 in command_loop_1 (dummy=138034676) at cmdloop.c:494 #38 0x80bd1a1 in condition_case_1 (handlers=138034788, bfun=0x809db54 <command_loop_1>, barg=138034676, hfun=0x809cfd8 <cmd_error>, harg=138034676) at eval.c:1653 #39 0x809dffc in command_loop_2 (dummy=138034676) at cmdloop.c:256 #40 0x80bcd74 in internal_catch (tag=138109412, func=0x809dfc8 <command_loop_2>, arg=138034676, threw=0x0) at eval.c:1328 #41 0x809d443 in initial_command_loop (load_me=138034676) at cmdloop.c:305 #42 0x80b8bb5 in xemacs_21_2_b4_i686_pc_linux (argc=1, argv=0xbffff050, envp=0xbffff058, restart=0) at emacs.c:1698 #43 0x80b92e1 in main (argc=1, argv=0xbffff050, envp=0xbffff058) at emacs.c:2115 Recent keystrokes: misc-user Recent messages (most recent first): Loading emacsbug...done Loading emacsbug... Loading /home/norbert/.emacs-session...done Loading /home/norbert/.emacs-session... Loading gnus-xmas...done Loading gnus-xmas... Loading /home/norbert/.emacs-env.el...done Loading /home/norbert/.emacs-env.el... Loading /home/norbert/.emacs-c.el...done passed emacs-c

1 participants
0 comments

Re: XEmacs-21.2-beta4 is out 26 years

SL Baur

Matthew O Persico <mpersico(a)erols.com> writes in xemacs-beta(a)xemacs.org: > Well, can we put a link to http://www.digistar.com/bzip2/ on the XEmacs > beta page so others can find it? Finding it easily will probably make > all the complaints go away. A link would be O.K. but we have the distribution already on the ftp site: ftp://ftp.xemacs.org/pub/xemacs/aux/ It is present in 8 other locations on the same server. $ locate bzip | grep .tar /ftp/pub/devel/egcs/infrastructure/bzip2-0.1pl2.tar.gz /ftp/pub/distributions/debian/dists/slink/main/source/utils/bzip2_0.9.0.orig.tar.gz /ftp/pub/sites/ftp.kernel.org/software/utils/compress/bzip2/bzip2-0.1pl2.tar /ftp/pub/sites/ftp.kernel.org/software/utils/compress/bzip2/bzip2-0.1pl2.tar.bz2 /ftp/pub/sites/ftp.kernel.org/software/utils/compress/bzip2/bzip2-0.1pl2.tar.gz /ftp/pub/sites/tsx-11.mit.edu/sources/usr.bin/Archivers/bzip-0.21.tar.gz /ftp/pub/tmp/slackware/slackware-3.5/source/a/bzip2/bzip2-0.9.0b.tar.gz /ftp/pub/tmp/slackware/slackware-3.5/source/a/bzip2/_bzip2.tar.gz /ftp/pub/tmp/slackware/slackware-3.5/source/a/tar/bzip2-tar.diff.gz /ftp/pub/tmp/slackware/slackware-3.6/source/a/bzip2/bzip2-0.9.0b.tar.gz /ftp/pub/tmp/slackware/slackware-3.6/source/a/bzip2/_bzip2.tar.gz /ftp/pub/tmp/slackware/slackware-3.6/source/a/tar/bzip2-tar.diff.gz /ftp/pub/tmp/stampede/stable/source/base/bzip2/bzip2-0.9.0c.tar.gz /ftp/pub/tux/xemacs/aux/bzip2-0.1pl2.tar.gz /ftp/pub/tux/xemacs/aux/bzip2-0.9.0b.tar.gz /ftp/pub/util/bzip2-0.1pl2.tar.gz

2 participants
1 comments

[PATCH] build fix. 26 years

Sergey Okhapkin

Hi! This patch fixes build problems when build directory differs from Xemacs src directory. lib-src/Makefile.in.in - add $srcdir/../src to include search path. Index: Makefile.in.in =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs-20/lib-src/Makefile.in.in,v retrieving revision 1.38 diff -u -p -r1.38 Makefile.in.in --- Makefile.in.in 1998/10/23 04:40:39 1.38 +++ Makefile.in.in 1998/12/02 10:32:46 ＠＠ -138,7 +138,7 ＠＠ ld_libs_general=＠ld_libs_general＠ ## We need to #define emacs to get the right versions of some files. -cppflags = -Demacs -I../src $(CPPFLAGS) +cppflags = -Demacs -I../src -I$(srcdir)/../src $(CPPFLAGS) cflags = $(CFLAGS) $(cppflags) $(c_switch_general) ldflags = $(LDFLAGS) $(ld_switch_general) $(ld_libs_general) -- Sergey Okhapkin, http://www.lexa.ru/sos Piscataway, NJ

2 participants
1 comments

Re: imenu oops... 26 years

Jan Vroonhof

Adrian Aichner <aichner(a)ecf.teradyne.com> writes: > Jan> main menubar. That you can navigate using M-x accelerate-menu > Jan> RET and the cursors keys. > > This works fine in (emacs-version) "XEmacs 21.0 \"Pyrenean-pre8\" > [Lucid] (i386-pc-win32) of Mon Nov 30 1998 on DARTER2" > natively built on WindowsNT4sp3. > > The M-x isn't even necessary. Unfortunately the X version does not generate "alt-press-only" events that you could bind to accelerate-menu. Jan

2 participants
1 comments

Re: a few more package get cleanups 26 years

Greg Klanderman

>>>>> "Jan" == Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: Jan> Jan> greg(a)alphatech.com (Greg Klanderman) writes: >> However, I'd like it to be the case that you get the error on entry to >> the package update stuff (pui-list-packages, etc) rather than later >> when you go to update a package. Jan> Jan> Then it should not be an error in my case. Often I do just want to Jan> look at the installed versions and there is no need to go the net for Jan> that? Note the "List" part of "List & Install" But if you've customized package-get-remote as you previously stated, entering pui-list-packages will grab a remote copy of the db with your last patch. It just seems the default behavior should favor keeping a less experienced user from shooting himself in the foot. Usually when you use pui-list-packages you want to install new packages. You should get the current list. Jan> Maybe we should change `pui-toggle-package' to warn in this case. Jan> And a add package-get-require-base with a "force-current = t" argument Jan> to it too. Additionally one can add a warning and an "Update" button Jan> to the top the *Packages* buffer. seems overly complicated. this stuff is already too hairy. also, with the code your way, (package-get-require-base t) may succeed but not actually get a current database. Jan> Note that the Jan> current package-get code does correctly first try to fetch the latest Jan> version if the package-get-remote has since become non-nil. No, pui-list-packages does (package-get-require-base t) so it thinks it already has gotten an up to date package index, when in fact it loaded the one from the etc directory, and has set package-get-was-current to true.

1 participants
0 comments

Re: "Pyrenean-pre8" problems on WinNT 26 years

Adrian Aichner

>>>>> "Charles" == Charles G Waldman <cgw(a)pgt.com> writes: Charles> The good news: I have XEmacs 21.0 "Pyrenean-pre8" built Charles> on Win32/MSVC6.0, with Jonathan Harris' unofficial EFS Charles> patches, and it mostly all works beautifully.... Charles> The bad news: it doesn't all quite work so beautifully. Charles> EFS works fine on my network, but I get these warnings: Charles> (1) (warning/warning) Error caught in Charles> `make-auto-save-file-name': Creating directory: No such Charles> file or directory, c:\home\cgw\home\cgw\/.autosave Yep, the current naming scheme for auto-save file names is not legal on WindowsNT's ````file system''''. You can get it to work by setting auto-save-directory nil. This works fine, except for performance when you edit files via NFS or EFS since the auto-save files are stored in the directory of the file it auto-saves. Charles> (HOME is /home/cgw; this is apparently getting doubled up Charles> somehow) Charles> Updating packages using EFS: XEmacs successfully fetches Charles> the .pkg.tar.gz files from xemacs.org, but when they are Charles> installed, I get a warning in the *Package Output* Charles> buffer: Charles> gunzip: stdout: Bad file number Charles> and the new package is not installed. Worse, the old Charles> files are removed from /Program Charles> Files/XEmacs/xemacs-packages and I'm left with no Charles> packages at all.... Charles> If updating packages via EFS is going to require a gunzip Charles> and tar, we better include suitable versions with the Charles> Windows distribution. I'm using the gunzip and tar from Charles> the Cygnus toolkit (in a non-Cygnus XEmacs) and they seem Charles> to be not suitable. Ditto for the FTP.EXE that comes Charles> with Cygnus: EFS works with \WINNT\System32\ftp.exe but Charles> not with the "ftp.exe" from Andy Piper's "local.tar.gz" Charles> distribution. -- Adrian Aichner European Design Center Teradyne GmbH Semiconductor Test Group Telephone +49/89/41861(0)-208 Dingolfinger Strasse 2 Fax +49/89/41861-217 (What is a Fax?) D-81673 MUENCHEN E-mail adrian.aichner(a)teradyne.com

2 participants
1 comments

[Success] 21.2 "Aglaophonos" XEmacs Lucid (beta4) on Solaris 2.5 26 years

John H Palmieri

See my comments below. uname -a: SunOS ahoward 5.5 Generic_103093-23 sun4m sparc SUNW,SPARCstation-10 ./configure '--prefix=/afs/nd.edu/user4/jpalmier' '--site-includes=/afs/nd.edu/user4/jpalmier/lib/include' '--site-libraries=/afs/nd.edu/user4/jpalmier/lib/lib' '--x-includes=/usr/openwin/share/include' '--with-cde=no' XEmacs 21.2-b4 "Aglaophonos" configured for `sparc-sun-solaris2.5'. Where should the build process find the source code? /afs/nd.edu/user4/jpalmier/silly/transfers/xemacs-21.2-b4 What installation prefix should install use? /afs/nd.edu/user4/jpalmier What operating system and machine description files should XEmacs use? `s/sol2.h' and `m/sparc.h' What compiler should XEmacs be built with? gcc -g -O3 -Wall -Wno-switch 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/openwin/share/include Where do we find X Windows libraries? /usr/dt/lib /usr/openwin/lib Additional header files: /afs/nd.edu/user4/jpalmier/lib/include Additional libraries: /afs/nd.edu/user4/jpalmier/lib/lib Runtime library search path: /afs/nd.edu/user4/jpalmier/lib/lib:/usr/dt/lib:/usr/openwin/lib:/usr/local/src/gnu96/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 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 "dot-locking" 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: --------------------------------------------------------- My comments: 1. If I ran configure without '--x-includes=/usr/openwin/share/include', then the variables x_libraries and x_includes would not be set correctly--they ended up being set to x_libraries: /usr/dt/lib /usr/openwin/lib x_includes: /usr/dt/include /usr/X11R6/include Even though /usr/openwin/share/include exists and contains the appropriate things, this part of the 'configure' was not defining x_includes properly (after this part of the script, x_includes was still "NONE"). I noticed that the PROBLEMS file in the distribution mentions something about this: *** Problems finding X11 libraries on Solaris with Openwindows Some users have reported problems in this area. The reported solution is to define the environment variable OPENWINHOME, even if you must set it to `/usr/openwin'. I do have this variable set to /usr/openwin, and it didn't help me. 2. Running configure without the option '--with-cde=no' leads to this problem: gcc -c -g -O3 -Wall -Wno-switch -Demacs -I. -DHAVE_CONFIG_H -I/afs/nd.edu/user4/jpalmier/lib/include -I/usr/dt/include -I/usr/openwin/share/include frame-x.c frame-x.c:975: Dt/Dt.h: No such file or directory frame-x.c:976: Dt/Dnd.h: No such file or directory make[1]: *** [frame-x.o] Error 1 make[1]: Leaving directory `/afs/nd.edu/user4/jpalmier/silly/transfers/xemacs-21.2-b3/src' make: *** [src] Error 2 Did I do something wrong, or did configure? -- John H. Palmieri e-mail: palmieri.2(a)nd.edu 205 Computing/Mathematics Building URL:http://www.nd.edu/~jpalmier/ University of Notre Dame (219) 631-8846 Notre Dame, IN 46556

2 participants
1 comments

Re: a few more package get cleanups 26 years

Jan Vroonhof

greg(a)alphatech.com (Greg Klanderman) writes: > However, I'd like it to be the case that you get the error on entry to > the package update stuff (pui-list-packages, etc) rather than later > when you go to update a package. Then it should not be an error in my case. Often I do just want to look at the installed versions and there is no need to go the net for that? Note the "List" part of "List & Install" Maybe we should change `pui-toggle-package' to warn in this case. And a add package-get-require-base with a "force-current = t" argument to it too. Additionally one can add a warning and an "Update" button to the top the *Packages* buffer. Note that the current package-get code does correctly first try to fetch the latest version if the package-get-remote has since become non-nil. 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 December 1998