From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: luangruo@yahoo.com, gregory@heytings.org, larsi@gnus.org,
monnier@iro.umontreal.ca, stefan@marxist.se, emacs-devel@gnu.org
Subject: Re: A more radical cleanup for make bootstrap?
Date: Tue, 20 Sep 2022 18:55:44 +0300 [thread overview]
Message-ID: <838rmevy4f.fsf@gnu.org> (raw)
In-Reply-To: <87czbqdpbb.fsf@gmail.com> (message from Robert Pluim on Tue, 20 Sep 2022 17:43:20 +0200)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: Po Lu <luangruo@yahoo.com>, gregory@heytings.org, larsi@gnus.org,
> monnier@iro.umontreal.ca, stefan@marxist.se, emacs-devel@gnu.org
> Date: Tue, 20 Sep 2022 17:43:20 +0200
>
> >>>>> On Tue, 20 Sep 2022 15:05:50 +0300, Eli Zaretskii <eliz@gnu.org> said:
>
>
> Eli> I usually have no problems identifying the offending *.elc files. And
> Eli> if that fails (which it does very rarely), then this never fails:
>
> Eli> $ find ./lisp -name "*.elc" -delete
> Eli> $ make
>
> I just did that because of a compile failure in ./lisp, it failed
> again in ./lisp (but differently)
When that happens, delete temacs and bootstrap-emacs as well.
next prev parent reply other threads:[~2022-09-20 15:55 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 19:46 A more radical cleanup for make bootstrap? Gregory Heytings
2022-09-19 19:48 ` Lars Ingebrigtsen
2022-09-19 20:26 ` Alan Mackenzie
2022-09-19 20:29 ` Lars Ingebrigtsen
2022-09-19 20:49 ` Alan Mackenzie
2022-09-19 20:51 ` Lars Ingebrigtsen
2022-09-19 21:01 ` Alan Mackenzie
2022-09-20 2:35 ` Eli Zaretskii
2022-09-20 2:42 ` Po Lu
2022-09-20 11:01 ` Eli Zaretskii
2022-09-20 10:01 ` Alan Mackenzie
2022-09-19 21:45 ` Gregory Heytings
2022-09-20 6:38 ` Alfred M. Szmidt
2022-09-20 8:22 ` Gregory Heytings
2022-09-19 20:53 ` Stefan Monnier
2022-09-20 2:29 ` Eli Zaretskii
2022-09-20 7:58 ` Gregory Heytings
2022-09-20 8:20 ` Po Lu
2022-09-20 8:25 ` Gregory Heytings
2022-09-20 8:46 ` Po Lu
2022-09-20 9:01 ` Gregory Heytings
2022-09-20 11:22 ` Eli Zaretskii
2022-09-20 11:55 ` Po Lu
2022-09-20 12:05 ` Eli Zaretskii
2022-09-20 12:51 ` Po Lu
2022-09-20 12:55 ` Eli Zaretskii
2022-09-20 13:08 ` Lars Ingebrigtsen
2022-09-20 13:27 ` Po Lu
2022-09-20 13:31 ` Lars Ingebrigtsen
2022-09-20 14:00 ` Eli Zaretskii
2022-09-20 15:54 ` Eli Zaretskii
2022-09-20 16:46 ` Michael Albinus
2022-09-21 2:16 ` Po Lu
2022-09-20 15:43 ` Robert Pluim
2022-09-20 15:55 ` Eli Zaretskii [this message]
2022-09-20 16:14 ` Michael Welsh Duggan
2022-09-20 16:21 ` Eli Zaretskii
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=838rmevy4f.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=gregory@heytings.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
--cc=monnier@iro.umontreal.ca \
--cc=rpluim@gmail.com \
--cc=stefan@marxist.se \
/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).