unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 12548@debbugs.gnu.org
Subject: bug#12548: 24.2.50; Eager macro-expansion skipped due to cycle
Date: Mon, 01 Oct 2012 11:13:04 -0400	[thread overview]
Message-ID: <jwvlifq5j2e.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83391ycq0c.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 01 Oct 2012 14:53:39 +0200")

> Since about 2 weeks ago, I see these warning messages while
> bootstrapping on MS-Windows, when Lisp files are being byte-compiled.

Hmm.. you should have seen them since when I introduced the
eager-macroexpansion, which is a bit more than 2 weeks.

>   Warning: Eager macro-expansion skipped due to cycle:
>     Γאª => (load "erc-backend.el") => (macroexpand-all (defun erc-server-connect Γאª)) => (macroexpand (erc-log Γאª)) => (load "erc.el") => (load "erc-backend.el")

[ Not sure what this Γאª is about, but I'll assume it's some incorrect
  encoding of … ]

> AFAICS, all of these messages are related either to loading tramp.el
> or erc-backend.el.  But I may have missed others, not sure.

Yes, IIRC there are two such problematic cycles, one with Tramp and
another with ERC (there were a couple more, but I fixed them).
I'm not completely sure how best to fix them, so I preferred to leave
them in and wait for the ERC and Tramp maintainers to fix them later.
They're harmless in the sense that the resulting .elc files should be
correct (and probably even identical).

I think the warning prints a clear and concise description of the cycle,
so it should not be too hard for the maintainers of those packages to
understand the problem and decide how best to fix it.

> and its subroutines.  I never saw anything similar in "regular" byte
> compilation after updating from the master repository, FWIW.

A bootstrap under GNU/Linux shows those same warnings.


        Stefan





  reply	other threads:[~2012-10-01 15:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-01 12:53 bug#12548: 24.2.50; Eager macro-expansion skipped due to cycle Eli Zaretskii
2012-10-01 15:13 ` Stefan Monnier [this message]
2012-10-01 15:30   ` Eli Zaretskii
2012-10-01 15:31   ` Drew Adams
2012-10-01 16:42     ` Stefan Monnier
2012-10-01 17:00       ` Drew Adams
2012-10-02  6:47 ` Glenn Morris
2012-10-02 16:45   ` Eli Zaretskii
2012-10-02 16:53     ` Glenn Morris
2012-10-02 18:07       ` Glenn Morris
2012-10-03  1:41         ` Stefan Monnier
2012-10-03  7:06           ` Glenn Morris
2012-10-03 13:04             ` Stefan Monnier
2012-10-03 16:19               ` Glenn Morris
2012-10-03 17:46                 ` Stefan Monnier
2012-10-04  1:39                   ` Michael Olson
2012-10-05 20:21                     ` Glenn Morris
2012-10-05 22:24                       ` Michael Olson
2012-10-03  1:42     ` 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=jwvlifq5j2e.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=12548@debbugs.gnu.org \
    --cc=eliz@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).