From: Eli Zaretskii <eliz@gnu.org>
To: Andrea Corallo <akrl@sdf.org>, Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 47161@debbugs.gnu.org
Subject: bug#47161: 28.0.50; [feature/native-comp] Failure to native-compile bytecomp.el etc.
Date: Tue, 16 Mar 2021 20:29:20 +0200 [thread overview]
Message-ID: <83eegfdkan.fsf@gnu.org> (raw)
In-Reply-To: <xjf7dm7xe52.fsf@sdf.org> (message from Andrea Corallo on Tue, 16 Mar 2021 16:22:01 +0000)
> From: Andrea Corallo <akrl@sdf.org>
> Cc: 47161@debbugs.gnu.org
> Date: Tue, 16 Mar 2021 16:22:01 +0000
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > What I did was modified byte-opt.el, saved, and said "make".
>
> I can reproduce it.
Good news, thanks.
> >> Also, shouldn't byte-opt.el be native compiled as it's in COMPILE_FIRST?
> >
> > That bothers me as well. It happens from time to time: for example,
> > I've just updated from Git, which brought modified bytecomp.el and
> > comp.el, both in COMPILE_FIRST. And yet this is what I see when I say
> > "make":
> >
> > make -C lisp all
> > make[1]: Entering directory `/d/gnu/git/emacs/native-comp/lisp'
> > make -C ../leim all EMACS="../src/emacs.exe"
> > make -C ../admin/grammars all EMACS="../../src/emacs.exe"
> > make[2]: Entering directory `/d/gnu/git/emacs/native-comp/admin/grammars'
> > make[2]: Nothing to be done for `all'.
> > make[2]: Leaving directory `/d/gnu/git/emacs/native-comp/admin/grammars'
> > make[2]: Entering directory `/d/gnu/git/emacs/native-comp/leim'
> > make[2]: Nothing to be done for `all'.
> > make[2]: Leaving directory `/d/gnu/git/emacs/native-comp/leim'
> > make[2]: Entering directory `/d/gnu/git/emacs/native-comp/lisp'
> > ELC emacs-lisp/bytecomp.elc
> > make[2]: Leaving directory `/d/gnu/git/emacs/native-comp/lisp'
> > make[2]: Entering directory `/d/gnu/git/emacs/native-comp/lisp'
> > ELC emacs-lisp/comp.elc
> > make[2]: Leaving directory `/d/gnu/git/emacs/native-comp/lisp'
> > make[2]: Entering directory `/d/gnu/git/emacs/native-comp/lisp'
> > make[2]: Nothing to be done for `compile-targets'.
> > make[2]: Leaving directory `/d/gnu/git/emacs/native-comp/lisp'
> >
> > Why not "ELC+ELN"?
>
> AFAICS using "make V=1" we fail only to add the correct "ELC+ELN" in
> place of "ELC" but we invoke the right command, will try to have a look.
Thanks.
> Regarding the macro expansion issue I tried to have a quick look but I'm
> not very much into cl-generic.el and couldn't spot any obvious (for me)
> issue so far.
Perhaps Stefan could help us out here.
next prev parent reply other threads:[~2021-03-16 18:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 15:27 bug#47161: 28.0.50; [feature/native-comp] Failure to native-compile bytecomp.el etc Eli Zaretskii
2021-03-15 15:48 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-15 17:26 ` Eli Zaretskii
2021-03-15 20:05 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-16 12:50 ` Eli Zaretskii
2021-03-16 16:22 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-16 18:29 ` Eli Zaretskii [this message]
2021-03-17 1:27 ` Stefan Monnier
2021-03-19 15:28 ` Eli Zaretskii
2021-03-19 15:58 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-04-10 16:44 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-24 13:18 ` Lars Ingebrigtsen
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=83eegfdkan.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=47161@debbugs.gnu.org \
--cc=akrl@sdf.org \
--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).