From: Paul Eggert <eggert@cs.ucla.edu>
To: "Peter Münster" <pmlists@free.fr>
Cc: 19672@debbugs.gnu.org
Subject: bug#19672: 25.0.50; make bootstrap fails on git HEAD
Date: Sat, 24 Jan 2015 18:45:49 -0800 [thread overview]
Message-ID: <54C458DD.3040308@cs.ucla.edu> (raw)
In-Reply-To: <874mrgpbcc.fsf@roche-blanche.net>
Thanks for reporting that. I see the same failure as you on my platform (Fedora
21 x86-64), but I get another failure earlier, as follows:
ELC gnus/nnregistry.elc
Warning: Using brain-dead macro `mm-with-unibyte-current-buffer'!
utf7.el: `mm-with-unibyte-current-buffer' is an obsolete macro (as of 25.1).
../emacs-lisp/eieio.el: `eieio-object-name-string' is an obsolete generic
function (as of 25.1); use `eieio-named' instead.
../emacs-lisp/eieio-base.el: `eieio-object-name-string' is an obsolete generic
function (as of 25.1); use `eieio-named' instead.
In toplevel form:
gnus/nnregistry.el:34:1:Error: Wrong type argument: listp,
cl-struct-cl--generic-tags
Makefile:287: recipe for target 'gnus/nnregistry.elc' failed
make[2]: *** [gnus/nnregistry.elc] Error 1
make[2]: Leaving directory '/home/eggert/src/gnu/emacs/static-checking/lisp'
A bisect finds that the nnregistry bug was introduced by this recent commit, and
I suspect that this change is causing your problem too:
commit fd62486e819056bc9d0f00c09731a45a7f837997
Author: Stefan Monnier <monnier@iro.umontreal.ca>
Date: Fri Jan 23 16:50:56 2015 -0500
* lisp/emacs-lisp/cl-generic.el (cl-no-primary-method): New fun and error.
(cl--generic-build-combined-method): Use it.
I'll CC: this email to Stefan to give him a heads-up.
next prev parent reply other threads:[~2015-01-25 2:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-24 13:17 bug#19672: 25.0.50; make bootstrap fails on git HEAD Peter Münster
2015-01-25 2:45 ` Paul Eggert [this message]
2015-01-25 16:10 ` Stefan Monnier
2015-01-25 16:39 ` Paul Eggert
2015-01-26 8:00 ` Tassilo Horn
2015-01-25 17:44 ` bug#19672: 19672@debbugs.gnu.org Stefan Husmann
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=54C458DD.3040308@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=19672@debbugs.gnu.org \
--cc=pmlists@free.fr \
/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).