From: "Robert J. Chassell" <bob@rattlesnake.com>
Cc: bob@rattlesnake.com
Subject: Re: [SUCCESS] broken bootstrap build on 2004 Mar 18
Date: Sun, 21 Mar 2004 09:19:38 -0500 (EST) [thread overview]
Message-ID: <m1B53ne-000UMrC@rattlesnake.com> (raw)
In-Reply-To: <m1B3xJP-000UMvC@rattlesnake.com> (bob@rattlesnake.com)
Success in bootstrap build, with CVS snapshot of Sun, 2004 Mar 21
13:48 UTC
The success is not from the new snapshot, but because of changes I
made to `emacs/leim/leim-list.el'.
On 2004 Mar 18 I reported a broken bootstrap build. It turns out that
this resulted from corruption in the file `emacs/leim/leim-list.el'.
Manually, I removed a good number of
(register-input-method ... )
expressions from that file and it now loads without error and Emacs
builds.
The function `update-leim-list-file' was unable to clean up the
corruption and did not report that it was failing. I do not know how
the file got corrupted.
Also, a separate issue, I found that `make clean' removes the `emacs'
executable from `emacs/src' but that updating leim-list.el requires
that `emacs' exist. The `emacs/src/emacs-21.3.50' did exist, so I
could copy from it to `emacs' and that solved that bug.
I am not sure quite what should be done about either problem, except
to ask that someone who understands make files better than I to look
into improving the error messages, please.
For a long time I thought that the initial failure came from a bug in
the autoloads since the last messages from the build were
Loading vc-cvs...
Loading vc-arch...
Wrong type argument: stringp, nil
make[2]: *** [autoloads] Error 255
make[2]: Leaving directory `/usr/local/src/emacs/lisp'
which is misleading to someone like me.
--
Robert J. Chassell Rattlesnake Enterprises
http://www.rattlesnake.com GnuPG Key ID: 004B4AC8
http://www.teak.cc bob@rattlesnake.com
next prev parent reply other threads:[~2004-03-21 14:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-18 13:11 broken bootstrap build on 2004 Mar 18 Robert J. Chassell
2004-03-21 14:19 ` Robert J. Chassell [this message]
2004-03-23 1:13 ` [SUCCESS] " Kenichi Handa
2004-03-23 14:40 ` Robert J. Chassell
2004-03-23 15:12 ` Stefan Monnier
2004-03-23 17:44 ` Robert J. Chassell
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m1B53ne-000UMrC@rattlesnake.com \
--to=bob@rattlesnake.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.