March 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Build failure: 21.2.13 25 years, 8 months

Marat Boshernitsan

Installation file is attached. Marat. % gcc -v Reading specs from /usr/misc/lib/gcc-lib/i686-pc-linux-gnu/egcs-2.91.57/specs gcc version egcs-2.91.57 19980901 (egcs-1.1 release) % gmake cd ./lib-src && gmake --no-print-directory all gmake[1]: Nothing to be done for `all'. cd ./lwlib && gmake --no-print-directory all gmake[1]: Nothing to be done for `all'. cd ./src && gmake --no-print-directory all EMACSBOOTSTRAPLOADPATH="/home/cs/harmonia/xemacs-21.2.13/src/../lisp/:/home/cs/harmonia/xemacs-21.2.13" EMACSBOOTSTRAPMODULEPATH="/home/cs/harmonia/xemacs-21.2.13/src/../modules/:/home/cs/harmonia/xemacs-21.2.13" ./temacs -batch -l /home/cs/harmonia/xemacs-21.2.13/src/../lisp/update-elc.el Loading /home/cs/harmonia/xemacs-21.2.13/src/../lisp/update-elc.el... Loading very-early-lisp... (2124) Loading find-paths.el... (13900) Loading packages.el... (24336) Loading setup-paths.el... (6832) Loading dump-paths.el... (0) Loading /home/cs/harmonia/xemacs-21.2.13/src/../lisp/dumped-lisp.el... (136) "Error: Library file backquote not found" rm -f ../lib-src/DOC; \ EMACSBOOTSTRAPLOADPATH="/home/cs/harmonia/xemacs-21.2.13/src/../lisp/:/home/cs/harmonia/xemacs-21.2.13" EMACSBOOTSTRAPMODULEPATH="/home/cs/harmonia/xemacs-21.2.13/src/../modules/:/home/cs/harmonia/xemacs-21.2.13" ./temacs -batch -l /home/cs/harmonia/xemacs-21.2.13/src/../lisp/make-docfile.el -- \ -o ../lib-src/DOC -d /home/cs/harmonia/xemacs-21.2.13/src -i ../lib-src/../site-packages \ abbrev.c alloc.c blocktype.c buffer.c bytecode.c callint.c callproc.c casefiddle.c casetab.c chartab.c cmdloop.c cmds.c console.c console-stream.c data.c device.c dired.c doc.c doprnt.c dynarr.c editfns.c elhash.c emacs.c eval.c events.c debug.c unexelf.c dgif_lib.c gif_io.c menubar.c scrollbar.c dialog.c toolbar.c menubar-x.c scrollbar-x.c dialog-x.c toolbar-x.c gui-x.c inline.c linuxplay.c console-tty.c device-tty.c event-tty.c frame-tty.c objects-tty.c redisplay-tty.c cm.c terminfo.c gpmevent.c event-unixoid.c database.c sysdll.c emodules.c process-unix.c event-stream.c extents.c faces.c fileio.c filemode.c floatfns.c fns.c font-lock.c frame.c general.c getloadavg.c glyphs.c glyphs-eimage.c glyphs-widget.c gui.c hash.c imgproc.c indent.c insdel.c intl.c keymap.c line-number.c lread.c lstream.c macros.c marker.c md5.c minibuf.c objects.c opaque.c print.c process.c profile.c rangetab.c redisplay.c redisplay-output.c regex.c search.c signal.c sound.c specifier.c strftime.! c symbols.c syntax.c sysdep.c undo.c balloon_help.c balloon-x.c console-x.c device-x.c event-Xt.c frame-x.c glyphs-x.c objects-x.c redisplay-x.c xgccache.c xselect.c widget.c window.c free-hook.c ralloc.c Loading /home/cs/harmonia/xemacs-21.2.13/src/../lisp/make-docfile.el... Loading very-early-lisp... (2124) Loading find-paths.el... (13900) Loading packages.el... (24300) Loading setup-paths.el... (6832) Loading dump-paths.el... (0) Loading /home/cs/harmonia/xemacs-21.2.13/src/../lisp/dumped-lisp.el... (136) Spawning make-docfile ... Spawning make-docfile ...done EMACSBOOTSTRAPLOADPATH="/home/cs/harmonia/xemacs-21.2.13/src/../lisp/:/home/cs/harmonia/xemacs-21.2.13" EMACSBOOTSTRAPMODULEPATH="/home/cs/harmonia/xemacs-21.2.13/src/../modules/:/home/cs/harmonia/xemacs-21.2.13" ./temacs -batch -l /home/cs/harmonia/xemacs-21.2.13/src/../lisp/loadup.el dump Loading /home/cs/harmonia/xemacs-21.2.13/src/../lisp/loadup.el... Using load-path (/home/cs/harmonia/xemacs-21.2.13/src/../lisp/ /home/cs/harmonia/xemacs-21.2.13) Using module-load-path (/home/cs/harmonia/xemacs-21.2.13/src/../modules/ /home/cs/harmonia/xemacs-21.2.13) Loading very-early-lisp... (2124) Loading /home/cs/harmonia/xemacs-21.2.13/src/../lisp/dumped-lisp.el... (188) Loading /home/cs/harmonia/xemacs-21.2.13/lisp/backquote.elc... (2936) Loading /home/cs/harmonia/xemacs-21.2.13/lisp/bytecomp-runtime.elc... (4696) Loading /home/cs/harmonia/xemacs-21.2.13/Installation.el... (36) Loading /home/cs/harmonia/xemacs-21.2.13/lisp/find-paths.elc... (5668) Loading /home/cs/harmonia/xemacs-21.2.13/lisp/packages.elc... (10484) Loading /home/cs/harmonia/xemacs-21.2.13/lisp/setup-paths.elc... (3668) Loading /home/cs/harmonia/xemacs-21.2.13/lisp/dump-paths.elc... (0) Load file subr: not found Fatal error during load, aborting gmake[1]: [xemacs] Error 1 (ignored) gmake[1]: *** [xemacs] Error 1 gmake: *** [src] Error 2

