bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#46502: 28.0.50; [feature/native-comp] (d3a399dd) native-comp bootstr


From: Eli Zaretskii
Subject: bug#46502: 28.0.50; [feature/native-comp] (d3a399dd) native-comp bootstrap failure
Date: Sat, 20 Feb 2021 10:56:13 +0200

> 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.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]