From: Eli Zaretskii <eliz@gnu.org>
To: Corwin Brust <corwin@bru.st>
Cc: aqua0210@foxmail.com, 64167@debbugs.gnu.org
Subject: bug#64167: 29.0.92; Ahead-of-time native compilation failed Emacs 29.0.92
Date: Mon, 19 Jun 2023 20:28:22 +0300 [thread overview]
Message-ID: <83pm5r745l.fsf@gnu.org> (raw)
In-Reply-To: <CAJf-WoQgtszip0DR5A-4dBae3eOVzvRiTefPZzJsDtQebNV2dQ@mail.gmail.com> (message from Corwin Brust on Mon, 19 Jun 2023 09:33:03 -0500)
> Cc: 64167@debbugs.gnu.org
> From: Corwin Brust <corwin@bru.st>
> Date: Mon, 19 Jun 2023 09:33:03 -0500
>
> On Mon, Jun 19, 2023 at 8:24 AM Eason Huang <aqua0210@foxmail.com> wrote:
> >
> > I try to build Emacs 29.0.92 on Windows 11, the `aot` option have no
> > affect. After I start Emacs, still need to compile the built-in
> > packages, such org,cc-mode and so on.
>
> I can reproduce this. Additionally, expressly passing
> --WITH_FULL_AOT=1 to make also has no effect.
>
> Both appear to work fine for non-release builds (i.e., "snapshot"
> builds made in-tree, vs building from a release tarball as we are
> doing in this case).
The difference is that in the release tarball you have all the *.elc
files up-to-date, so the native-compilation rule doesn't kick in.
Remove all the *.elc file, and I'm guessing that the aot build will
work.
I will need to think how to fix this for a release tarball build.
next prev parent reply other threads:[~2023-06-19 17:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 13:24 bug#64167: 29.0.92; Ahead-of-time native compilation failed Emacs 29.0.92 Eason Huang
2023-06-19 14:33 ` Corwin Brust
2023-06-19 17:28 ` Eli Zaretskii [this message]
2023-06-21 6:05 ` Eason Huang
2023-06-21 11:06 ` Eli Zaretskii
2023-06-21 13:06 ` Corwin Brust
2023-06-21 13:11 ` Eason Huang
2023-06-22 11:48 ` Eli Zaretskii
2023-07-01 8:24 ` 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=83pm5r745l.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=64167@debbugs.gnu.org \
--cc=aqua0210@foxmail.com \
--cc=corwin@bru.st \
/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).