From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?utf-8?Q?=C3=93scar_Fuentes?= Newsgroups: gmane.emacs.devel Subject: Re: MinGW build on master fails with Error 127 Date: Sat, 24 Dec 2022 19:56:51 +0100 Message-ID: <87zgbczl3g.fsf@telefonica.net> References: <83wn6wr5oz.fsf@gnu.org> <0c9519c9-add7-9fb1-ac7f-2f20e1916d65@bluewin.ch> <83tu20r4y7.fsf@gnu.org> <01b7362d-7d60-3054-5590-d4dbbcda76d7@bluewin.ch> <83r0x4r490.fsf@gnu.org> <837cyh71ft.fsf@gnu.org> <832966a5-bd27-76f9-4757-a8c246eca416@bluewin.ch> <835ye06ex7.fsf@gnu.org> <87sfh424ya.fsf@telefonica.net> <83y1qw4x8w.fsf@gnu.org> <87o7rs22yn.fsf@telefonica.net> <83v8m04un9.fsf@gnu.org> <87cz8820hx.fsf@telefonica.net> <83sfh44t2t.fsf@gnu.org> <878riw1y70.fsf@telefonica.net> <83pmc84qs3.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="17392"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Dec 24 19:57:40 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1p99iF-0004Lc-Pn for ged-emacs-devel@m.gmane-mx.org; Sat, 24 Dec 2022 19:57:39 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1p99hd-0001zy-92; Sat, 24 Dec 2022 13:57:01 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1p99hb-0001zh-2M for emacs-devel@gnu.org; Sat, 24 Dec 2022 13:56:59 -0500 Original-Received: from relayout02-redir.e.movistar.es ([86.109.101.202]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1p99hZ-0006xP-4z; Sat, 24 Dec 2022 13:56:58 -0500 Original-Received: from sky (91.red-81-39-16.dynamicip.rima-tde.net [81.39.16.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: 981711563@telefonica.net) by relayout02.e.movistar.es (Postfix) with ESMTPSA id 4NfYF0366RzdZxp; Sat, 24 Dec 2022 19:56:52 +0100 (CET) In-Reply-To: <83pmc84qs3.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 24 Dec 2022 20:09:48 +0200") X-TnetOut-Country: IP: 81.39.16.91 | Country: ES X-TnetOut-Information: AntiSPAM and AntiVIRUS on relayout02 X-TnetOut-MsgID: 4NfYF0366RzdZxp.A4702 X-TnetOut-SpamCheck: no es spam, clean X-TnetOut-From: ofv@wanadoo.es X-TnetOut-Watermark: 1672513012.60471@MojvhXgCv6Wkx4nB20FVEw Received-SPF: softfail client-ip=86.109.101.202; envelope-from=ofv@wanadoo.es; helo=relayout02-redir.e.movistar.es X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:301876 Archived-At: Eli Zaretskii writes: >> The MSYS2 distribution named "MINGW64" already links to MSVCRT, as >> always did, and that will not change. Is the UCRT64 distribution the one >> that provides a gcc/binutils/everything-else that links to UCRT. > > So if the user has the UCRT version installed, they will necessarily > link against UCRT64. The user can have all distributions installed, if he wishes. They live in separate directories. There is an emacs package for each distribution (for instance: mingw-w64-x86_64-emacs for MSVCRT on x86_64, mingw-w64-i686-emacs for MSVCRT on x86, both built with gcc, mingw-w64-clang-x86_64-emacs for UCRT64 built with Clang, etc). Each of those packages installs on a different directory hierarchy. If the user opts for building his own Emacs, he must take care of installing it along its dependencies or running it after adjusting PATH to point to the directory where the binary dependencies are stored. For instance, if he builds in a CLANG64 shell, the resulting binary will depend on UCRT and the dlls located in the subdirectory /clang64/bin of the MSYS2 install. > Does the wording in nt/INSTALL.W64 guide users to only one of these > two variants (and if so, to which one), or is it generic, and the user > will have to choose when they install MinGW? It definitively points to the MINGW64 variant (the traditional one that uses MSVCRT *and* runs on x86_64) because it lists the packages with the mingw-w64-x86_64- prefix. A cursory look also shows some important problems with that document. For instance, gives a link to download the MSYS2 installer instead of directing the user to the MSYS2 project webpage (msys2.org). That link is no longer valid. In general, I don't know why we (Emacs) make the effort of providing so much guidance for building under MSYS2 when no similar level of detail is provided for Debian, Fedora, Cygwin, etc. Actually, building Emacs under MSYS2 is almost the same as the other platforms. >> The commit message says "fclose fail during atexit as if they were >> already closed" but indeed it doesn't describe a user-visible problem. I >> can ask for more details, if you are interested. > > I am. Ok, I'll ask the patch author.