From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 58224@debbugs.gnu.org
Subject: bug#58224: 29.0.50; "make bootstrap" spuriously warns: "comp.el newer than byte-compiled file"
Date: Sat, 01 Oct 2022 16:29:37 +0200 [thread overview]
Message-ID: <87y1tzehwu.fsf@gnus.org> (raw)
In-Reply-To: <CADwFkmnBWpNPdpcTJWrmcrw5yqUTGur23tqt8XV_ayhXudoS4w@mail.gmail.com> (Stefan Kangas's message of "Sat, 1 Oct 2022 16:15:09 +0200")
Stefan Kangas <stefankangas@gmail.com> writes:
> Every time I "make bootstrap", I get a ton of spurious messages (see
> below). I believe they started showing up with Lars' much appreciated
> work on improving build speeds.
No, I think they were there before that.
> Is there any chance we could do something to silence them? If we
> can't solve it "properly", how about just a hack? For example, could
> we add some variable to suppress these messages at this stage of the
> build process?
Yes, making the warnings go away would be nice.
next prev parent reply other threads:[~2022-10-01 14:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-01 14:15 bug#58224: 29.0.50; "make bootstrap" spuriously warns: "comp.el newer than byte-compiled file" Stefan Kangas
2022-10-01 14:29 ` Lars Ingebrigtsen [this message]
2022-10-01 14:50 ` Eli Zaretskii
2022-10-01 16:10 ` Stefan Kangas
2022-10-01 18:11 ` Alan Mackenzie
2022-10-01 21:15 ` Alan Mackenzie
2022-10-02 5:59 ` Eli Zaretskii
2022-10-02 10:43 ` Alan Mackenzie
2022-10-02 11:04 ` Eli Zaretskii
2022-10-02 11:32 ` Alan Mackenzie
2022-10-02 15:38 ` Alan Mackenzie
2022-10-02 15:54 ` Eli Zaretskii
2022-10-02 16:46 ` Alan Mackenzie
2022-10-02 17:07 ` Eli Zaretskii
2022-10-02 20:37 ` Alan Mackenzie
2022-10-02 21:29 ` Stefan Kangas
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=87y1tzehwu.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=58224@debbugs.gnu.org \
--cc=stefankangas@gmail.com \
/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.