From: Eli Zaretskii <eliz@gnu.org>
To: Andy Moreton <andrewjmoreton@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Bootstrap failure on master with native compilation for Windows
Date: Sat, 26 Oct 2024 22:17:08 +0300 [thread overview]
Message-ID: <86cyjmbrnv.fsf@gnu.org> (raw)
In-Reply-To: <8634kiit9e.fsf@gmail.com> (message from Andy Moreton on Sat, 26 Oct 2024 20:00:45 +0100)
> From: Andy Moreton <andrewjmoreton@gmail.com>
> Date: Sat, 26 Oct 2024 20:00:45 +0100
>
> Hi,
>
> Building from latest master branch on Windows using the mingw64
> toolchain works if native compilation is disabled.
>
> With native compilation enabled, there is an error in a bootstrap build
> from a clean tree when dumping:
>
> GEN autoloads
>
> C:/emacs/git/emacs/master/src/lread.c:5485: Emacs fatal error: assertion failed: NILP (Vcomp_abi_hash)
>
> Backtrace:
> 0000000400281213
> 000000040010ab11
> 000000040018477c
> 00000004001fda5d
> 00000004002b112b
> 00000004002af8e1
> 0000000400308e86
> 00000004000012e1
> 00000004000013ee
> 000000067261736c
> 000000067441cc89
> make[2]: *** [Makefile:203: autoloads] Error 3
> make[2]: Leaving directory '/c/emacs/git/emacs/master/build/mingw64-x86_64-O2-native/lisp'
>
>
> Running a git bisect points to commit edf37e811caf ("Implement drawing
> text with DirectWrite on MS-Windows.").
>
> Possibly something to do with defsubr calls in syms_of_w32dwrite, and the
> latter being called in the wrong initialisation order ?
Does it help to move the following part out of syms_of_w32dwrite to
the top level of that file?
DEFVAR_BOOL ("w32-inhibit-dwrite", w32_inhibit_dwrite,
doc: /* If t, don't use DirectWrite. */);
next prev parent reply other threads:[~2024-10-26 19:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-26 19:00 Bootstrap failure on master with native compilation for Windows Andy Moreton
2024-10-26 19:17 ` Eli Zaretskii [this message]
2024-10-26 19:20 ` Eli Zaretskii
2024-10-26 19:41 ` Eli Zaretskii
2024-10-27 0:30 ` Andy Moreton
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=86cyjmbrnv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andrewjmoreton@gmail.com \
--cc=emacs-devel@gnu.org \
/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).