GNU bug report logs - #12548
24.2.50; Eager macro-expansion skipped due to cycle

Previous Next

Package: emacs;

Reported by: Eli Zaretskii <eliz <at> gnu.org>

Date: Mon, 1 Oct 2012 12:55:02 UTC

Severity: minor

Found in version 24.2.50

Done: Glenn Morris <rgm <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: 12548 <at> debbugs.gnu.org
Subject: bug#12548: 24.2.50; Eager macro-expansion skipped due to cycle
Date: Mon, 01 Oct 2012 17:30:57 +0200
> From: Stefan Monnier <monnier <at> iro.umontreal.ca>
> Cc: 12548 <at> debbugs.gnu.org
> Date: Mon, 01 Oct 2012 11:13:04 -0400
> 
> > 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.

What can I say? I don't bootstrap too often ;-)

> >   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 … ]

Most probably.  The Windows console is notorious for screwing up
non-ASCII characters, since the encoding used by GUI applications and
by console programs is different.

> > 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.

Thanks for the info.





This bug report was last modified 12 years and 200 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.