unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Bill Wohler <wohler@newt.com>
Cc: emacs-pretest-bug@gnu.org, emacs-devel@gnu.org
Subject: Re: emacs-unicode-2: bootstrap failed due to recent mh-e changes
Date: Fri, 31 Mar 2006 17:06:59 -0800	[thread overview]
Message-ID: <21442.1143853619@olgas.newt.com> (raw)
In-Reply-To: <200604010052.k310q8xm015692@jane.dms.auburn.edu>

Luc Teirlinck <teirllm@dms.auburn.edu> wrote:

> Bill Wohler wrote:
> 
>    If an update doesn't resolve the problem, please remove
>    lisp/mh-e/*.elc and try again.
> 
> All of that is apparently not sufficient to solve the problem.  Still
> same error message:
> 
> Compiling /home/teirllm/emacscvsdir/emacs/lisp/./mh-e/mh-e.el
> 
> In toplevel form: mh-e/mh-e.el:997:1:Error: Symbol's function
> definition is void: mh-strip-package-version
> make[2]: *** [compile] Error 1
> make[2]: Leaving directory `/home/teirllm/emacscvsdir/emacs/lisp'
> make[1]: *** [bootstrap-build] Error 2
> make[1]: Leaving directory `/home/teirllm/emacscvsdir/emacs'
> make: *** [bootstrap] Error 2

I do not understand this. If you remove mh-e/*.elc, it compiles. If you
just touch mh-e/mh-e.el and compile it fails.

I found that making mh-strip-package-version a macro fixes the error
(which I just checked in). If someone would like to explain why this is
so, I would listen eagerly. Is this fixing the problem, or merely
masking the symptoms?

Color me baffled by the compiler (again).

-- 
Bill Wohler <wohler@newt.com>  http://www.newt.com/wohler/  GnuPG ID:610BD9AD
Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian!
If you're passed on the right, you're in the wrong lane.

  reply	other threads:[~2006-04-01  1:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-31 16:14 emacs-unicode-2: bootstrap failed due to recent mh-e changes Zhang Wei
2006-03-31 16:29 ` Randal L. Schwartz
2006-03-31 18:48 ` Bill Wohler
2006-04-01  0:52   ` Luc Teirlinck
2006-04-01  1:06     ` Bill Wohler [this message]
2006-04-01  3:51       ` Luc Teirlinck

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=21442.1143853619@olgas.newt.com \
    --to=wohler@newt.com \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-pretest-bug@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).