From: Eli Zaretskii <eliz@gnu.org>
To: Eason Huang <aqua0210@foxmail.com>
Cc: corwin@bru.st, 64167@debbugs.gnu.org
Subject: bug#64167: 29.0.92; Ahead-of-time native compilation failed Emacs 29.0.92
Date: Wed, 21 Jun 2023 14:06:33 +0300 [thread overview]
Message-ID: <83cz1p5b2e.fsf@gnu.org> (raw)
In-Reply-To: <tencent_2B3677E4285ECE4AF290E43600C03FD66409@qq.com> (message from Eason Huang on Wed, 21 Jun 2023 14:05:13 +0800)
> 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
>
> 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
>
> But it will failed with some errors on Windows 10 and Windows 11:
> ```
> ELC+ELN erc/erc-menu.elc
> ELC+ELN erc/erc-netsplit.elc
> ELC+ELN erc/erc-networks.elc
>
> Backtrace:
> 00007ff6a78ca72e
> 00007ff6a7798b21
> 00007ff6a77b9611
> 00007ff6a792ee8a
> 00007ffa37c47ff0
> 00007ffa38712477
> 00007ffa386c14ec
> ```
And the build without aot succeeds and can successfully natively
compile those same files (erc-networks.el) without problems?
If the build without aot also fails, then this is a separate problem
and should be discussed in a separate bug report. It might be the
same problem reported and discussed in bug#63365 (are you also using
GCC 13.1?).
next prev parent reply other threads:[~2023-06-21 11:06 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83cz1p5b2e.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.