all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Xue Fuqiao <xfq.free@gmail.com>
To: "Aurélien Aptel" <aurelien.aptel@gmail.com>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
	Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: Can't build trunk -- subr.el: Symbol's function definition is void: called-interactively-p
Date: Thu, 31 Jan 2013 23:05:25 +0800	[thread overview]
Message-ID: <20130131230525.9f01b2cb69879aa0edc7ff03@gmail.com> (raw)
In-Reply-To: <CA+5B0FOYsZPPCjQtxA5DA3-35YbV2kKv19ERnSDCvL3Qa530UA@mail.gmail.com>

On Thu, 31 Jan 2013 13:26:26 +0100
Aurélien Aptel <aurelien.aptel@gmail.com> wrote:

> On Thu, Jan 31, 2013 at 12:30 PM, Andreas Schwab <schwab@linux-m68k.org> wrote:
> > Aurélien Aptel <aurelien.aptel@gmail.com> writes:
> >
> >> Loading emacs-lisp/byte-run (compiled; note, source file is newer)...
> >
> > Try bootstrapping.
> 
> It works when I `make bootstrap`, but why does the simple `make` fail?
> 

In INSTALL.BZR:

Occasionally the file "lisp/loaddefs.el" (and similar automatically
generated files, such as esh-groups.el, and *-loaddefs.el in some
subdirectories of lisp/, e.g. mh-e/ and calendar/) will need to be
updated to reflect new autoloaded functions.  If you see errors (rather
than warnings) about undefined lisp functions during compilation, that
may be the reason.

-- 
Best regards, Xue Fuqiao.
http://www.emacswiki.org/emacs/XueFuqiao



      reply	other threads:[~2013-01-31 15:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-31 11:06 Can't build trunk -- subr.el: Symbol's function definition is void: called-interactively-p Aurélien Aptel
2013-01-31 11:30 ` Andreas Schwab
2013-01-31 12:05   ` Bastien
2013-01-31 12:26   ` Aurélien Aptel
2013-01-31 15:05     ` Xue Fuqiao [this message]

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=20130131230525.9f01b2cb69879aa0edc7ff03@gmail.com \
    --to=xfq.free@gmail.com \
    --cc=aurelien.aptel@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=schwab@linux-m68k.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 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.