From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 70357@debbugs.gnu.org, eliz@gnu.org, monnier@iro.umontreal.ca
Subject: bug#70357: 30.0.50; loadup.el, load nadvice before seq
Date: Sun, 14 Apr 2024 08:26:04 +0200 [thread overview]
Message-ID: <m25xwkxxxf.fsf@Pro.fritz.box> (raw)
In-Reply-To: <87zftw7k23.fsf@web.de> (Michael Heerdegen's message of "Sun, 14 Apr 2024 04:30:12 +0200")
Michael Heerdegen <michael_heerdegen@web.de> writes:
> Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of
> text editors" <bug-gnu-emacs@gnu.org> writes:
>
>> I did not look in enough detail to see the specific problem. E.g. I
>> don't know what is the actual warning that we're trying to emit.
>
> It says
>
> byte-compile-report-error((void-function advice--cd*r))
Right, that's where I got the idea from that loading nadvice first might
help.
>
> This should be the occurrence in `byte-compile--function-signature', no?
> And nadvice.el maybe not loaded?
>
> AFAIU this could be the cause of the circle and its recursion.
What Stefan said about the different behaviour when some files are
compiled and others are not, is, I guess, what I see here. Sometimes
things work, sometimes they don't. Eli's attempt to reproduce the
problem also shows that, I think. Hence my thought if it wouldn't be an
idea to ignore .elcs when dumping bootstrap-emacs.pdmp. It doesn't help
with circular dependencies, but at least it is easier to reproduce when
it happens.
next prev parent reply other threads:[~2024-04-14 6:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 18:19 bug#70357: 30.0.50; loadup.el, load nadvice before seq Gerd Möllmann
2024-04-12 19:03 ` Eli Zaretskii
2024-04-12 20:43 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-13 4:01 ` Gerd Möllmann
2024-04-13 5:22 ` Gerd Möllmann
2024-04-13 6:19 ` Eli Zaretskii
2024-04-13 7:07 ` Gerd Möllmann
2024-04-13 7:31 ` Eli Zaretskii
2024-04-13 7:39 ` Gerd Möllmann
2024-04-13 9:29 ` Eli Zaretskii
2024-04-13 12:44 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-14 2:30 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-14 6:26 ` Gerd Möllmann [this message]
2024-04-14 7:30 ` Eli Zaretskii
2024-04-14 12:48 ` Gerd Möllmann
2024-04-14 14:14 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-15 3:11 ` Gerd Möllmann
2024-04-15 6:16 ` Gerd Möllmann
2024-04-15 7:01 ` Gerd Möllmann
2024-04-15 7:55 ` Gerd Möllmann
2024-04-15 8:01 ` Gerd Möllmann
2024-04-15 12:11 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-15 12:47 ` Gerd Möllmann
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m25xwkxxxf.fsf@Pro.fritz.box \
--to=gerd.moellmann@gmail.com \
--cc=70357@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=michael_heerdegen@web.de \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.