From: Eli Zaretskii <eliz@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: 70357@debbugs.gnu.org, monnier@iro.umontreal.ca
Subject: bug#70357: 30.0.50; loadup.el, load nadvice before seq
Date: Sat, 13 Apr 2024 12:29:11 +0300 [thread overview]
Message-ID: <86ttk5pq54.fsf@gnu.org> (raw)
In-Reply-To: <m2bk6dyan5.fsf@Pro.fritz.box> (message from Gerd Möllmann on Sat, 13 Apr 2024 09:39:10 +0200)
> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Cc: monnier@iro.umontreal.ca, 70357@debbugs.gnu.org
> Date: Sat, 13 Apr 2024 09:39:10 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> If seq.el, the source file, is loaded from loadup, these functions are
> >> not yet compiled. If seq.elc is loaded, the functions are apparently
> >> already compiled, and a warning is emitted.
> >
> > How to create this situation?
>
> I get that regularly when I make changes in some .c file, build in src,
> which builds a new temacs, and so on, and all while seq.elc exists.
Strange. I just tried to reproduce this, but couldn't. I did
"touch src/data.c", then "make", and I see no problem. Moreover,
loadup says
Loading emacs-lisp/seq...
both when it dumps bootstrap-emacs and when it dumps emacs, and that
means it loads seq.elc, not seq.el.
So there's something else here we are missing, I suppose.
next prev parent reply other threads:[~2024-04-13 9:29 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 [this message]
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
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
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=86ttk5pq54.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=70357@debbugs.gnu.org \
--cc=gerd.moellmann@gmail.com \
--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 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).