From: Eli Zaretskii <eliz@gnu.org>
To: aqua0210@foxmail.com, corwin@bru.st
Cc: 64167-done@debbugs.gnu.org
Subject: bug#64167: 29.0.92; Ahead-of-time native compilation failed Emacs 29.0.92
Date: Sat, 01 Jul 2023 11:24:04 +0300 [thread overview]
Message-ID: <83sfa8qbtn.fsf@gnu.org> (raw)
In-Reply-To: <83v8ff3eg0.fsf@gnu.org> (message from Eli Zaretskii on Thu, 22 Jun 2023 14:48:47 +0300)
> Cc: corwin@bru.st, 64167@debbugs.gnu.org
> Date: Thu, 22 Jun 2023 14:48:47 +0300
> From: Eli Zaretskii <eliz@gnu.org>
>
> > From: Eason Huang <aqua0210@foxmail.com>
> > Cc: Corwin Brust <corwin@bru.st>, 64167@debbugs.gnu.org
> > Date: Wed, 21 Jun 2023 14:05:13 +0800
> >
> > Eli Zaretskii <eliz@gnu.org> writes:
> >
> > > 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.
> > Yes, you are right. I tried to download source code from
> > https://git.savannah.gnu.org/cgit/emacs.git/snapshot/emacs-2bad5829ff76538774676f7274f40ce7baf04c73.tar.gz
> >
> > And it can be build --with-native-compilation=aot
>
> OK, I think I fixed this now on the emacs-29 branch. I tested the fix
> with several configurations, but not all of them. In particular, I
> didn't test out-of-tree builds, so if someone could test that, I'd
> appreciate.
No further comments, so I presume the bug was indeed fixed, and I'm
closing it. Feel free to reopen if something still doesn't work.
prev parent reply other threads:[~2023-07-01 8:24 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
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 [this message]
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=83sfa8qbtn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=64167-done@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).