unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Berman <stephen.berman@gmx.net>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Symbol's function definition is void: bovine-batch-make-parser
Date: Sat, 30 Nov 2013 19:56:39 +0100	[thread overview]
Message-ID: <8738mdsopk.fsf@rosalinde.fritz.box> (raw)
In-Reply-To: <2kiov9bu8h.fsf@fencepost.gnu.org> (Glenn Morris's message of "Sat, 30 Nov 2013 13:49:18 -0500")

On Sat, 30 Nov 2013 13:49:18 -0500 Glenn Morris <rgm@gnu.org> wrote:

> Stephen Berman wrote:
>
>> Source file
>> /data/steve/bzr/emacs/quickfixes/lisp/cedet/semantic/bovine/grammar.el'
>> newer than byte-compiled file
>> Source file
>> /data/steve/bzr/emacs/quickfixes/lisp/cedet/semantic/grammar.el' newer than
>> byte-compiled file
>> Symbol's function definition is void: bovine-batch-make-parser
> [...]
>> This is with 'make -k; make'.  I haven't tried bootstrapping yet
>
> For future reference, you can check
>
> http://hydra.nixos.org/jobset/gnu/emacs-trunk
>
> rather than asking here. If the relevant bzr revision has any green
> lights at all, then you know a bootstrap works.

Thanks for the tip.

> Otherwise if CPU time is worth more than your personal time to you,
> you should start by looking at the "Source file newer" messages around
> the failure, and try removing the associated .elc files.

I did try that and it didn't work (maybe it would have if I'd deleted
all *.elc file under lisp/semantic and not just in the subdirectory
where the error was signalled, but I decided to go ahead and bootstrap
instead -- had something away from Emacs to do anyway ;-).

Steve Berman



  reply	other threads:[~2013-11-30 18:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-30 16:48 Symbol's function definition is void: bovine-batch-make-parser Stephen Berman
2013-11-30 17:52 ` Stephen Berman
2013-11-30 18:49 ` Glenn Morris
2013-11-30 18:56   ` Stephen Berman [this message]
2013-11-30 20:16     ` Stefan Monnier

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=8738mdsopk.fsf@rosalinde.fritz.box \
    --to=stephen.berman@gmx.net \
    --cc=emacs-devel@gnu.org \
    --cc=rgm@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).