May 1998 - XEmacs-Beta - XEmacs Mailing List Archives

[OK --but no TTY] 21.0 "San Clemente" XEmacs Lucid (beta41) on i586-pc-linux 26 years, 6 months

Larry Ayers

libc6 rather than libc5 ncurses libs and headers. I am in the midst of upgrading everything to libc6 (a Debian Linux system), and the ncurses 3.0 (libc5) and ncurses 3.4 (libc6) are both in /usr/lib. XEmacs will build with TTY support, but warnings are generated during compilation concerning the incompatibility of libc5 ncurses and libc6. The resulting executable will dump core immediately. I disabled the TTY support and all built and runs well. Does anyone have any hints on how to convince the configure script to find the right ncurses? BTW appending the contents of my old ~/.xemacs/options.el to ~/.xemacs/init.el has worked well. > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /usr/local/src/xemacs-21.0-b41/Installation: > (Output from most recent run of ./configure) uname -a: Linux liatris 2.0.34 #1 Sat May 23 22:20:59 CDT 1998 i586 unknown ./configure '--prefix=/usr/local/xemacs-beta' '--with-site-lisp' '--package-path=/usr/local/xemacs-beta/lib/xemacs/packages' '--with-toolbars=no' '--gung-ho' '--with-xpm' '--with-pop' '--with-tiff=no' '--with-gif=no' '--with-dialogs=athena' '--error-checking=none' '--debug=no' '--with-tty=no' XEmacs 21.0-b41 "San Clemente" configured for `i586-pc-linux'. Where should the build process find the source code? /usr/local/src/xemacs-21.0-b41 What installation prefix should install use? /usr/local/xemacs-beta 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 conversion. Compiling in native sound support. Compiling in support for Berkeley DB. Compiling in support for OffiX. Compiling in support for Drag'n'Drop ( OffiX ). 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. Using indexed lrecord implementation. > Contents of /usr/local/src/xemacs-21.0-b41/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\|/usr/local/src/xemacs-21\.0-b41/lisp/[^ ]+ hides " /usr/local/src/xemacs-21.0-b41/lib-src/etags.c:1849: warning: array subscript has type `char' /usr/local/src/xemacs-21.0-b41/lib-src/etags.c:1849: warning: array subscript has type `char' /usr/local/src/xemacs-21.0-b41/lib-src/etags.c:1849: warning: array subscript has type `char' /usr/local/src/xemacs-21.0-b41/lib-src/etags.c:1849: warning: array subscript has type `char' /usr/local/src/xemacs-21.0-b41/lib-src/ootags.c:1912: warning: array subscript has type `char' /usr/local/src/xemacs-21.0-b41/lib-src/ootags.c:1912: warning: array subscript has type `char' events.c:635: warning: unused variable `f' search.c:2265: warning: `prev' might be used uninitialized in this function sysdep.c:909: warning: unused variable `con' glyphs-x.c:164: warning: `qtable' might be used uninitialized in this function Purespace usage: 95168 of 1507600 (6% -- 1379k wasted). Purespace usage: 758288 of 1507600 (50% -- 731k wasted). XEmacs: Pure size adjusted, Don't Panic! I will restart the `make' make[1]: [xemacs] Error 1 (ignored) Purespace usage: 758288 of 758288 (100%). /usr/local/xemacs-beta/lib/xemacs/site-lisp/time-stamp hides /usr/local/xemacs-beta/lib/xemacs/packages/lisp/xemacs-base/time-stamp /usr/local/xemacs-beta/lib/xemacs/packages/lisp/efs/passwd hides /usr/local/xemacs-beta/lib/xemacs/packages/lisp/xemacs-base/passwd /usr/local/xemacs-beta/lib/xemacs/packages/lisp/efs/auto-save hides /usr/local/src/xemacs-21.0-b41/lisp/auto-save 3 Emacs Lisp load-path shadowings were foundLoading /usr/local/src/xemacs-21.0-b41/lisp/auto-autoloads... (file auto-autoloads.el is newer)

1 participants
0 comments

Re: Sounds -- .au, .wav, or both? 26 years, 6 months

Jan Vroonhof

SL Baur <steve(a)xemacs.org> writes: > Is there any platform that absolutely requires .au and cannot handle > .wav? I am not sure, but probably Sun. I am also not sure our implementation of NAS can handle .wav. .au is the standard audio format under Unix. Look at this snippet from 'man nas' Due to the nature of the file formats, only the Sun/NeXT file format can be piped through standard input and/or standard output. The convention for specifying standard input or standard output is to use a hyphen ("-") as the file name. Jan

