May 1998 - XEmacs-Beta - XEmacs Mailing List Archives

[FAILURE] XEmacs 21.0-beta38 on MkLinux 26 years, 6 months

Stephen R. Anderson

downloaded fresh sources & elc tarball. Make stopped with: [....] gcc -c -g -O2 -Wall -Wno-implicit -Wno-switch -Demacs -I. -DHAVE_CONFIG_H -I/usr/X11/include floatfns.c floatfns.c:934: warning: `struct exception' declared inside parameter list floatfns.c:934: warning: its scope is only this definition or declaration, floatfns.c:934: warning: which is probably not what you want. floatfns.c:935: conflicting types for `matherr' /usr/include/math.h:118: previous declaration of `matherr' floatfns.c: In function `matherr': floatfns.c:943: dereferencing pointer to incomplete type floatfns.c:944: dereferencing pointer to incomplete type floatfns.c:946: dereferencing pointer to incomplete type floatfns.c:948: dereferencing pointer to incomplete type make[1]: *** [floatfns.o] Error 1 make[1]: Leaving directory `/usr/local/SRC/Xemacs/xemacs-21.0-b38/src' make: *** [src] Error 2 Installation included below. Compiler is egcs-1.02. Betas 34-36 built ok (I didn't try 37). --Steve Anderson uname -a: Linux bloch 2.0.33-osfmach3 #15 Wed Mar 4 19:09:42 EST 1998 ppc unknown ./configure '--with-gnu-make' '--with-offix=no' '--extra-verbose' '--cflags=-g -O2 -Wall -Wno-implicit -Wno-switch' XEmacs 21.0-b38 "Repartida" configured for `powerpc-unknown-linux'. Where should the build process find the source code? /usr/local/SRC/Xemacs/xemacs-21.0-b38 What installation prefix should install use? /usr/local What operating system and machine description files should XEmacs use? `s/linux.h' and `m/powerpc.h' What compiler should XEmacs be built with? gcc -g -O2 -Wall -Wno-implicit -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/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 JPEG image conversion. Compiling in support for PNG image conversion. Compiling in support for TIFF image conversion. 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 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: ---------------------------------------------------------

1 participants
1 comments

Re: More package questions 26 years, 6 months

John Jones

>>>>> Olivier Galibert writes: > On Wed, May 06, 1998 at 06:42:06AM -0700, JJ wrote: >> It is only supposed to update the packages you have, and decides >> which to update based on package-get-base. Currently, it may end >> up installing packages you do not have if they are required by >> packages you do have. I think that should be changed since >> sometimes package A is officially required by package B, but there >> are no real problems in running B without A. > In *this* case what we have to fix is the dependency. We should > have a "dependency overrride" flag, but *not* set it by default. Yes, we should fix dependencies which are not required. But this should be independent of package-get-update-all. If user A initially gets packages using package-get-all, he will fetch dependent packages as well. If user B thinks he is smarter than the dependency system, he can fetch get only the ones he wants with package-get (or plain old ftp). Either way, the user is in control of whether dependent packages are automatically fetched. Now these two users decide to update their packages with package-get-update-all. Currently user B ends up fetching the dependent packages he was intentionally did not download to start with. I think that conflicts with the principal of least surprise. If package-get-update-all is (trivially) changed to not go after dependent packages, then it acts as expected for both user A and user B. It works for user A because he has dependent packages, and if package-get-base shows a newer version of one of those has come out, package-get-update-all will still get that newer version. John Jones jj(a)asu.edu

2 participants
1 comments

[partial success] 21.0 "Repartida" XEmacs (beta38) i386 NT4.0 26 years, 6 months

Peter Windle