1 participants
0 comments

Re: Better Installataion file and `describe-installation' under Windows 25 years, 8 months

Adrian Aichner

>>>>> "Jonathan" == Jonathan Harris <jhar(a)tardis.ed.ac.uk> writes: Jonathan> Adrian Aichner wrote: >> >> When I found that xemacs.mak was broken in 21.2-b13 I decided a >> redesign was in order to create a complete Installation file in favor >> of the CONF_REPORT which goes to STDOUT of nmake. Jonathan> This is certainly nicer than my hack, but unfortunately hangs while Jonathan> loading lisp\Installation.el during dump for me on Windows 95. Hi Jonathan, I probably goofed! How do I replace CONTROL-Ms with nothing in a way that would not interfere with MULE either? How do I do this right? Installation.el: Installation ＠type > Installation.el << (setq Installation-string (replace-in-string " <<NOKEEP type Installation >> Installation.el type >> Installation.el << " "CONTROL-M" "")) <<NOKEEP I'll devise a new patch if you help me through this. >> ＠＠ -1022,6 +908,18 ＠＠ >> $(LIB_SRC)\make-docfile.exe -a $(DOC) -d $(TEMACS_SRC) > Jonathan> $(DOC_SRC8) >> $(LIB_SRC)\make-docfile.exe -a $(DOC) -d $(TEMACS_SRC) > Jonathan> $(DOC_SRC9) >> +Installation.el: Installation >> + ＠type > Installation.el << >> +(setq Installation-string >> + (replace-in-string >> + " >> +<<NOKEEP >> + type Installation >> Installation.el >> + type >> Installation.el << >> +" >> + "" "")) Should be " " "")) What did I do wrong? After patching xemacs.mak on Windows 95, do you still have the C-m above? Regards, Adrian Jonathan> ^^ ^^ Jonathan> This is the problem. (replace-in-string foo "" "") hangs. >> +<<NOKEEP >> + >> $(LISP)\Installation.el: Installation.el >> copy Installation.el $(LISP) Jonathan> Jonathan. Jonathan> -- Jonathan> Jonathan Harris | jhar(a)tardis.ed.ac.uk Jonathan> London, England | Jonathan.Harris(a)symbian.com -- Adrian Aichner Teradyne GmbH, European Design Center Integra Test Division 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

3 participants
2 comments

Re: (old?) question: why is help-selects-help-window non-nil by default? 25 years, 8 months

SL Baur

John H Palmieri <John.H.Palmieri.2(a)nd.edu> writes in xemacs-beta(a)xemacs.org: > I have a few questions about the variable help-selects-help-window: > why is it non-nil by default? When did XEmacs start behaving this > way? I don't recall, it has been set this way for as long as the source code has been under CVS (from December 1996). > I am curious about the reasons for this difference. (I also couldn't > find anything about the change in etc/NEWS or etc/OONEWS. Did I just > miss it, or is it even older than that?) Those files would be too recent. > (It recently occurred to me that this behavior ought to be > customizable, which of course it is, so at least now I don't have to > be confused by *this* difference between GNU Emacs and XEmacs as I > switch from one to the other.) Yup. This is another default I don't like at all.

1 participants
0 comments

Re: extent-data in bbdb-xemacs.el 25 years, 8 months

Les Schaffer

Gleb Arshinov sez: > This bug has been fixed in the later versions of bbdb, so what's > actually needed is an upgrade to the latest version. using bbdb-version 2.00.02 (the latest bbdb package from xemacs.org packages directory) bbdb-1.07-pkg.tar.gz 275 Kb Tue Feb 2 05:49:00 1999 ----- trying bbdb functions: Recent minibuffer messages (most recent first): Symbol's function definition is void: extent-data ----- can someone post the fix? i gather from the previous poster its small and painless. thanks les schaffer

1 participants
0 comments

Re: Paren expression staying permanently highlighted? 25 years, 8 months

Reid Rivenburgh

>>>>>> "Reid" == Reid Rivenburgh <reid(a)ldap-green.lanl.gov> writes: >> [problem with paren highlighting...] > Try starting xemacs -vanilla and see if you still see this problem. Okay. The problem is that things are fine when I first start up, and then something eventually triggers the problem. Running -vanilla until it happens (if it does!) won't be much fun, but I'll give it a shot. Reid

1 participants
0 comments

Re: VM bug in 21.0.66 and sumo-03-12 25 years, 8 months

Raymond Toy

>>>>> "SL" == SL Baur <steve(a)xemacs.org> writes: SL> Raymond Toy <toy(a)rtp.ericsson.se> writes in xemacs-beta(a)xemacs.org: >> One of the users here has run into a problem with the VM in the latest >> sumo (03-12) tarball and 21.0.66. >>> From "xemacs -vanilla" and an empty .vm file, M-x vm produces an >> error. SL> Because I am a very dumb California blonde. Sorry about that. Please SL> fetch vm-1.19-pkg.tar.gz from the FTP site and give that a try. It SL> should work a bit better. Got it and my colleague tried it out. Everything is fine now! Ray P.S. I'm been getting an occasional bounced mail from xemacs.org saying there was a remote protocol error and the address had permanent fatal errors (xemacs-beta(a)xemacs.org and steve(a)xemacs.org). Is this my fault or xemacs.org?

1 participants
0 comments

ispell stangeness 25 years, 8 months

Andrew S. Howell

I mailed the other day about "Strange behavior with MULE and punctuation on 21.0.65,Solaris 2.5.1." It turns out this si a problem in ispell. If you do M-x ispell-minor-mode and then type: .SPC where SPC, is, you guessed a space, then you buffer will look like: . ^--- cursor I tried to trace what was happening by doing debug-on-entry ispell-minor-check, but I got lost in the bowles of ispell-word. ispell-minor-check is bound to space. The code in question is: (save-window-excursion (save-restriction (narrow-to-region (save-excursion (forward-line -1) (point)) (point)) (ispell-word nil t)))) (command-execute (key-binding (this-command-keys))))) I'm not adept enought with elisp to figure out much else from here. I checked ispell.el, and it had not changed since 21.0.63, and I don't remember it being a problem then. I use ispell-minor-mode for email, so I'm sure I would have noticed. I tried it with -no-init-file, just to make sure that I was not messing something up in my .emacs. No luck. Any help in how to debug this further would be greatly apreciated. Thanks, Andy

1 participants
1 comments

Re: Customize bug? 25 years, 8 months

Didier Verna

Per Abrahamsen writes: >> It depends. I think the *default* customize settings (such as in `defface' >> forms) should be overridden with X resources. On the other hand, >> hand-changed customize settings (such as with `M-x customize-face') should >> override X resources. Per> I'm not sure that is conceptually right. X resources gives the ability to Per> make "per display" customizations, while customize only support Per> customizations based on some broad display categories. The most specific Per> should win. E.g. you may want to select different font sizes for Per> different sized monitors , something customize cannot know about. When faced with an existing specifier-like mechanism[1] we often forget that the problems they solve is not really restricted to their domain. What's interesting in the X resources mechanism is not that you can specify on a per-display basis, but that for such or such display, you actually know that you'll get a BW or color, big or small screen etc. However, even if X provides a mechanism to cope with this variety of displays, those problems are not specific to X. For instance, some terminals support colors, some don't. We could also support the background pixmap resource in Eterm. But now, there's Xt and we're tempted to use it. It's a shame because it's limited, and it makes it harder for us to think of the design of a more generic specification model. What's missing now is a generic way of saying "I want this size, this look and this color. If I happen to work on BW, let's do this..." In other words, IMHO, if with X you can manage to get the size you want on all screens, but not with Custom, let's not conclude that X should override Custom. Let's conclude that the user needs a higher way of setting the font size, and X resources will be a "backend" for this model when running under X. I'm not saying this can be done in a few days :-) Footnotes: [1] The X resources mechanism is such, in the sense that you can "specify" on a per-display, per-langage, per-screen ... basis. -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / E.N.S.T. INF C201.1 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 73 46 75634 Paris cedex 13 Fax. (33) 01 45 81 31 19

