unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Tassilo Horn <tsdh@gnu.org>
To: Stefan Husmann <stefan-husmann@t-online.de>
Cc: 20125@debbugs.gnu.org
Subject: bug#20125: 25.0.50; Build error related to "cl-every"
Date: Tue, 17 Mar 2015 16:31:18 +0100	[thread overview]
Message-ID: <87r3snbpyx.fsf@gnu.org> (raw)
In-Reply-To: <87bnjrn4nq.fsf@t-online.de> (Stefan Husmann's message of "Tue, 17 Mar 2015 14:18:33 +0100")

[-- Attachment #1: Type: text/plain, Size: 2019 bytes --]

Stefan Husmann <stefan-husmann@t-online.de> writes:

> I write this using an emacs from xwidgets-mvp-branch, but the bug happens
> when trying to build from master. 
>
> Message:
> Loading /home/haawda/paketierung/maintained_by_me/emacs-lucid-git/src/emacs-lucid-git/lisp/emacs-lisp/timer.el (source)...
> Eager macro-expansion failure: (void-function cl-every)
> Eager macro-expansion failure: (void-function cl-every)
> Symbol's function definition is void: cl-every
> Makefile:830: recipe for target 'bootstrap-emacs' failed
> make[2]: *** [bootstrap-emacs] Error 255
> make[2]: Leaving directory '/home/haawda/paketierung/maintained_by_me/emacs-lucid-git/src/emacs-lucid-git/src'
> Makefile:398: recipe for target 'src' failed
> make[1]: *** [src] Error 2
> make[1]: Leaving directory '/home/haawda/paketierung/maintained_by_me/emacs-lucid-git/src/emacs-lucid-git'
> Makefile:1086: recipe for target 'bootstrap' failed
> make: *** [bootstrap] Error 2
> ==> ERROR: A failure occurred in build().

I have that, too.  Bisecting results in this commit made by Stefan (in Cc).

--8<---------------cut here---------------start------------->8---
801eda8a2a00b3f28a69ffe51b05a649fffc5c58 is the first bad commit
commit 801eda8a2a00b3f28a69ffe51b05a649fffc5c58
Author: Stefan Monnier <monnier@iro.umontreal.ca>
Date:   Mon Mar 16 16:11:38 2015 -0400

    * lisp/emacs-lisp/cl-macs.el (cl--transform-lambda): Optimize &aux.
    
    Rework to avoid cl--do-arglist in more cases; add comments to explain what's
    going on.
    (cl--do-&aux): New function extracted from cl--do-arglist.
    (cl--do-arglist): Use it.
    * lisp/emacs-lisp/cl-generic.el: Add Version: header, for ELPA purposes.

:040000 040000 f73912afa1b052c7d6957b819d7e5ee803f8855b 5bcfa670c6f4a4b0a52ccafaa9f01df4264e9657 M	lisp
:040000 040000 0355fb5b6c0ed6f83276f03b0f2e6dd808420f24 53cd3b8db8869877edd27e110d4127b69ef52372 M	test
--8<---------------cut here---------------end--------------->8---

Bye,
Tassilo

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 212 bytes --]

  reply	other threads:[~2015-03-17 15:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-17 13:18 bug#20125: 25.0.50; Build error related to "cl-every" Stefan Husmann
2015-03-17 15:31 ` Tassilo Horn [this message]
2015-03-17 18:31 ` 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=87r3snbpyx.fsf@gnu.org \
    --to=tsdh@gnu.org \
    --cc=20125@debbugs.gnu.org \
    --cc=stefan-husmann@t-online.de \
    /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).