From: Eli Zaretskii <eliz@gnu.org>
To: Pip Cet <pipcet@gmail.com>
Cc: mwd@md5i.com, 46502@debbugs.gnu.org, akrl@sdf.org
Subject: bug#46502: 28.0.50; [feature/native-comp] (d3a399dd) native-comp bootstrap failure
Date: Sat, 20 Feb 2021 10:56:13 +0200 [thread overview]
Message-ID: <83a6rz15jm.fsf@gnu.org> (raw)
In-Reply-To: <CAOqdjBdBk7+OiQCJkvczHeizAp99G7o-VxhQCe7hfig09jtLiA@mail.gmail.com> (message from Pip Cet on Sat, 20 Feb 2021 04:35:39 +0000)
> From: Pip Cet <pipcet@gmail.com>
> Date: Sat, 20 Feb 2021 04:35:39 +0000
> Cc: akrl@sdf.org, mwd@md5i.com, 46502@debbugs.gnu.org
>
> Okay. Here's what I'm seeing (master branch, interrupted after
> macroexp.elc is compiled).
It's hard to see the differences, since your MUA seemed to have folded
long lines. Can you send the diffs as an attachment?
And when exactly did you interrupt the second run? The first things
that get compiled are these:
COMPILE_FIRST = \
$(lisp)/emacs-lisp/macroexp.elc \
$(lisp)/emacs-lisp/cconv.elc \
$(lisp)/emacs-lisp/byte-opt.elc \
$(lisp)/emacs-lisp/bytecomp.elc \
$(lisp)/emacs-lisp/autoload.elc
Which one of these was being compiled when you pressed Ctrl-C?
> > In general, Make itself will delete any target files it knows about
> > that were not fully built at the time of SIGINT. Maybe we don't tell
> > Make enough about the files native-comp produces?
>
> So we should delete the early-compilation .elcs if we end up deleting
> bootstrap-emacs.pdmp, too?
No, I don't think so. (What is the relation between
bootstrap-emacs.pdmp and the produced *.elc files?) If the
compilation of these *.elc files has finished, I see no reason to
delete them, because they should be correct and usable.
next prev parent reply other threads:[~2021-02-20 8:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-14 5:05 bug#46502: 28.0.50; [feature/native-comp] (d3a399dd) native-comp bootstrap failure Michael Welsh Duggan
2021-02-18 9:47 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-18 10:14 ` Pip Cet
2021-02-18 10:29 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-18 14:34 ` Eli Zaretskii
2021-02-19 13:31 ` Pip Cet
2021-02-19 13:48 ` Eli Zaretskii
2021-02-19 14:26 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-02-20 4:35 ` Pip Cet
2021-02-20 8:56 ` Eli Zaretskii [this message]
2021-02-20 9:15 ` Pip Cet
2021-02-20 11:21 ` Eli Zaretskii
2021-02-20 11:48 ` Eli Zaretskii
2021-02-20 12:03 ` Pip Cet
2021-02-20 12:42 ` Eli Zaretskii
2021-02-20 17:00 ` Pip Cet
2021-02-20 17:18 ` Eli Zaretskii
2021-02-20 15:42 ` Stefan Monnier
2021-02-20 17:02 ` Pip Cet
2021-02-20 17:12 ` Stefan Monnier
[not found] ` <jwvo8etr7hf.fsf-monnier+emacs@gnu.org>
2021-04-05 2:56 ` Michael Welsh Duggan
2021-02-18 14:55 ` Michael Welsh Duggan
2021-02-18 15:12 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=83a6rz15jm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=46502@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=mwd@md5i.com \
--cc=pipcet@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 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).