1 participants
0 comments

Re: Customize bug? 25 years, 8 months

William M. Perry

Per Abrahamsen <abraham(a)dina.kvl.dk> writes: > Hrvoje Niksic <hniksic(a)srce.hr> writes: > > > The unbundled code had, however, other problems; for instance, I > > recall that you couldn't dump XEmacs with code that used `defface'. > > Yep. I suspect it is still the case for Emacs. It is probably less > of a problem in the Emacs cathedral than in the XEmacs bazaar. > > > True. font.el provides some of the needed functionality, but it's way > > too naive to be taken seriously (no offense Bill!) Not to mention > > that the redisplay doesn't support merging of font properties. > > Right, but font.el gives you the ability to write code that works as well > as the current display code will allow, and that will work better (with > no changes to the code) as the display model grows more powerful. > > > It depends. I think the *default* customize settings (such as in > > `defface' forms) should be overridden with X resources. On the other > > hand, hand-changed customize settings (such as with `M-x customize-face') > > should override X resources. > > I'm not sure that is conceptually right. X resources gives the ability > to make "per display" customizations, while customize only support > customizations based on some broad display categories. The most specific > should win. E.g. you may want to select different font sizes for > different sized monitors , something customize cannot know about. But with a decent font model, you could say 'I want a 1inch high font' and it would work everywhere, no matter your monitor size or pixel resolution. :) -Bill P.

1 participants
0 comments

Font model for XEmacs (was Re: Customize bug?) 25 years, 8 months

William M. Perry

Hrvoje Niksic <hniksic(a)srce.hr> writes: > Per Abrahamsen <abraham(a)dina.kvl.dk> writes: > > > > In FSF Emacs this is trivial since customize exactly matches the > > > FSF font model. Adapting customize to more powerful font models > > > (whether for XEmacs or for FSF 20.5+) without overly complicating > > > the interface will be a challenge. > > > > There is no XEmacs font model, which is the only hard thing about > > it. > > True. font.el provides some of the needed functionality, but it's way > too naive to be taken seriously (no offense Bill!) Not to mention that > the redisplay doesn't support merging of font properties. I totally agree. If anyone out there wants to help take font.el and move it down into the display engine, speak up! I don't have the detailed redisplay knowledge to do the work. It won't be trivial either, but we can probably borrow some of the Emacs 21.x redisplay logic for the font-property merging. -Bill P.

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