1 participants
0 comments

Re: objectives for 21.0? 26 years, 6 months

SL Baur

[I'm widening the response to this reasonable question to xemacs-beta]. Andy Piper <andyp(a)parallax.co.uk> writes: > Steve, > I'm just wondering what the objectives for 21.0 are. Its just that we have > most of the pieces in place for a really kick-ass mswindows version of > XEmacs. However there are still a few major outstanding bugs and some bits > missing - mainly the rest of the image code. Do you want to target 21.0 as > the first official mswindows release, or has it just been too long between > releases? MS Windows support is a priority for 21.0, make it so, but please exercise due haste in putting it together.

3 participants
2 comments

[Success] 21.0 "San Clemente" XEmacs Lucid (beta41) on i386-pc-cy gwin32 26 years, 6 months

Michael Hill

With Andy's patches and -O2 (changed manually -- I take it it's more easily done with configure). The toolbar looks great. Still no dialog boxes though. Mike > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /binary/xemacs-21.0-b41/Installation: > (Output from most recent run of ./configure) uname -a: CYGWIN32_NT DILBERT 4.0 19.1 i686 unknown ./configure '--site-includes=/usr/local/include' XEmacs 21.0-b41 "San Clemente" configured for `i386-pc-cygwin32'. Where should the build process find the source code? /binary/xemacs-21.0-b41 What installation prefix should install use? /usr/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 -O3 -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? x11 Where do we find X Windows header files? /usr/X11R6.3/include Where do we find X Windows libraries? /usr/X11R6.3/lib Additional header files: /usr/local/include Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for GIF image conversion. Compiling in support for JPEG image conversion. Compiling in support for PNG image conversion. Compiling in support for TIFF image conversion. Compiling in support for GNU DBM. Compiling in support for ncurses. Compiling in File coding support. Compiling in support for OffiX. Compiling in support for Drag'n'Drop ( OffiX ). Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Athena dialog boxes. 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: --------------------------------------------------------- > /binary/xemacs-21.0-b41/beta.err does not exist!

2 participants
1 comments

b41 cygwin suckfest, gcc -O3 -> -O2 *please* 26 years, 6 months

Andy Piper

b41 is really turning into a suckfest under cygwin for me. Martin, gcc -O3 loses big time under cygwin. Can we possibly undo this change? Surely people can bump the optimization level if they really want it? I was getting all sorts of bogues crashes in the extent code with -O3 (i.e. I couldn't get XEmacs up and running) which all went away with -O2. I suspect that a couple of the other fixes I posted were related to gcc -O3. andy --------------------------------------------------------------------------- " .sigs are like your face - rarely seen by you and uglier than you think" Dr Andy Piper, Technical Architect, Parallax Solutions Ltd mail: andyp(a)parallax.co.uk web: www.parallax.co.uk/~andyp

2 participants
2 comments

[Success] 21.0 "San Clemente" XEmacs Lucid (beta41) on hppa1.1-hp-hpux11.00 26 years, 6 months

Marcus Thiessel

>From scratch with no problems. > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /opt/src/xemacs-21.0-b41/Installation: > (Output from most recent run of ./configure) uname -a: HP-UX tmbbwtx B.11.00 A 9000/720 16954192 two-user license ./configure 'hppa1.1-hp-hpux11.00' '--dynamic=no' '--prefix=/usr/local/xemacs' '--with-x' '--with-dialogs=motif' '--with-xface=yes' '--with-tty=yes' '--x-includes=/usr/include/Motif1.2_R6 -I/usr/include/X11R6' '--x-libraries=/usr/lib/Motif1.2_R6 -L/usr/lib/X11R6' '--with-database=dbm' '--with-pop' '--mail-locking=lockf' '--site-includes=/usr/contrib/include -I/usr/local/include' '--error-checking=none' '--extra-verbose' '--site-libraries=/usr/contrib/lib -L/usr/local/lib' '--with-sound=no' '--with-xmu' '--with-mule=yes' '--with-cde=yes' '--with-session' '--with-tooltalk=yes' '--with-gcc=no' '--with-gnu-make=no' '--gung-ho' '--package-path=/opt/src/packages' '--cflags=+DA1.1 +DD32 +O2 +Onolimit +Odataprefetch +Oentrysched +Oprocelim +Olibcalls' XEmacs 21.0-b41 "San Clemente" configured for `hppa1.1-hp-hpux11.00'. Where should the build process find the source code? /opt/src/xemacs-21.0-b41 What installation prefix should install use? /usr/local/xemacs What operating system and machine description files should XEmacs use? `s/hpux11.h' and `m/hp800.h' What compiler should XEmacs be built with? cc -Ae +DA1.1 +DD32 +O2 +Onolimit +Odataprefetch +Oentrysched +Oprocelim +Olibcalls 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/include/Motif1.2_R6 -I/usr/include/X11R6 /usr/contrib/X11R6/include Where do we find X Windows libraries? /usr/dt/lib /usr/lib/Motif1.2_R6 -L/usr/lib/X11R6 /usr/contrib/X11R6/lib Additional header files: /usr/contrib/include -I/usr/local/include Additional libraries: /usr/contrib/lib -L/usr/local/lib 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 support for TIFF image conversion. Compiling in support for DBM. Compiling in Mule (multi-lingual) support. Compiling in XIM (X11R5+ I18N input method) support. Using Motif to provide XIM support. Compiling in support for CDE. Compiling in support for ToolTalk. Compiling in support for OffiX. Compiling in support for Drag'n'Drop ( OffiX CDE ). Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Motif dialog boxes. Compiling in DLL support. movemail will use "lockf" for locking mail spool files. Using POP for mail access Using Lisp_Objects with minimal tagbits. Using indexed lrecord implementation. Compiling in extra code for debugging. Compiling in code for checking XEmacs memory usage. > /opt/src/xemacs-21.0-b41/beta.err does not exist!

1 participants
0 comments

Problem with menus was Red Gnus 26 years, 6 months

Rebecca Ore

It appears that Red Gnus caused the menus to disappear. I removed it and the menus were fine on Beta 41 run installed as well as Beta 40 run in place. Can we perhaps take this out of the packages? Still don't know what the deal is with the uuencode problem, but Red Gnus didn't handle that any better. -- Rebecca Ore

1 participants
0 comments

Re: A couple of rebuilds later.... 26 years, 6 months

SL Baur

Rebecca Ore <rebecca.ore(a)op.net> writes: > What's the deal? If I'm not doing something wrong, this is a > serious problem here for the users who do go to the menus. This isn't going to (or shouldn't) affect new users. Grepping for custom-put in all custom-load.el files will quickly tell you where it's coming from. > (1) (error/warning) Error in menubar filter: (void-function > custom-put). > Anyone got a patch or explanation for this? You have a very old package in your package path somewhere. The likeliest candidate is Gnus 5.4 -- its package on the FTP site never got updated to the current interface. Remove the old, install the new and you should be O.K.

1 participants
0 comments

A couple of rebuilds later.... 26 years, 6 months

Rebecca Ore

I still don't have a menu for Options>Customize>Emacs> This continues to be the error-message. I removed all the files in the Xemacs-21.0 directory except for info before rebulding this time. I also redownloaded and replaces the xemacs.base package. What's the deal? If I'm not doing something wrong, this is a serious problem here for the users who do go to the menus. (1) (error/warning) Error in menubar filter: (void-function custom-put). Anyone got a patch or explanation for this? -- Rebecca Ore

3 participants
2 comments

Re: Redisplay while evaluating Lisp code 26 years, 6 months

Hrvoje Niksic

"Kirill M. Katsnelson" <kkm(a)kis.ru> writes: > The message queue is drained to see if there are any C-g's typed. > The redisplay behavoir you mention appears to be a side effect of > this mechanism... A great side-effect, I'd say! > There is another consequence, and I do not know is it good or > bad. To see it, start Task Manager (C+Sh+ESC anywhere in Windows), > and click on the "Performance" tab. You will see CPU meter, staying > at 100% when (while t) is looping. OK. > Now, press left button on the frame side or corner, as if you are > gonig to drag it. CPU drops down to 0. While you resize the frame, > real redisplay() is called, to update frame contents. > > This means that rediplay may get called any time QUITP is executed. This, in itself, should not be too bad. It is generally expected that, with QUIT, anything is possible. > More to this, resizing frame may cause frame windows to be deleted, How come? -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- Thou Who might be our Father Who perhaps may be in Heaven... -- Roger Zelazny

2 participants
1 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 May 1998