From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: clang fails to compile emacs in Microsoft Windows
Date: Sat, 13 May 2023 15:46:24 +0300 [thread overview]
Message-ID: <83v8gw9z6n.fsf@gnu.org> (raw)
In-Reply-To: <87bkiobe2z.fsf@telefonica.net> (message from Óscar Fuentes on Sat, 13 May 2023 14:39:16 +0200)
> From: Óscar Fuentes <ofv@wanadoo.es>
> Date: Sat, 13 May 2023 14:39:16 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> > If the MSYS2 project wants to maintain Clang patches, that's fine with
> >> > me. But then these issues are best posted to the MSYS2 forum, not
> >> > here.
> >>
> >> Why? Here is the people that hack and build Emacs on a regular basis,
> >> right?
> >>
> >> Please note that the problem on the OP is not related to the patches.
> >
> > It is related to a configuration that isn't officially supported.
>
> Last time I looked the configure script had references to ancient
> propietary compilers and systems that are not in use for decades.
Which ones?
> But adding a trivial fix for a Free toolset on a Free software
> distribution for the most widely used OS that *also improves support
> for gcc by eliminating a warning* is not acceptable.
You have completely misunderstood and misinterpreted what I wrote.
prev parent reply other threads:[~2023-05-13 12:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 14:11 clang fails to compile emacs in Microsoft Windows Biswapriyo Nath
2023-05-12 15:06 ` Eli Zaretskii
2023-05-12 15:47 ` Óscar Fuentes
2023-05-12 15:59 ` Biswapriyo Nath
2023-05-12 16:03 ` Biswapriyo Nath
2023-05-12 16:13 ` Eli Zaretskii
2023-05-12 16:10 ` Eli Zaretskii
2023-05-12 20:07 ` Óscar Fuentes
2023-05-12 20:10 ` Biswapriyo Nath
2023-05-13 6:00 ` Eli Zaretskii
2023-05-13 7:21 ` Biswapriyo Nath
2023-05-13 5:53 ` Eli Zaretskii
2023-05-13 12:39 ` Óscar Fuentes
2023-05-13 12:46 ` 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=83v8gw9z6n.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).