Well, finally managed to get around to building XEmacs on NT. Build was native windows with XPM support. Simple file editing seems fine, so far. M-x shell gives me a usable DOS shell with a couple of minor glitches; communication with the shell seems a little prone to lossage at times. An attempt at SMTP mail was a complete non-starter; looked like a zero-page "read". Completely reproducible, too. Unfortunately, the debugger refused to start from the "cancel". I'll be making an attempt to run xemacs from devstudio to provoke that way. Does the NT build with MULE by default? ClearCase support is a non-starter so far. vc-cc attempts to run "/usr/atria/bin/cleartool"; after I'd patched this to `(substitute-in-file-name "$ATRIA_HOME/bin/cleartool.exe")' cleartool refused to start (jammed on "starting cleartool..."). This may be something to do with my flaky process communications, I suppose. I may, time permitting, have a go at fixing this up 'cos it'd be rather handy. Cheers, -- pete "..."

1 participants
1 comments

Re: [PATCH] efs-kerberos typo 26 years, 6 months

Hrvoje Niksic

Olivier Galibert <galibert(a)pobox.com> writes: > On Wed, May 06, 1998 at 11:39:36AM -0400, Raymond Toy wrote: > > Should this have been sent to the patches mailing list? Are all > > patches supposed to go there now? > > Yep. For Steve's sake, you should add a Changelog entry too, please. Not only Steve's. When I locate a bug to a particular part of code, I always skim the ChangeLogs to see if that code has been tinkered with lately. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- Predestination was doomed from the start.

1 participants
0 comments

[PATCH] efs-kerberos typo 26 years, 6 months

Raymond Toy

Here is a patch for a typo in efs-kerberos. Dosn't help me get efs working via kerberos for me though. Bummer Should this have been sent to the patches mailing list? Are all patches supposed to go there now? Ray *** efs-kerberos.el~ Sat Mar 14 05:18:18 1998 --- efs-kerberos.el Wed May 6 10:12:57 1998 *************** *** 87,93 **** (setq efs-kerberos-passwd-failed nil efs-kerberos-passwd-sent nil efs-kerberos-output "") ! (condition-case nil (delete-process "*efs kerberos*") (eror nil)) (let* ((program (or (nth 3 efs-gateway-type) "kinit")) (args (nth 4 efs-gateway-type)) (proc (apply 'start-process --- 87,93 ---- (setq efs-kerberos-passwd-failed nil efs-kerberos-passwd-sent nil efs-kerberos-output "") ! (condition-case nil (delete-process "*efs kerberos*") (error nil)) (let* ((program (or (nth 3 efs-gateway-type) "kinit")) (args (nth 4 efs-gateway-type)) (proc (apply 'start-process

2 participants
1 comments

bug in fsf-compat package 26 years, 6 months

Andy Piper

thingatpt.el is read only in the tar - it should be read/write by me. andy

1 participants
0 comments

Re: [bug] buffer-syntactic-context hosed by `(' at beginning of line 26 years, 6 months

Jan Vroonhof

Hrvoje Niksic <hniksic(a)srce.hr> writes: > I assume the bug is due to an optimization in font-lock.c, but I am > not sure how to fix it. New data point. Using the cc-mode version from 20.4 in 21.x "solves" it. Jan

1 participants
0 comments

RE: Basic package question 26 years, 6 months

"Zow" Terry Brugger

Thanks for your help Itay! Terry -----Original Message----- From: Itay Ben-Yaacov [SMTP:pezz＠www-mail.huji.ac.il] well, being a "newbie" myself, i'll try to help: all those empty directories should be very full, so something is wrong. if i am not mistaken, "make install" under cygnus would fail till andy's install script a few betas back, since it would try to install executables without the .exe extension. since it looks like you're trying b30, maybe upgrading a little could help. you are 8 betas in the past :) as for the location of the packages: maybe there is an 'official' method, but after not too many try-and-fails i found that installing under PREFIX/lib/xemacs-21.0-b??/packages (which does not exist) works just fine. hope i've been of some help :) -- Itay Ben-Yaacov

1 participants
0 comments

Re: More package questions 26 years, 6 months

Hrvoje Niksic

Olivier Galibert <galibert(a)pobox.com> writes: > On Wed, May 06, 1998 at 06:42:06AM -0700, John W. Jones wrote: > > It is only supposed to update the packages you have, and decides which > > to update based on package-get-base. Currently, it may end up > > installing packages you do not have if they are required by packages > > you do have. I think that should be changed since sometimes package A > > is officially required by package B, but there are no real problems in > > running B without A. > > In *this* case what we have to fix is the dependency. We should have a > "dependency overrride" flag, but *not* set it by default. Or, maybe we should do what Debian does, which is distinguish between "suggesting" a package and "requiring" it. When package A requires package B, it means it will be useless without it. OTOH, when package A suggests package B, it means that it will run without it, but (say) with less features. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- Be nice to your kids. They'll choose your nursing home.

2 participants
1 comments

packages again 26 years, 6 months

Andy Piper

Ok, my package updates are *not* (really, really) going into the package path I specified when I built emacs. They may not be going anywhere at all, how do I debug this? I have --prefix=/usr/gnu and --package-path=/usr/gnu/lib/xemacs/packages For instance the mail-lib that was downloaded was version 1.12 but the _pkg.el for mail-lib in /usr/gnu/lib/xemacs/packages/lisp/mail-lib is v 1.09. andy

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