From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: ofv@wanadoo.es, 53377@debbugs.gnu.org
Subject: bug#53377: 28.0.91: Build fails on MSYS2/MinGW-w64 with Clang
Date: Thu, 20 Jan 2022 09:40:04 +0200 [thread overview]
Message-ID: <83o846rh2j.fsf@gnu.org> (raw)
In-Reply-To: <87lezb2opb.fsf@yahoo.com> (bug-gnu-emacs@gnu.org)
> Resent-From: Po Lu <luangruo@yahoo.com>
> Original-Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
> Resent-CC: bug-gnu-emacs@gnu.org
> Resent-Sender: help-debbugs@gnu.org
> Cc: 53377@debbugs.gnu.org
> Date: Thu, 20 Jan 2022 09:14:24 +0800
> From: Po Lu via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> Óscar Fuentes <ofv@wanadoo.es> writes:
>
> > Building under the Clang environment (which uses clang instead of gcc)
> > fails with
>
> Do we really want to support building Emacs with Clang on MS-Windows?
It depends on what would such support require. Judging by what I see
in the original report, we are very far from understanding that, so I
would withhold my judgment until I see what changes to the existing
code are needed to support that configuration. I have no real
knowledge of how Clang supports native MS-Windows; I don't even know
what they use for the runtime library. So I cannot envision up front
what kind of changes will be needed to produce a successful native
MS-Windows build of Emacs using Clang.
next prev parent reply other threads:[~2022-01-20 7:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 23:41 bug#53377: 28.0.91: Build fails on MSYS2/MinGW-w64 with Clang Óscar Fuentes
2022-01-20 1:14 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-20 3:32 ` Óscar Fuentes
2022-01-20 3:41 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-20 3:59 ` Óscar Fuentes
2022-01-20 4:52 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-20 7:54 ` Eli Zaretskii
2022-01-20 7:40 ` Eli Zaretskii [this message]
2022-01-21 4:14 ` Richard Stallman
2022-01-20 7:33 ` 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=83o846rh2j.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=53377@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=ofv@wanadoo.es \
/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.