From: Alan Mackenzie <acm@muc.de>
To: emacs-devel@gnu.org
Subject: update Hades
Date: Sat, 6 Oct 2007 14:20:36 +0000 [thread overview]
Message-ID: <20071006142036.GA2082@muc.de> (raw)
Hi, Emacs!
I've just done a update on the CVS trunk. It doesn't build, though I've
tried many things to get it going:
I tried the usual INSTALL.CVS recipe: ./configure; make; cd lisp; make
recompile EMACS=../src/emacs; cd ..; make
(i) I had to download the new ../doc directory in. No complaints about
this. But for anybody else who needs to do this, the recipe is "cvs
update -d".
(ii) It worked up until "make recompile EMACS=../srce/emacs". This
failed for the lack of (defmacro with-demoted-errors). I solved this by
rebytecompiling subr.el by hand. I think the bug here is that "make
recompile" doesn't first recompile the "critical"[*] files first and
then load them. Our ..../lisp/Makefile doesn't reflect the dependencies
in our files.el.
After hand-compiling subr.el, "make recompile ..." worked.
[*] Not sure which files count as "critical", but subr.el is certainly
amongst them. Probably simple.el, too.
(iii) cd ..; make. This fails just after dumping the emacs executable,
giving these messages:
Dumping under names emacs and emacs-23.0.50.6
1153925 pure bytes used
./emacs -q -batch -f list-load-path-shadows
Symbol's function definition is void: encoded-kbd-setup-display
(defun encoded-kbd-setup-display...) is in
..../lisp/international/encoded-kb.el. I've byte compiled this by hand,
but this doesn't help. Should encoded-kb.el perhaps be in loadup.el?
Or do we need an autoload?
Anybody got a quick workaround for this encoded-kbd-setup-display
problem?
--
Alan Mackenzie (Ittersbach, Germany).
next reply other threads:[~2007-10-06 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-06 14:20 Alan Mackenzie [this message]
2007-10-06 15:18 ` update Hades Dan Nicolaescu
2007-10-06 18:16 ` Alan Mackenzie
2007-10-06 20:02 ` Andreas Schwab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071006142036.GA2082@muc.de \
--to=acm@muc.de \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).