From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: MinGW build on master fails with Error 127 Date: Sat, 24 Dec 2022 21:10:26 +0200 Message-ID: <83lemw4nz1.fsf@gnu.org> 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> <87zgbczl3g.fsf@telefonica.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="40307"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: =?iso-8859-1?Q?=D3scar?= Fuentes Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Dec 24 20:11:27 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 1p99va-000AHU-Jq for ged-emacs-devel@m.gmane-mx.org; Sat, 24 Dec 2022 20:11:26 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1p99ui-0003zH-8e; Sat, 24 Dec 2022 14:10:32 -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 1p99uf-0003yo-Vs for emacs-devel@gnu.org; Sat, 24 Dec 2022 14:10:30 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1p99uf-0001XZ-5J; Sat, 24 Dec 2022 14:10:29 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=qWB4UJh9DGYyiJxf7lfjT9fgtJhu1Eyu8sd78yma6Vk=; b=RFXQqdc1NoH9LNQxm3PD HPNcn6BjC3JqK406myeqgWA+O1z6RBpVA5jng7p7vLNnM492ZJ+7RxiwwP9+BCX92sJAfolLH47+7 6bJ7ZKkXGzHZXnZ7mwVSdXBr46Tyjx9AJACKIEf6zXC01OMpQEk+ao+iApTWqv+oA08I/I2zYRs7x tCr5azuX5YSOequm2H5YZ4aQb+pvU62Ye7M0OIj1blkX0gTHDmUKLHC4jwSmoCfRLkDtdsGVz/9IY 4NrSLjTyXzMnQrG/BrVDXc3Azm3K8dcR/W7KsgFjcmpRwLW1T2cBw3G26lnhYiDKeBPurBKU9/F1y eRM2V3LsDKTSKA==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1p99ue-0000OS-CP; Sat, 24 Dec 2022 14:10:28 -0500 In-Reply-To: <87zgbczl3g.fsf@telefonica.net> (message from =?iso-8859-1?Q?=D3scar?= Fuentes on Sat, 24 Dec 2022 19:56:51 +0100) 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:301877 Archived-At: > From: Óscar Fuentes > Cc: emacs-devel@gnu.org > Date: Sat, 24 Dec 2022 19:56:51 +0100 > > > 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. OK, that's good. > 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. Fixes for stale and outdated URLs will be appreciated. > 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. The Windows users typically need to do more to arrange for a working build environment than users on Posix hosts. > Actually, building Emacs under MSYS2 is almost the same as the other > platforms. Once you have a suitable build environment, yes. But until you get there, no. > >> 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. My guess is that close_stream (which is a Gnulib module) does something that fails with UCRT. For example, it uses __fpending, and AFAIR that's defined in Emacs for Windows using the MSVCRT internals of the FILE object, so maybe it needs to be amended. In general, I would suggest to step into close_stream and see what exactly fails there.