February 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Problems Building on Irix 6.2 25 years, 2 months

Martin Buchholz

I'm in the process of investigating this, but I wasn't ready for it to become an issue for xemacs-beta so soon. But I'll throw some thoughts out there now. First, a question: shouldn't we have this patch?? --- configure.in.old +++ configure.in ＠＠ -1941,7 +1941,7 ＠＠ AC_MSG_CHECKING("for runtime libraries flag") case "$opsys" in sol2 ) dash_r="-R" ;; - decosf* | linux* ) dash_r="-rpath " ;; + decosf* | linux* | irix*) dash_r="-rpath " ;; *) dash_r="" for try_dash_r in "-R" "-R " "-rpath "; do Secondly, my setup is a little unusual - broken MIT X11 installed in /usr/local and libwnn installed in /usr/lib but not /usr/lib32. Man pages are not installed :-(. In other words, a typical real-life system. I haven't figured out how to make configure deal sanely with this setup yet. You are trapped in a twisty maze of directories. In every one there is a libX11, each slightly different: $ ll /usr/local/lib/libX11.* /usr/lib*/**/libX11* | grep -v '.->' -rw-r--r-- 1 root sys 1551960 Jan 2 1996 /usr/local/lib/libX11.a -rw-r--r-- 1 root sys 1826704 Oct 8 1996 /usr/lib64/libX11.so.1 -rw-r--r-- 1 root sys 1500576 Oct 8 1996 /usr/lib/abi/libX11.so.2 -rw-r--r-- 1 root sys 1592652 Oct 9 1996 /usr/lib32/libX11.so.1 -rw-r--r-- 1 root sys 1471032 Oct 9 1996 /usr/lib/libX11.so.1 I (re)discovered that --x-includes=/usr/include is a BAD idea when using gcc. /net/wanchai/export1/xemacs/local/irix/bin/gcc -c -fno-exceptions -O3 -Wall -Wpointer-arith -Winline -Wmissing-prototypes -Wmissing-declarations -Wunused -Wformat -Wno-switch -Wno-sign-compare -Wno-uninitialized -Wshadow -Demacs -I. -DHAVE_CONFIG_H -I/net/wanchai/export1/xemacs/local/irix/include -I/usr/include /tmp_mnt/net/wanchai/export1/xemacs/home/martin/x/ws/21.0/src/symbols.c /tmp_mnt/net/wanchai/export1/xemacs/home/martin/x/ws/21.0/src/symbols.c: In function `maybe_call_magic_handler': /tmp_mnt/net/wanchai/export1/xemacs/home/martin/x/ws/21.0/src/symbols.c:2879: warning: implicit declaration of function `__NO_CFOLD_WARNING' /tmp_mnt/net/wanchai/export1/xemacs/home/martin/x/ws/21.0/src/symbols.c:2879: warning: implicit declaration of function `__builtin_alignof' /tmp_mnt/net/wanchai/export1/xemacs/home/martin/x/ws/21.0/src/symbols.c:2879: parse error before `Lisp_Object' /tmp_mnt/net/wanchai/export1/xemacs/home/martin/x/ws/21.0/src/symbols.c:2879: parse error before `Lisp_Object' /tmp_mnt/net/wanchai/export1/xemacs/home/martin/x/ws/21.0/src/symbols.c:2879: parse error before `Lisp_Object' /tmp_mnt/net/wanchai/export1/xemacs/home/martin/x/ws/21.0/src/symbols.c:2879: parse error before `Lisp_Object' /tmp_mnt/net/wanchai/export1/xemacs/home/martin/x/ws/21.0/src/symbols.c:2879: warning: implicit declaration of function `__builtin_classof' /tmp_mnt/net/wanchai/export1/xemacs/home/martin/x/ws/21.0/src/symbols.c:2879: parse error before `Lisp_Object' /tmp_mnt/net/wanchai/export1/xemacs/home/martin/x/ws/21.0/src/symbols.c:2879: parse error before `)' Martin

1 participants
0 comments

Re: Odd problem with 21.0.63 25 years, 2 months

SL Baur

[Thanks for the report] Kevin Oberman <oberman(a)es.net> writes in xemacs-beta(a)xemacs.org: > This may be some weird FOTU thing. (That's Fluke Of The Universe.) I > can't easily reproduce it and it may never happen to anyone ever again. > I just built 21.0.63 on Digital UNIX 4.0D using DEC C. No problems > seen during the build. I then updated packages and proceeded. > When I started up XEmacs, I got an error that mime-setup was not > found. I checked and I found all of the .el.gz files, but no > .elcs. This is true of all files .els in the tm package. Since I had > gziped all of the .el files, they were not loaded/executed. Wierd. > ... Could something have been wrong with the MANIFEST.tm? I don't > see anything obvious about it. Yup, there's a problem[1]. I'll make a new version ASAP. > I deleted the package and re-installed it. All .elcs were present. I'm > stumped. Hopefully this was only due to corruption of the MANIFEST file. Footnotes: [1] Everything after `lib-src/tmdecode' is wrong: lib-src/tm-ps lib-src/tmdecode lib-src/CVS: Entries Repository Root

1 participants
0 comments

Package warnings when starting up 21.2.10 25 years, 2 months

John Mignault

The only thing i"ve noticed so far is this warning when starting up XEmacs: (1) (warning/warning) Autoload error in: /usr/local/lib/xemacs/packages/man/lisp/strokes/auto-autoloads: Already loaded How exactly should I go about tracking down something like this? I looked in the file mentioned and nothing jumped out as an obvious suspect... Suggestions for appropriate parts of the docs? Am I just indescribably dense? :) j -- #!/usr/bin/perl $dot="\x2e";$lt="\x3c";$gt="\x3e";$at="\x40"; print "J Mignault ${lt}jbm${at}panix${dot}com${gt}\n"; $wright = qq(The other day I went to a tourist information booth and asked, "Tell me about some of the people who were here last year.");

2 participants
1 comments

[Success] 21.2 "Boreas" XEmacs Lucid (beta10) on i586-pc-linux 25 years, 2 months

John Mignault

Patched up from b9 (why, it seems like only yesterday. Wait, it *was* yesterday.) Fine so far. j > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /usr/local/src/xemacs-21.2.8/Installation: > (Output from most recent run of ./configure) uname -a: Linux jbm 2.0.34 #1 Fri May 8 16:05:57 EDT 1998 i586 unknown ./configure '--dynamic' '--with-database=gnudbm' '--with-xpm' '--gung-ho' '--with-mule=no' '--with-png=yes' '--with-session' XEmacs 21.2-b10 "Boreas" configured for `i586-pc-linux'. Where should the build process find the source code? /usr/local/src/xemacs-21.2.8 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 GNU DBM. Compiling in support for ncurses. Compiling in support for GPM (General Purpose Mouse). Compiling in support for proper session-management. 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 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: --------------------------------------------------------- > /usr/local/src/xemacs-21.2.8/beta.err does not exist! -- #!/usr/bin/perl $dot="\x2e";$lt="\x3c";$gt="\x3e";$at="\x40"; print "J Mignault ${lt}jbm${at}panix${dot}com${gt}\n"; $wright = qq(Why isn't phonetic spelled the way it sounds?);

1 participants
0 comments

[crash] XEmacs 21.2.9 Xt keysym death (again) 25 years, 2 months

Karl Kleinpaste

Got another x_to_emacs_keysym() bomb, appears identical to what happened in -b8. The frame pointer is again null. RH5.2, kernel 2.2.1-ac4, XFree 3.3.3.1. Program received signal SIGSEGV, Segmentation fault. x_to_emacs_keysym (event=0xbffff554, simple_p=0) at frame.h:248 248 assert (EQ (FRAME_TYPE (f), sym)); (gdb) bt #0 x_to_emacs_keysym (event=0xbffff554, simple_p=0) at frame.h:248 #1 0x819d7ae in x_event_to_emacs_event (x_event=0xbffff554, emacs_event=0x898a848) at event-Xt.c:997 #2 0x819f89b in emacs_Xt_event_handler (wid=0x8543b28, closure=0x0, event=0xbffff554, continue_to_dispatch=0xbffff48f "\001 %P\b,") at event-Xt.c:2440 #3 0x400f1c9f in XtDispatchEventToWidget () #4 0x400f26fd in _XtDefaultDispatcher () #5 0x400f2975 in XtDispatchEvent () #6 0x400fd3d5 in XtAppProcessEvent () #7 0x819f674 in emacs_Xt_next_event (emacs_event=0x8b24c5c) at event-Xt.c:2392 #8 0x80d5049 in event_stream_next_event (event=0x8b24c5c) at event-stream.c:568 #9 0x80d7afc in next_event_internal (target_event=145902684, allow_queued=1) at event-stream.c:2022 #10 0x80d8179 in Fnext_event (event=145902684, prompt=137634620) at event-stream.c:2239 #11 0x8073742 in Fcommand_loop_1 () at cmdloop.c:569 #12 0x80734e5 in command_loop_1 (dummy=137634620) at cmdloop.c:493 #13 0x8091745 in condition_case_1 (handlers=137634732, bfun=0x8073498 <command_loop_1>, barg=137634620, hfun=0x8072984 <cmd_error>, harg=137634620) at eval.c:1640 #14 0x807396c in command_loop_2 (dummy=137634620) at cmdloop.c:255 #15 0x8091338 in internal_catch (tag=137709664, func=0x8073938 <command_loop_2>, arg=137634620, threw=0x0) at eval.c:1315 #16 0x8072dc3 in initial_command_loop (load_me=137634620) at cmdloop.c:304 #17 0x808d0f1 in xemacs_21_2_b9_i686_pc_linux (argc=5, argv=0xbffffa14, envp=0xbffffa2c, restart=0) at emacs.c:1736 #18 0x808d865 in main (argc=5, argv=0xbffffa14, envp=0xbffffa2c) at emacs.c:2165 (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 (gdb) uname -a: Linux beaver.jprc.com 2.2.1 #2 SMP Fri Jan 29 08:22:50 EST 1999 i686 unknown ./configure '--with-pop' '--with-mule' '--with-png' XEmacs 21.2-b9 "Athena" configured for `i686-pc-linux'. Where should the build process find the source code? /home/karl/src/x/xemacs-21/xemacs-21.2.9 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 session-management. 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. 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: 21.2.9: package adding broken 25 years, 2 months

Dmitry Yaitskov

First, let me say Hi to the list (this is my first message here). >Jan> When installing a package, the package tools default to where >Jan> xemacs-base is. Unfortunately that won't work if we are installing >Jan> xemacs-base. Therefore the tools take (last late-packages). This will >Jan> typically be the subdirectory as you mentioned. > > >Jan> That should not be necessary. The most important thing is to get >Jan> xemacs-base and mule-base in the right place after that the rest >Jan> should just work. > >Ok, I moved the src directory to a different location, no longer under the >packages/ directory. In addition, xemacs-base is already installed in >/usr/local/src/xemacs/xemacs-21.2.9/packages/. Then I tried: > >M-x package-admin-add-binary-package jde-1.14-pkg.tar.gz > >This time it ended up in: > >/usr/local/src/xemacs/xemacs-21.2.9/packages/man/lisp/jde/... >/usr/local/src/xemacs/xemacs-21.2.9/packages/man/pkginfo/MANIFEST.jde >/usr/local/src/xemacs/xemacs-21.2.9/packages/man/etc/jde/... > >.../packages/man/ is still not the proper place. I installed xemacs-21.2-b9 on my NT box yesterday. Then I started installing packages via the List & Install screen. I installed some packages, exited xemacs, later installed some more. The first time they got installed into their correct places (under ...\xemacs-packages\). After that, all new packages get installed under ...\xemacs-packages\man (and late-packages has it at the end). Manually moving them up the dir tree keeps them working. -- Cheers, -Dima.

1 participants
0 comments

Re: 21.2.9: package adding broken 25 years, 2 months

Jan Vroonhof

Gregory Neil Shapiro <gshapiro(a)sendmail.org> writes: > /usr/local/src/xemacs/packages/src/xemacs-base-1.29-pkg.tar.gz ends up > installing the package in that ../packages/src/ directory instead of > ../xemacs-21.2.9/packages/ making the installed package unreachable. Unfortunately this is a design problem combined with misconception form your side [probably caused by lack of documentation]. Any subdir of a known package hierarchy NOT in packages-special-base-regexp is ALSO a package hierarchy[1]. When installing a package, the package tools default to where xemacs-base is. Unfortunately that won't work if we are installing xemacs-base. Therefore the tools take (last late-packages). This will typically be the subdirectory as you mentioned. > I believe ../packages/src/ was the current working directory I don't think it has anything to do with the current working directory, see above. > when the > package-admin-add-binary-package was executed but the command should > have used a package hierarchy. By XEmacs thinking it _is_ a package hierarchy. Moreover it should work with the packages installed there. It may be ugly, but it should work. > The same thing happens when trying to use the package-ui. I had to install > all of the packages by hand using tar. That should not be necessary. The most important thing is to get xemacs-base and mule-base in the right place after that the rest should just work. Have you read README.packages? Jan Footnotes: [1] I think this is a mistake.

2 participants
1 comments

Odd problem with 21.0.63 25 years, 2 months

Kevin Oberman

This may be some weird FOTU thing. (That's Fluke Of The Universe.) I can't easily reproduce it and it may never happen to anyone ever again. I just built 21.0.63 on Digital UNIX 4.0D using DEC C. No problems seen during the build. I then updated packages and proceeded. When I started up XEmacs, I got an error that mime-setup was not found. I checked and I found all of the .el.gz files, but no .elcs. This is true of all files .els in the tm package. Since I had gziped all of the .el files, they were not loaded/executed. I then checked the tm-1.16-pkg.tar file. All .elcs were present. I also noticed that the tm-1.16-pkg.tar and tm-1.16-pkg.tar.gz files were still in my /tmp directory. I assume that this indicates something went wrong. I had already exited XEmacs and no longer have the package installation log. All I can think of is that the deletion of old files managed to delete the new .elcs. This only happened to the tm package. All others I installed were fine. Could something have been wrong with the MANIFEST.tm? I don't see anything obvious about it. I deleted the package and re-installed it. All .elcs were present. I'm stumped. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman(a)es.net Phone: +1 510 486-8634

1 participants
0 comments

Re: Deleted packages? 25 years, 2 months

SL Baur

Gregory Neil Shapiro <gshapiro(a)sendmail.org> writes in xemacs-beta(a)xemacs.org: > The following packages were removed on the latest update: > ediff > hm--html-menus > jde ??? This must be a build mistake. I see these packages in the unpacked area where I built the last Sumo tarball, but I don't see them in the a la carte section ... O.K. There's a problem here. Ediff didn't build cleanly: While compiling toplevel forms in file /usr/home/steveb/staging/xemacs-packages/prog/ediff/ediff-diff.el: !! Symbol's value as variable is void ((x-bitmap-file-path)) Ditto for hm--html-menus. Ditto for jde. I'll have to poke around a bit to see what went wrong. hm--html-menus and jde have trivial mistakes in their Makefiles. > mailcryptng > Without mailcryptng, we are back to an outdated version of mailcrypt. > I agree mailcryptng should be dropped but only after mailcrypt is > updated to 3.5.1, the currently released version. This package hasn't been formally added.

3 participants
2 comments

Distribution Build Report for XEmacs-21.2.10 25 years, 2 months

Steven Baur

Greetings XEmacs beta testers. I am in the process of building the next distribution of XEmacs 21.2. I have tested the attached configuration. Sincerely, The XEmacs Build 'Bot -- 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 '--prefix=/usr/home/steveb/staging' '--cflags=-O' '--with-mule' '--without-x11' '--debug=no' '--error-checking=none' XEmacs 21.2-b10 "Boreas" configured for `i386-pc-bsdi3.0'. Where should the build process find the source code? /usr/home/steveb/staging/xemacs-21.2 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. movemail will use "flock" for locking mail spool files.

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