From: Angelo Graziosi <angelo.g0@libero.it>
To: include_yy@qq.com
Cc: 72335@debbugs.gnu.org
Subject: bug#72335: An attempt to fix UCRT64 build failure
Date: Sat, 3 Aug 2024 17:39:10 +0200 [thread overview]
Message-ID: <eb782544-ba02-4610-a029-4374fa24d193@libero.it> (raw)
In-Reply-To: <tencent_3792C71A2B55CAA768DBCEBC4E2DEF337008@qq.com>
> MSYS2 do provides a patch[2] that do something about function
> `close_output_streams' in src/sysdep.c. By applying it, I can get these results:
>
> ***
> *** "make all" succeeded, but Emacs is not functional.
> ***
This happens if you apply only one patch.
You have to apply _both_ patches (don't ask WHY!):
https://github.com/msys2/MINGW-packages/blob/master/mingw-w64-emacs/001-ucrt.patch
https://github.com/msys2/MINGW-packages/blob/master/mingw-w64-emacs/002-clang-fixes.patch
I do monthly UCRT64 builds of Emacs master on Win10 (*true* machine, not
Wine nor VBox). I did the last build with yesterday master and had only
two warnings for ORG/TEXI files
org.texi:16157: warning: @anchor should not appear on @item line
org.texi:16170: warning: @anchor should not appear on @item line
Maybe MSYS2 people which created those patches can clarify...
Ciao,
Angelo.
next prev parent reply other threads:[~2024-08-03 15:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-28 13:55 bug#72335: An attempt to fix UCRT64 build failure YI Yue via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-28 14:22 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-28 14:49 ` bug#72335: ��� " o0o0o���� via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-28 14:29 ` Eli Zaretskii
2024-07-28 14:47 ` bug#72335: ��� " o0o0o���� via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-03 15:39 ` Angelo Graziosi [this message]
2024-08-11 16:50 ` Yi Yue via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-11 18:35 ` Angelo Graziosi
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=eb782544-ba02-4610-a029-4374fa24d193@libero.it \
--to=angelo.g0@libero.it \
--cc=72335@debbugs.gnu.org \
--cc=include_yy@qq.com \
/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.